Got my gTab yesterday. [VERY EXCITED!]
Plugged in wall outlet, waited 4 hours to charge.
Connected to WiFi.
Updated TapnTap, as instructed.
My Vist Ultimate computer didn't see the gTab when I plugged it in, at least not so I could get to the root directory.
So I went to an old XP and tried that. It worked.
Wanted to Root it, so I installed (sorry if that's not the correct word) ClockworkMod v08.
So far so good.
Then rooted TnT Lite v 4.2
Still good.
Then rooted TnT Lite suppl 4.25
STILL okay.
Then went to gMail. Added my gMail account. (An account I use for business.) It took a LONG time to do whatever it was doing. So I went to do something else, thinking it would continue doing it's thing in the background. I was wrong. It messed up, and I kept getting error messages.
Next thing I know, I'm somehow in that infinite boot loop.
It was about 2 am, and I was tired, and... panicked!
Next thing you know I'm freaking out and went hog-wild (while following directions to the letter), to get my brand new toy to work.
I did nvflash windows, still infinite boot loop. I tried putting the vanilla recovery 3588 on there. Still infinite boot loop.
Kept at things, trying everything I read, and STILL... infinite boot loop.
Then I figured it was time to try to get my Vista computer working so I wouldn't have to keep transferring stuff from the Vista to the XP to the miscroSD card to the gTab, and followed directions about APX mode.
I was delirious, exhausted and scared, and kind of went postal (in a frenzied OCD sort-of way), trying everything and anything to get rid of the infinite boot loop.
Now it won't even power up. (AT ALL!) I think I gave it a heart attack, or possibly a stroke. And that's with not even owning it for 24 hours!
I've tried the long 45 second power hold, then the short one. [Did that about 37 times.] I've tried power and Vol+. Nope. Then did a few power and Vol-, just to really freak the poor sick, dead thing out. [Like kicking the proverbial dead horse, I guess. Trying to see if there was any life left in it.] I even read to turn off the lights to see if there was a faint glow. But nope. No glow.
I will now follow the directions from another post, and will let it just sit for 24 hours (if I can survive the wait) to let the battery discharge and then see if it will boot. [After this nightmare, there is no WAY I will take off the back and hit the reset button--thereby definitely voiding my warranty.] But I hope I'm not like the woman from the forum thread: http://forum.xda-developers.com/showthread.php?t=968177
If I am, and can't get this thing to power up, do you think WOOT will let me return it???? I'm so upset that I broke my new toy so quickly. If anyone has any suggestions about getting this thing to boot up, I'd appreciate it. [at this point, I'd be happy to have it boot up in the infinite boot loop!]
Oh, and one last question, how does having it turned off (because I can't turn it on) and sitting there drain the battery to the point that it needs to start fresh after a mere 24 hours with no activity? Is that typical for tablets?
THANK YOU to anyone who can offer advice on what to try next or how to remedy this problem. Please keep in mind that I am good with PCs and laptops/netbooks, but am VERY new to this whole android and tablet things, so if you send instructions, please give implicit directions (as though you are instructing a 3-year-old), without feeling as if you are insulting me. [Please believe it's what I need, and will appreciate. As will the other wooters who just turned their gTabs into brinks] And know that you will be helping Roebeet by answering my questions, because the poor guy must be exhausted from all of us lay-peoples' foibles and mess-ups. [The man seems to be a God at this site!]
Did you do what is mentioned right after step 10 in this thread?
http://forum.xda-developers.com/showthread.php?t=865245
"If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups."
But first... switch to decaf and get some rest... ;-)
Panic doesn't help.
It might actually be powering up but staying in APX mode. I've seen one do that. If that's the case you can still nvflash it back to normal. Let it charge for 15-20 minutes and leave it on the charger. Try to start it up and see if your pc can see it.
You maybe got the bootloop because your tab had sleep death while syncing. Was the error you got by chance something like process.acore? If so that is a classic error that happens after syncing contacts, sometimes there are empty contacts with no data that make the tab go nuts. Simply deleting the bad contacts solves the problem.
A simple wipe data/cash/davlic would have been the first place to start. Breathing helps when stuff goes wonky.
If you can get it to recovery a repartition is totally necessary. Deffinetly... and maybe some whiskey ....
Good luck.
good luck with woot return, dont even think they do it.
I wouldn't worry about the warranty. You already voided it when you rooted the device.
I'm so sorry, guys, I didn't check off the subscribe notification, so I didn't know that anyone had written.
cdavisccs28, I didn't do that while the tablet was boot looping, but somehow it went from bootlooping to complete death.
K J Rad, it wasn't charging, and wouldn't boot. [And you can probably guess, I tried numerous times.]
Mantara, the death in the middle of syncing certainly didn't help it, and, as you suggested, might have been the last nail in the coffin. The whiskey suggestion was funny! Actually I, personally don't drink, but as you might have deduced, I'm a carrier. [AKA: I've been told that I drive people to drink.]
spike378 & filterking: Yup, I think you are both correct. How I managed to spike from "excited as a schoolgirl" to "completely tanking" in less than 24 hours amazes even ME! [And I know me, and am used to me! I think that was a personal record!] [If I don't laugh about it, I'll cry!]
THANK YOU ALL for replying! Your time and concern meant a lot to me, but I think this baby is totally bricked! Elvis has DEFINITELY left the building! If I do get another one (I'll have to start saving again), I might be too afraid to play with it. I really am good with PCs and notebooks, so I might just keep staying with what I know. YOU GUYS ROCK, for trying to help me, and I really appreciate it!
Same problem. I booted the device up, and connected it to WiFi. Then it gave a popup where it asked to update to the newest version. I said okay, and let it do its thing. Then it restarted into a bootloop. So, I turned the device off, and tried to turn it back on, except -- nothing. With the USB plugged in, it's not recognized by the computer at any time after I press the power button. I've been trying to get it to boot for an hour now and it's still just sitting there with a black screen. Not even a backlight is showing. Anyone know of any solution? Or is it time to ask for an RMA from Woot!?
h.nocturna, WOW, you didn't even get to the part where you started doing everything and anything (in a frenzy) to get it to work properly! That might be a good thing, h.nocturna, because you haven't voided your warranty! You might need to send it to Viewsonic to be fixed (since it messed up while you were doing their update), but at least you can do THAT! I mailed my brand new brick to my son up in college and gave him this site, and told him to have a blast, and do whatever he wanted with it. [He's known me his whole life, and said even HE "can't fathom my destroying something so completely in less than 10 hours."] I wish you luck!
Oh, one more question that will help the masses, I'm sure. So how do you get your computer to recognize the device as a hard drive, when it is plugged in to a Windows PC (without voiding the warrenty, of course)? [Vista Ultimate does not recognize it, and neither did Windows 7.] Please give step-by-step instructions for the lay-person. [By answering this question, at least we will solve THAT problem for folks!]
badtypist,
I wrote you a fix last night and when I went to save it the Forums had been shut down and do it didn't save to post --
and I had been on the road and was exhausted and just couldn't stay up long enough to redo it if and when they came back up. Sorry.
You simply needed to find one solution and then let us get down the procedure to follow to fix it.
Several people in the past have gotten to the point where you were. I read two fixes.
One was some people were able to get the tab to start again by playing with the
power switch -- hold it for long, long times and then press a short startup, etc. Somehow they got that to reset and start.
Somewhere else in the forums -- and I have never done this with either of my tablets --
there are a few threads where someone in this kind of situation opened up
the tablet card and simply unplugged the battery for 10- or more seconds. There also
is a reset button inside the case as shown in an old thread where someone opened a
G-Tab up and took pictures.
If any of those three choices get to where you can either use power / volume - to get
into NVFlash more ---- or to where we can load CWM -- then you are in fair shape.
LOTS AND LOTS OF BOOT LOOPS ARE ASSOCIATED WITH PARTITIONING. Simply
getting into CWM and re-partitioning to 2048 and 0 and then using CWM to "Fix
Permissions" will get it working. CWM also will let you wipe the cache and wipe the
factory data, which sometimes will allow and NVFlash to come on up and work right.
You see, we were not dead by any stretch.
You might pass this on to the recipient of the tablet.
Also, so many people are trying to do so much that is over their heads -- and so many
people are borking their tablets -- that this site and the folks that can help -- just can't communicate. Sad day.
I wish you luck. Hope this helps.
Rev
EDIT: Well, I guess we missed the boat completely. Evidently she mailed of the G-Tab and checked
out for good!!!
Hi Rev! Sorry I didn't get back to you sooner. I TRIED to get back to you sooner, but I think this site was down, because it kept timing out and wouldn't let me get to the site OR the conversation thread! I tried a few times, then tried later, and now just tried again!
I think you guys are getting BLASTED with desperate lay-people from the over 10,000 tablets sold on Woot who have "borked" their tablets. (That's a funny word, Rev! I hope I'm using it properly! And please note, although the WORD is funny, the actual situation is NOT funny!)
Yes, I mailed the offending frustration-linked object to my son, and can't "take it back," but perhaps I will beg for and borrow enough money to try again, sometime soon! If I do, I will come back here again sine I feel I have bonded with the wonderful, sharing folks on this site. (I'm a she, by the way, not a "he.") I admire (okay, worship) the folks who help us lay-people out so we don't sit alone crying and trying to power/Vol+ in solitude!
I've read your other posts previously, Rev, and you are so wonderful to help us n00bs! So please remember "badtypist" (hopefully with good thoughts) and when you hear my name again, let's hope it's to say... THIS TIME I ROOTED IT CORRECTLY!!!!
Thanks again, for your time, Rev AND the rest of you, which wasn't wasted, because I sent my son this link and he will (in his spare time) read through it to fix HIS new tablet. [I think he kind of liked that his mom messed up! He got a VERY expensive new toy, if he can fix it.]
Perhaps I'll talk with you soon...
badtypist (and bad ROOTER. Or is it ROOTERIST? Or maybe ROOTIST? Whatever the proper term, I think we can all agree that I AM bad at it!)
Gtab Update Problems
So, I would agree with some of the posts above. I would also point out that you have two options (or some combination of the two):
1. Try to return the tablet, or put in a warranty claim (the warranty specifically does not cover modification\rooting)
2. Try to fix it yourself
I tend to choose #2 f I think the chances are better than 50/50 in my favor. Also, if the hardware is okay, you can have it fixed in 20 minutes.
The experience that the OP went through is EXACTLY why I discourage newer g-tablet owners from rushing in and flashing alternate firmware to their tablet. I am often chided for this recommendation, but I believe that it is unwise to modify a brand new tablet.
If you still want to mod it, you should have a backup plan. I save my update file to an external USB drive. You should then be able to re-install the stock update by placing it on a microSD card. You need to rename it to update.zip, and add a file that tells it to look at the microSD card for an update. I am a but fuzzy on the specifics, but that file is named "command", and I found it somewhere here in the forums.
As I plan on modding my newer woot tablet (or maybe my older Sears one). I will first set this up, and will work out the details.
Hi buzzzard, thanks for the great info! VERY helpful. I did see that video while researching the gTab, but didn't bookmark it, so I appreciate your adding it here! My son will see all your posts and will use all of your suggestions to try to raise my brand new gTab from the dead! [It wasn't even in zombie mode when I shipped it to my son, so we'll see what happens! I'll keep ya'll informed.]
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS? [I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
buzzzard,
I have always understood -- and I don't want to know bad enough to spend the time
researching it -- that the warranty is void when you load non-standard software.
And even if it were not, I have real questions about messing up a computer and then
taking it back to the seller as if it were faulty. Seems to me there is a dishonesty
component in that equation.
I think modders SHOULD accept the risk that they can trash their tablets -- and that
if they do then the loss is theirs.
Rev
P. S. -- I've tried to say this much without starting a flame war -- if you do I won't
answer you and will ask the moderator to close and hide the thread.
badtypist said:
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS?
Click to expand...
Click to collapse
For one, this will give you time to read up and learn more. I can tell that you are confused by all of this. You don't "root it to a faster OS". Rooting is a method to gain root privileges on the tablet. To you windows users, root is the equivalent of Administrator. There also is only one OS available for this tablet, and that is Android. Some have made modified/customized versions of Android, but it is still Android.
[I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
Click to expand...
Click to collapse
There seems to be the misperception that you have to install a custom firmware to get root privileges or Android Market access. This can be done on the stock firmware, and then makes the tablet much more useful.
butchconner, I know you weren't talking to me, but I am taking full responsibility, and am hoping my son can resurrect my gTab, and I DO hope there will be no flaming, as well. ["There's no need for flaming. It's unsportsmanlike, kind-of rude and unproductive," said the mom to all reading this thread. So please don't flame so this won't get deleted for other poor people who "bork" their gTabs.]
badtypist,
wasserkapf was around when I got my first G-Tablet -- when we were all getting started last November.
You have no idea how bad the software was back then and the things we had to do to make things work.
It wasn't a question of 10 different ROMS and whether it was fast or not -- it was a question of making it work.
But I agree with wasserkapf (and I don't mean this comment particularly at you ) that
people are trying to do too much to fast. In addition to being a minister, I also was
an exec in the IT field for 30 years. I learned to read the docs, to move slow, to make sure each step was
successfully completed before moving on, to test things that
I'm not sure of -- and a whole host of other things that IT people use to operate their
company's systems without crashing it and losing data.
I helped a guy along the way who said he was inexperienced and that his tablet was in
the same kind of situation yours ways. He had gotten his G-Tab, charged it up, and had loaded EVERYTHING he could find on it.
Three or four different ROMS including an
experimental ROM he had been warned was risky. Yet he was having to ask what
recovery was and where to look for files and other basic questions.
I think everybody should get their tablet, upgrade to the latest version of stock, install z4root and
Titanium Backup and learn to use them, then install the latest version of Angry Birds and whatever useful software they need -- and then enjoy
that for a while while they learn the ins and outs of modding.
I help people because of the kind of person I am and because I am retired and have
some time to devote. But I also will be honest and tell you this -- I don't suffer
obnoxious, foolish people well -- and there are folks I just don't help because someone gave them good advice
and they didn't listen........I help folks who need and deserve to be helped.
The alternate ROMs are nice. And it's neat to add market and other useful stuff to
your tablet. But none of those kinds of things are so important that they are worth
what some folks do.
Nuff said. I don't respond to flames. And when you have been helping people as long
as I have, then you can have your opinion.
Peace,
Rev
If I play with my build.prop settings is there any chance of bricking my phone?
I fully intend on making a backup of the build.prop for when I inevitably mess it up, but I don't have a full system backup if I softbrick.
The reason I want to do this is that some of the Tegra 2 games won't work on my phone because they are "not available in my region". I think that is bs, and I think modding my build.porp will help. So I want to modify my settings to trick the game into letting me play.
On that note, could anyone tell me what settings to change? The 'region' setting is a no-brainer, but anything else? There are quite a few items that indicate KR or olleh (the provider).
DrNugu said:
If I play with my build.prop settings is there any chance of bricking my phone?
Click to expand...
Click to collapse
Worst case just flash a ROM
sent via tapatalk from my CM7 Atrix
btw - I'm stock gingerbread with root. I'm not really interested in ROMs (at the moment), I'd just like my phone to act like it's American <insert joke here >. Basically, I want it to tell the software that it is an AT&T phone in America, so that I don't get rejected because I'm in Korea. They have strange gaming rules and many hoops to jump through before a game can be released here. Hence my shenanigans.
If you have a knowledge of adb then you are fine. You can soft brick but not hard brick.
sent from my Atrix via XDA premium
N00B in N33D
Hey guys,
I've been searching and searching and I can't really find a way to fix this problem I've been having.
I have a Motorola Atrix from Bell running 2.3.6 and I had rooted it.
I got a little power hungry since this is my first android and therefore obviously my first root, and I started deleting stuff like crazy. Unfortunately one of those things was all of the yahoo system apps since I didn't look up if they were important or not, and they obviously were.
My problem is as an attempt to re-install all the yahoo files, I tweaked the build.prop file. I opened it as a text file and changed the ro.build.version.sdk=10 to ro.build.version.sdk=9, i think it was the 6th line of the build.prop text then I rebooted my phone.
I never made a backup or nandroid or anything like that, mainly because I didn't think anything that bad could happen from it. Then I ran multiple factory resets of my phone in hopes to fix this problem, but it still persists. All my phone does now is continously try to boot up, but it just keeps restarting itself halfway through, I can't get to the unlock screen or anything like that. I feel like I royally messed up my phone, if anyone could help me out with this it would be much appreciated.
I can run hard resets using the buttons and run things such as fastboot and RSD even though I dont really have much idea what they are. So I've been trying to educate myself a little with http://forum.xda-developers.com/showthread.php?t=1154600&highlight=soft-bricked+atrix and I'm finally starting to understand what I actually did to my phone.
Once again any help would be much appreciated, thanks, if you need any more information just let me know.
hi guys,i have the i9300t,and because of that extra t my phone has to wait for all the official updates a hell of alot longer than the other versions. ive never rooted my phone before or installed custom software,ive been looking into it recently because so far jellybean on my device sucks and i would prefer something better. i like the look of android 4.2 and someone suggested cyanogenmod 10.1. i was wondering if anyone is using it as a daily driver and if so,is it worth it,what bugs are there etc. also if i was to root and install new software,and there was a hardware issue or something that i could send away for warranty,is it possible to unroot and make it look like it never happened so that the tech center dosent refuse warranty?
im guessing all these questions are answered elsewhere and are probably very simply answered but im new to all this and with threads that are sometimes 100+ pages long,its not something that i want to go searching for.
also sorry if this is in the wrong section,if it is please move it or notify me i would be happy to move it
Thanks in advance
You can always unroot, just install Triangle Away, which resets your flash counter (aka how many times have you flashed unofficial firmware i think). Applies for hw issues too, just do that and you're good. I use cm10.1 on my nexus 7 and it's great, but look out for the issues. Correct me if I am wrong
hmm those issues arent too bad,nothing that would impact day to day use. mainly jellybean official sucks really bad,laggy widgets,sometimes unpredictable behaviour accross device (just earlier i recieved a txt from a friend and when i opened the txt it then swapped over to another contacts conversation). ive had all my contacts multiply upon upgrading and had to manually go through and fix them all. occasional non responsiveness etc. i just want stock android and i dont want to have to buy a new phone. so i guess rooting is my way to go.
Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!
joethesupercow said:
Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!
Click to expand...
Click to collapse
Don't drop it in the toilet when your texting in the washroom.
Check the pockets of the clothes you are washing.....I lost many gameboy games that way when i was a child
And dont update with low battery and dont turn off the phone during an update/flashing a rom
Be patient. Seriously. I remember the first time I was backing up in recovery I got frustrated and terrified that I messed something up after 2 minutes, and shut off the phone. Thankfully this was just during a backup, but I've heard plenty of brick stories of the "I don't think anything's happening after __ time, I'll just kill it it."
Also, READING IS FUNDAMENTAL. There are often silly nuances of your phone giving you some type of message and your left to pick a command. Often every other install sees the same message, and it isn't necessarily true that the right option looks like the right option.
Read and be patient.
Back everything up as you go. It's easy and quick and can save you loads of time and effort if something goes wrong. In my experience, when following instructions and proceeding carefully it's difficult to brick your device.
Sent from my SCH-I545 using xda app-developers app
I like to get drunk and flash stuff on the weekends though!
You know what I do when I buy a video game? If you guessed read the instructions then play the game, you're dead wrong! I jump right in and start killing stuff!
Anyways, my point is, sometimes I'll just miss a step, or not pay attention, and was wondering is it easy to get out of a jam like that? I've never worked Odin, but have some adb experience. Can I just Odin back to the stock image and restore a nandroid after I get a recovery back on it?
Sent from my Nexus 7 using Tapatalk 2
As someone may use this thread to commit warranty fraud it is being closed
Moral of the story is: Backup backup backup
Do not flash anything not specifically for your model and carrier unless VERY specific instructions are given by someone who succeeded
And on that same note READ READ READ
Has anybody ever really "bricked" their Device? Whats your definition of "Bricked"?
I asked because I hear this a lot and i hear just as much if i that if it hows any life at all, it can be saved. ( i fully agree). and also you will hear just about everything you do can and will brick your device. ( i understand why this is said) but how many of you have actually had to use your device as target practice as this is the only fun thing you can now do with it? I get everybody defines it as pretty much any problem you have...just get on this site..every single post somewhere is "help i bricked my phone". "did you turn it on"..."oh wait , thanks" Now i get the fear, especially when i first started messing around with android.. i guess i am the type who thinks its easier to just try and figure it out by reading then to ask and I afraid you will laugh at me and call me names.."DID YOU READ ALL 6567 PAGES BEFORE YOU ASKED"..NO THEN TOUGH, HERS HOW..." JK love you all, casue i will ask in the future.. so on the topic if you all don't mind I would like to tell you about how I and I alone have a hard time bricking.... Please don't take this and go try any of what i said i did in this story...you will brick your phone OK now that is out of the way I would like to say ... I think its impossible.. ( its not....) yes it is
Hello land of android. I just wanted to tell my story of the S7 edge Live demo unit of H Ell. I have one and I went to remove the retail version or what ever it just wouldn't boot anymore. I could get in blue down load screen but that it. I tried for 2 months, in between my other phones and not caring anymore about the phone ( my friend gave to me, he had two that he got while working at a Verizon at best buy store in the Midwest and it shut down.. he managed the store and they told him to toss the phones....in case your wondering as every post i see about these somebody is calling the guy posting a thief in one way or another...EVERY SINGLE ONE, besides this one ha ha jk, one of you will) anyways I have flashed and flashed and flashed with no success, I finally got twrp on it...OK, now i am getting somewhere. still took 3 days and many a thing I flashed, at this point it has a boot loader exception error that i have never seen nor could find many people on here that have. Used to have "USE smart switch to recovery cause your update failed" or something like that and a half a dozen other errors from doing stuff that i don't fully understand. I tell you, to people who are worried about bricking their device.....I am starting to think thats a myth...i tried my hardest to brick this phone ( i flashed every zip file i could get my hands on, its started to be a joke to to see how much the phone could take..i was flashing zips of different phones he ll i was flashing zips that had nothing to do with Android at all. back to what i was saying couldn't get it to boot either so i was thinking maybe that this mythical BRICK i keep hearing about. I do this to all my phones and every single one of them, thanks to all the knowledge and amazing people on this site, reading posts not asking..wanted to point that out, i am not wasting peoples time asking them to help me fix things I am trying to screw up on purpose. ok back to it..I got all my devices running, rooted and blazing away every single time...."knock knock"... he he get it cause i am at my desk.. huh ..my WOODEN desk.. right...come onahg nevermind..i suck at life, anywho back at it.... ITS my way of leaning. ( should of seen my computers back in the day trying to learn what the hell "Windows was". ) Anyways I am just rambling on about this to just say, its a lot harder to brick your phone then it is to do anything else to it. IF YOU LISTEN TO ME AND GO TRY ALL THIS DUMB STUFF AND BRICK YOUR PHONE...TOTALLY YOUR FAULT FOR LISTENING TO A RANDOM STRANGER ON THE INTERNET...DON'T DO IT. Anyways, i finally got the live demo unit SM-G935X booted with a Rom..i tied them all.. like 4 at least ha ha and a bunch of stock firmware. I flashed the Flyme on it, which i know nothing about and the mo-fo booted up after two months of nothing and just crazy errors.. Its now saying its a SM-G935F. its rooted and everything..way cool. I just thought i would share or if anybody needs to test a program, file, or apk..... anything...ill be your GG PIGGY. ( for stuff you are actually trying to make work, i don't need programs written just to F my S up... i can most likely handle that on my own....edit...actually,,this would be funny....nah never mind. no intentional screw ups...yet..just talk me into it... Its going to be my mission to see how much this phone can take...you know ..for science and all that. But later, right now i am gonna enjoy playing with my new S7 since i just got it going. BUT SERIOUS..DO NOT ATTEMPT ANY OF THIS, YOU WILL BE THE ONE WHO BRICKS THEIR PHONE.. Also wanted to point out my S5......yeah that little F'er can take some abuse as well. Even my daily driver one plus 6t has already seen its share of the Jrod thinking he is some master developer hacker dude. that going to figure out the next awesome thing we didn't know we could do. ( not even close...not even in like dog years of life times or ...wait that s shorter isn't it,,anyway back at it the One Plus 6t oh yeah ... it cries at night, i pretend i cant hear it but I know whats up. Anyways thanks for letting me ramble on & on. Sorry this was a mess...i get to excited and type way faster then i can think. ( my English teacher said i was going places....ADC but still its somewhere,,,i did ,,damn,ok never mind back at it. wait no i am done. I would like to hear if anybody has like totally killed their device with software ... i get you could put it in the microwave and brick it,,, i fell for that twice.. i want to hear if it happen to you and how. .so next story. or just completed delete this and ban me.. I deserve it.