Related
The subject was just to make you laugh, there is no Pron in this story.
For the short version minus the story, skip down to the 2nd paragraph, otherwise read below.
Well I have been running my Hermes for over a year, have flashed it dozens of times, about 10 Roms ago, I ran across one that caused a hard reset, so I quickly dumped it and moved on. I went back to flashing like normal. Then running M2D I got a hard reset that was so bad, it froze the machine and could not even boot. I gave up on the M2D based Roms and went back to old and trusty CRC's stuff. Yesterday again when I really needed my phone to work perfect, on a car club drive, 100 miles from home with people calling me to arrange times they are meeting me and to ask exactly where our group was in the run, my phone locked up. I was able to get it to load back up long enough to quickly hit the call forward to my wifes phone who was along with me. I had her fiddle with it, and reset it. Right back to fresh install of CRC 14.1 On a good note, I found that when needing too, I can install TomTom and even configure my Bluetooth GPS with one hand while driving at 90mph on a backroad chasing other car guys.
Ok during my random flashing of Roms over the last year or so, I have never once flashed it back to stock. I installed Hard SPL, upgraded the radio to 1.54 and never looked back.
Could someone give me a quick brush up on Re-Flashing back to an OEM rom, what is the "Proper" rom that I should be using. Will the OEM rom screw with my radio. Why is this even necessary?
Capt Fiero said:
The subject was just to make you laugh, there is no Pron in this story.
For the short version minus the story, skip down to the 2nd paragraph, otherwise read below.
Well I have been running my Hermes for over a year, have flashed it dozens of times, about 10 Roms ago, I ran across one that caused a hard reset, so I quickly dumped it and moved on. I went back to flashing like normal. Then running M2D I got a hard reset that was so bad, it froze the machine and could not even boot. I gave up on the M2D based Roms and went back to old and trusty CRC's stuff. Yesterday again when I really needed my phone to work perfect, on a car club drive, 100 miles from home with people calling me to arrange times they are meeting me and to ask exactly where our group was in the run, my phone locked up. I was able to get it to load back up long enough to quickly hit the call forward to my wifes phone who was along with me. I had her fiddle with it, and reset it. Right back to fresh install of CRC 14.1 On a good note, I found that when needing too, I can install TomTom and even configure my Bluetooth GPS with one hand while driving at 90mph on a backroad chasing other car guys.
Ok during my random flashing of Roms over the last year or so, I have never once flashed it back to stock. I installed Hard SPL, upgraded the radio to 1.54 and never looked back.
Could someone give me a quick brush up on Re-Flashing back to an OEM rom, what is the "Proper" rom that I should be using. Will the OEM rom screw with my radio. Why is this even necessary?
Click to expand...
Click to collapse
You can use any OEM rom, theres a stripped one in my 4shared, this means it wont flash over your radio, so its safer.
And this is necessary because of the way BS roms are made, they mess with the internal memmory structure (combinging the ext rom and the main storage), flashing a OEM is like a spring clean
Hi there guys,
this is pretty much my first post, although i've used this site a LOT since i got my phone
I have been trying to install various WM 6.5 ROM packages onto my phone over the past two days (about 8 or 9 hours in total), only to be met by failiure every time! (i have never attempted to install a Cutsom ROM on my phone before)
My Phone will Start, although it will just Hang on the "TOUCH Diamond" Screen, meaning i have to boot to the Tri Colour screen to revert back and install official rom!
I have tried FuFu 4.1.4, Ghetto, Miri etc etc..
i started off using 1.40 OliNex Hard-slp, and as i tried every possible WWE Diamond WM 6.5 ROM i could find, until i realised, it really wasnt working, after installing custom ROM, Hard resetting, and then reverting to the Official every time; multiple times!
I have now installed the 1.34 HardSLP (http://forum.xda-developers.com/showthread.php?t=408621) using "Jump=slp" (and checked that it is installed) and have found that this does not work either!
I really have no clue as to why it wont work, as i have searched and searched google, and done a load of searches on xda Dev. too and cant find anything!
I also noticed, that every time i went to revert back to the official ROM (2.03) The RUU shows "From: (blank space)" "To: 2.03......."
Any enlightenment on the subject would be great, as i think i've spent a bit too much time trying to get it to work to suddenly turn back now!
P.S, to all developers out there, THANKS for all of you great work! Keep it up guys, there's so much great stuff coming out!
Problem fixed, was cos i was doing the flashing on a stupidly crap laptop lol!
ahh well...
WM 6.5 is a bit better than 6.1 haha
same problem
hi
could you explain step by step how you solve it , i have the same problem " touch diamond" is on screen with nothing happens, i tred allmost everything including a diffrend compuer ...
have you flashed your phone with a hardslp??
I've had problems rooting in the past, but this one takes the cake.
I got my M9 today and was gleefully rooting it. Everything was going fine. I installed Android Revolution HD 14.0, and it went smoothly as far as I could tell. It installed, booted up, and wanted to take me through the start up process.
Except for one thing, I have no mobile data connection. Everything's one. It's not like the mobile data is off or Airplane mode is on or something. I just don't get any data. I can't text or get on the net (wifi does work, however).
When I realized something was wrong, I went to go use my backup, except that was gone. I'm trying to download a different ROM now, Viper One (which I used on my M7), but I'm not sure if that'll work. I'd love to try out Revolution, but I don't know if it's Revolution HD, or something on my end that I must have done without paying attention.
Could I have somehow deleted the necessary files to give me service and Revolution HD doesn't have those files? I've accidentally wiped phones way back when I first started rooting, but was always able to get everything back in gear after figuring it out, so I can't be totally screwed here. I just don't know what to do?
you could try ##786# in the dialer and hit reset in the menu
I tried that actually. I'm trying something else right now. It took some searching, but I finally found a post on here (I'm bad at searching when I'm freaking out) that had a similar issue as me, so hopefully that works. I'll check in.
I tried the suggestion in this thread and that didn't work either.
I'm just at a loss. There has to be a way out of this right?
Success!
I tried ViperOne and it said it was corrupted. So I downloaded it again and realized that the second download was about 1.2gigs larger than the first download. So for whatever reason the original download didn't get it all but said it was finished.
So I flashed the complete ViperOne, and I'm in.
i cant seem to find all the files i need, i formated data, via TWRP / formated everything, trying to get back to stock, because everytime i turned around something kept uninstalling supersu, one min id have root, the next i didnt think it was kernel issues idk, i wanna start over though, can someone help me. this is what im working with these two photos. i was running SkyHigh-v3.60, and BigDaddyPK1_Aroma1.x
https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Flash the latest TAR file in Odin and you return to stock.
mac.os.x said:
i cant seem to find all the files i need, i formated data, via TWRP / formated everything, trying to get back to stock, because everytime i turned around something kept uninstalling supersu, one min id have root, the next i didnt think it was kernel issues idk, i wanna start over though, can someone help me. this is what im working with these two photos. i was running SkyHigh-v3.60, and BigDaddyPK1_Aroma1.x
Click to expand...
Click to collapse
If you don't want to jump all the way to starting over with ODIN flash, you can just load TDH-JR ROM, which has probably what you want: https://forum.xda-developers.com/sprint-galaxy-s6/development/rom-tdh-jr-rom-t3550677 -- maybe give that a shot.
I fixed it yesterday finally, thanks for the response though but I ended up doing I downloaded like three different Factory ROMs and I tried each one of them thinking that but then I read somewhere that once I upgrade the CPL or somewhere along them lines that I can't go back but they added this stupid ass code that you can't go backwards cuz of the battery issues they had when all the galaxys were blowing up, somet hi ing l8ke that, so after I read about that I went ahead and well obviously at that point you just want to fash yiur factory ROM at that point is the ROM that you upgraded to just grab that same ROM and use the same kernel and everything and I did and it booted but I sold that
S6 i think I'm going to try I'm and check that ROM out that you just posted the one I'm on now the black one that were referring to right now I sold the yesterday after I fixed it but this white one is the better one and I'm about to root it now plus it's already unlocked it's a Galaxy SM g920p 32gig unlock I'm rocking MetroPCS on it right now and I'm getting pretty good signal actually.
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.