Related
Just got this phone and I love it but the seller on ebay had it rooted and had one of the roms from here on it. They said they would put it all back to stock for me. I like to start with a clean slate if you know what I mean. Well, it is back on gingerbread but root is still there and a whole bunch of other stuff (apps, roms, titanium backup) etc etc in folders on the internal storage. My question is can I safely get this phone back to being stock just like it was from the factory, without the risk of bricking it? I know how to use Odin for the Epic 4G and all. I knew there were some problems with the touch and some phones getting bricked. I have no clue what they may have done to the phone so I am a bit concerned to do anything to it till I hear from someone who has done this (gone completely back to stock) Also, is there a tutorial somewhere?? Thanks guys for your help with this.
Oh here is some more info if it helps looks like I am on Android version 2.3.6, EL29, kernel 2.6.35.7 there is some other info if you need it please let me know I do see a Caulklin's folder in there in the internal storage so most likely they did have that rom on there at one time. There is also a ACS folder in there but when I try to open any of the folders in there I get an error that there is no program that can perform this action. Grrrrrr
Hi.
When messing with Gingerbread, especially stock, bricks are pretty hard to come by nowadays.
Here is what I suggest:
http://forum.xda-developers.com/showthread.php?t=1433101
(from what you said, you probably understand this already)
Just run the EL29 OC. You'll be good to go.
In terms of the internal storage, just delete it all or run a format. You won't get yourself in trouble that way, it's just the internal storage.
If you're concerned about the data wipe brick, that is only on ICS. So since you're on GB, it is not a problem (and totally unrelated to clearing internal storage.)
Post back if you have any questions or anythin'.
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Thanks guys. The phone at one time was on an ICS rom and yes I can search for it. I just wanted to make sure before I did, that this could be done. So, I will see about finding the tutorial and how to go about getting the phone all back to factory like. I know I am so anal this way, but I really do like to start with a clean slate before I do anything to any phone. thanks again guys I will holler if I run into any problems. LOVE this phone though.
thewadegeek said:
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Click to expand...
Click to collapse
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
It didn't for whatever reason. I had to go in and edit the MIN and MDN manually to get it to activate so maybe that is why. That thing was a HUGE pain to do too. It would not take and kept resetting. Had to try it like 5 times.
Esoteric68 said:
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
Click to expand...
Click to collapse
If you are stuck with what to do next then take it to a Sprint store and let them wipe it for you.
Good info
As I'm going to try this and hopefully get the missus off her Opt S and onto an E4GT this week this was good timing to cover the process.
Here's what I am planning to do:
1) Flash EL29 + Root
2) Factory Reset from Recovery (which should clear NVRAM if I understand correctly)
3) Call MVNO and have them set up phone
4) Allow hands-free activation to hopefully fill in the blanks
If this works as I hope then I shouldn't have to tinker manually with the NVRAM data.... if not then I have my phone to base most of that off of. And of course it depends if the carrier will let me set the phone up - in the past they haven't been warm to using a different phone unless you purchased it directly from them.
All this just to sit tight until we can get the GS3 probably next year.. yeesh.
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!
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
budbay said:
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
Click to expand...
Click to collapse
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Formhault said:
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Click to expand...
Click to collapse
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
budbay said:
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
Click to expand...
Click to collapse
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Formhault said:
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Click to expand...
Click to collapse
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
budbay said:
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
Click to expand...
Click to collapse
No idea, honestly. The RMA I did was for a replacement, since it was within 14 days of purchase, so I got to choose to get a replacement. Should have chosen the refund, wait another month and get the 3T... had I known it was going to be released. Oh well.
In your case... I guess you can do another RMA and hope for a better intervention. Perhaps explain to them... more thoroughly? Or just go with the flow - they'll reload the OS, you'll report the same issue again... Maybe they replace it, I don't know.
Interesting that they did the OS reloading IN SERVICE. Usually, this procedure is done via remote control... So they don't have to pay for shipping when such a thing can be done via a remote session, you know... Weird.
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.
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
yarmannen said:
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
Click to expand...
Click to collapse
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
youdoofus said:
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
Click to expand...
Click to collapse
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
yarmannen said:
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
Click to expand...
Click to collapse
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
youdoofus said:
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
Click to expand...
Click to collapse
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
yarmannen said:
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
Click to expand...
Click to collapse
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
youdoofus said:
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
Click to expand...
Click to collapse
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
yarmannen said:
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
Click to expand...
Click to collapse
well, you have TWRP and magisk installed, i assume. Correct?
youdoofus said:
well, you have TWRP and magisk installed, i assume. Correct?
Click to expand...
Click to collapse
Yes! TWRP is installed. Magisk got installed with the ROM.
yarmannen said:
Yes! TWRP is installed. Magisk got installed with the ROM.
Click to expand...
Click to collapse
to be perfectly honest, if youve done all the things in the OP and its still doing that, its time to drop fat man or little boy and start from stock tar.md5. Boot to DL mode and flash the stock firmware. Obviously something is awry and the usual tricks didnt help so far. Mushroom cloud time