Related
I've posted a couple new topics, and sent out few private messages. No responses. I am just having the worst time with this phone.
And I don't mean to sound like its the end of the world or anything, its just a lot of little things irritating me with this phone ever since I've rooted it.
I rooted with nand and installed damage control. Everything seemed fine, and then I was having permissions issues (i think, still waiting for a response to THAT post). Then applications would load up and then force close, and reinstalling didnt work. I was having problems with the camera.
I'm not sure I did it right, but I did a nand backup, wiped everything. then switched to a rooted supersonic rom. Loaded all that up, and everything seemed fine, camera was fine. Shortly afterwards though, things started messing up again. I think im having problems with the permissions. Handcent downloaded an update, and then couldnt install because of "insufficient memory". I backed up with titanium, wiped, then rebooted, and handcent worked. But now my camera doesnt work.
There are two options I can think of. First, I want to get completely back to factory, a fresh out of the box HTC Evo. No signs of root, just back to working 100% with no flaws like it did before. Flash whatever updates Sprint sends out and go on with life.
Or second, I like some of the benefits of being rooted, such as wi-fi tethering. Is there a specific way to reapply root, or to reapply roms? I'm kind of thinking of completely starting over. like a brand new stock evo being rooted for the first time. I'm nervous that maybe I didn't flash that supersonic rom right. I wouldn't mind having a different rom but everyone has mixed reviews/problems on every single rom created so far. If there was a nice rooted rom with everything working, 4g, wimax, camera, everything, thats the one I want. I don't really need any special frills or fanciness.
either post here, or my google talk is [email protected]. if anyone could give me a hand with this, I'd appreciate it, I'd even donate through paypal. I just want to get this phone straightened out, I got iphone kids laughing at me!
First, please ditch the giant sig.
Second, there have been a lot of posts regarding damage controls rom and problems, so i think that's the start of it.
I would try fresh's rom and see if it works for you, after doing a complete wipe again. Of course, don't bother with a nandroid backup or restore since all that does is restore the rom, and your rom is messed up.
So in recovery, go into the wipe menu and wipe it all and flash fresh 5.3.
Alright sig is gone, sorry.
I have a hard time keeping up with the hundreds of posts in those various rom threads. I'm not too lazy to search, but I just can't find anything. And then with work and everything taking up time, its tough to follow.
I'll download Fresh's rom right now, no back ups or anything, and give it a shot. thanks for the tip!
Would DamageControl rom still have any affect on my system now, since i am now on the supersonic 1.32.651.1?
I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Rawt said:
I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Click to expand...
Click to collapse
have you tried booting into stock recovery, wiping data and cache?
xBeerdroiDx said:
have you tried booting into stock recovery, wiping data and cache?
Click to expand...
Click to collapse
I did it last night, but in my tired confusion, i may have fudged it up. going to do it now and ill update in a few minutes. Thanks for the help thus far.
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
hednik said:
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
Click to expand...
Click to collapse
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
10 minutes later and its still sitting at restoring call log. should i abort this?
Rawt said:
10 minutes later and its still sitting at restoring call log. should i abort this?
Click to expand...
Click to collapse
you can if you want
since call logs aren't important as long as your contact list is restored
pcshano said:
you can if you want
since call logs aren't important as long as your contact list is restored
Click to expand...
Click to collapse
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Rawt said:
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Click to expand...
Click to collapse
Settings, not much can be done about that. It's needed to wipe them when going to a custom ROM (same goes when updating to avoid issues).
Titanium Backup can save your Wifi, apps and apps data (requires root). Also can save your texts and call logs with it.
Rawt said:
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
Click to expand...
Click to collapse
Sounds like you booted into stock recovery which is what you wanted.
I used to think it was a pain restoring settings all the time but after 100 or so ROM's over various devices its takes 10-15 minutes to do that and install my apps form the market (I only use maybe 20 or so and maybe are one I have apk for already.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
hednik said:
.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
This line is awesome!
Sent from my SGH-I747 using xda app-developers app
Rawt said:
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
Click to expand...
Click to collapse
Keep in mind that flashing a custom ROM also means flashing the updates (as it can always get better and there are bugs to fix), meaning that you will have to factory reset every time (which resets your settings, cleans your apps and such). So it's something you kinda have to get used to when flashing.
That's also why I suggested Titanium Backup, it saves a lot of time when it comes to apps, wifi, call logs, texts, etc. You'll still have to go through your settings, emails and accounts though.
If you wanna go ahead and give Darthstarkers another try, re-download it and make sure you follow their full instructions.
hednik said:
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
its true. the first time around is always a little bumpy. as long as you are doing things correctly and installing the correct files, things will only go smoother with time.
this is just my preference, but once i've transcended stock (to aosp), i dont mess around with kies anymore. i know you had your things backed up via that route but ask around and you'll see, there are a lot of useful apps out there that can backup and seamlessly restore everything you want after flashing.
dont give up. everyone deserves the performance and style they want on their device. next time you're ready, let us know. between myself, hednik and a few others, we can get you the best way to do this right here in one thread versus 20 different sites/threads/opinions. cheers
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Rawt said:
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Click to expand...
Click to collapse
It's basically the way to show your gratitude, you've said thanks and pressed the button, can't ask for much more :highfive: Especially from a new user.
I hope you find the time to enjoy one of those custom ROM at some point and we'll be here if you need help again. Good luck!
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
I've always been interested in installing ROMs, rooting, and all the cool stuff that comes with it, since my first android phone. Unfortunately, my first two android phones ended up having a lot of issues with just working stock, so when I finally ended up getting a Samsung Galaxy Note II (I317M - Rogers/Canadian) and it worked... I held off on the modding. Well, my cell contract is up, the warranty has expired, sounds like the perfect time to start.
Of course, this is post KNOX, so after reading around and watching some videos, it was unclear as to whether I could actually install ROMs at all. I wasn't worried about the warranty, just if I could do it, and it would work. So I decided to just jump in anyway.
First task is to root. I tried flashing a CWM+Root with Odin 1.85. No go. Just wouldn't work. So I ended up using chainfire's CF-Auto-root. It would give me the root I wanted, and the stock recovery. The package came with Odin 3.07, and everything worked. It flashed, I downloaded Titanium Backup and launched it, and SuperSU did prompt for root access, and everything went fine. Excellent! Two years after getting the phone and 3 years since I've wanted to do this, everything is going well.
Next task is a custom recovery. I picked TWRP, mostly because I wanted to try the Ditto Note ROM, and they suggested using that. Flashed the recovery in Odin 3.07 and reboot into Recovery with the three finger salute of volume up, home, and power. TWRP launches. Excellent. First order of business is to click the backup button and check all the boxes. Takes 1400-1500 seconds to backup the 6.5GB.
Time to get the ROM and jump in. Downloaded Ditto Note 4 v 2.2 from the team Electron site, and transfer it to my phone. So far things are looking good. Still don't know for SURE if my bootloader is locked or if KNOX will not let me do things, but I have a couple of backups, so I'm going to take the plunge. I reboot into TWRP, wipe the dalvik cache, cache, data, and system, then I install the ROM. Didn't take long at all. Time to see if it works.
At this point I should mention that the reboot function on TWRP(v2.8.6.0) seems to just loop me back into TWRP, no matter which option I choose. So I hold the power button to actually reboot... and...
TA DA! Ditto Note 4 is going through it's first start. I come across a black and white gradient fill background with some sort of animated tesseract sphere in the middle. I'm cool with that, but that also means I can add in my own animation at some point which is even more cool. Go through the start up prompts and...
The first problem. Wifi won't turn on. The other Canadians here will know the pain of not having wifi for your cell with our data prices up here. This is something that needs to be solved. Back on to the forums to see if anyone else has had the same issue, and someone did, the solution? Flash the latest AGNi kernel. Hey, I'm down, now do I flash a kernal with odin or TWRP? After spending way too much time on google, I went to the actual AGNi thread and after a few pages found out that people were installing it with CWM. TWRP it is then. I tried installing it through TWRP, all seemed to go well, though I did note that in the terminal window I did say that it failed to set permissions. That can't be good, but it did say that it installed successfully. Let's give it a go.
The phone started... but nothing had changed. I noticed the OTA Updater app, so I tried using that. Once it was done downloading I clicked the install/flash button. That wasn't a good idea. I flashed it, but ended up in a loop that would only show me TWRP. Even after removing the battery it would only go to TWRP.
What else could I do? I restored the backup in TWRP. Let's start over.
Rooted with the same method, Installed TWRP again, installed DN4 again, tried to run the AGNi settings app and found out that root wasn't working. So after some searching I came across the 2.14 SuperSU update and installed it with TWRP. Root is back. Awesome. Time to get my wifi back, installed the 4.4.5 AGNi kernel, and this time, no permission sets failed. This too, is a great sign. Got the OTA Updater download and this time, decided not to have the program reboot to install it, and just rebooted into TWRP myself to do it manually. Installed fine, rebooted and... my wifi is working.
Mission accomplished. I haven't fully tested everything yet, but I did check to make sure that the s-pen was working, the camera, and after messing with the APN settings a bit, had LTE as well.
All things considered, for a first time, not too bad. So glad I had made that backup before hand. Glad I had remembered to do that, and also to write down the APN stuff before hand. It was mostly correct to what I had, but there were 2 fields that were different, changed them and had full LTE.
So far things seem great! More testing is needed, but I can call and recieve calls, wifi/cellular data works, camera and s-pen works.
Still a noob in this department, but due to the xda-devs making good products, nothing killed the phone, and things are working great.
Thanks to Chainfire, Team Win, Team Electron, psndna88, and anyone else that has worked on any of these projects. So far things work well, and those of us with older phones really appreciate your effort and work on breathing new life into these devices. Cheers mates!
Nice first post for your first one my friend excellent ?! If you need any help with Dn4 you can post in the q&a section since your so new to Xda.
And welcome to the world of Android and Xda enjoy your stay here.. Ttys
Bajan
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.