I know it's better to backup efs folder. What else should I back up?
i may be wrong, but i thought it was only possible to access the efs folder AFTER you root, then back it up.
Reading would be my suggestion. A simple root is non-destructive.
jack man said:
i may be wrong, but i thought it was only possible to access the efs folder AFTER you root, then back it up.
Click to expand...
Click to collapse
I guess I will root it first then.
You should follow the guide that doesn't activate the dreaded exclamation mark at boot and flash counter. It's one of the stickies I believe
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Alright mate, this is what you need to do before rooting. I'll provide you with a step by step guide, but you MUST follow all instructions to the LETTER.
1. Turn your computer on, grab a coffee and your USB cable that came with the phone.
2. Call your mum, tell her you love her.
3. Go put your clothes in the washing machine.
4. Clean the dishes in your sink.
5. Computer on? Good. Navigate to the XDA General SGH I777 forum.
6. Take a break, you worked hard up till now.
7. Go out for a walk.
8. Buy a dog, they provide companionship and are bargaining chips with your Korean neighbors in hairy situations, like when Korean ninjas ambush you (a known bug in the rooting process).
9. Name your dog, and prepare yourself - this next part is tricky.
10. You're going to die. DON'T FREAK OUT. You DO want your phone rooted right? That's what I thought. Death is only the beginning.
11. Once dead, you'll descend into Hades, where you'll have to fight Cerebus. Good thing you bought that dog now, right? You know exactly how to handle this puppy.
12. After killing him (assuming you did), you need to cut off the LEFT head (there's three, so make sure you cut the right one off).
13. Now, go ahead and talk to the witch who deals with the threads of people's lives, tell her you're just trying to root your SGH I777. She'll understand. Ask her about her "Steel Thread Life Assurance Policies." Be sure to mention me: I get paid by commission.
14. OK, so you're back with the living, + 1 left head of the guard of Hades. Take your phone and place it into the head's mouth. Plug your phone in to your computer.
15. Almost there, good buddy. Go read the thread about how to Easily Root Your phone. They're all updated to make sure you don't trip the flashcounter.
16. ???
17. Profit!
You now made your dear ole ma happy, you own a dog, you died, killed the guard to Hades, came back to life, increased your reading comprehension, learned how to find threads in XDA, you made one less thread about answered questions, and you rooted your phone without having to back anything up beforehand!
Any other questions?
Sent from my SAMSUNG-SGH-I777 using xda premium
autonomous-inc said:
Alright mate, this is what you need to do before rooting. I'll provide you with a step by step guide, but you MUST follow all instructions to the LETTER.
1. Turn your computer on, grab a coffee and your USB cable that came with the phone.
2. Call your mum, tell her you love her.
3. Go put your clothes in the washing machine.
4. Clean the dishes in your sink.
5. Computer on? Good. Navigate to the XDA General SGH I777 forum.
6. Take a break, you worked hard up till now.
7. Go out for a walk.
8. Buy a dog, they provide companionship and are bargaining chips with your Korean neighbors in hairy situations, like when Korean ninjas ambush you (a known bug in the rooting process).
9. Name your dog, and prepare yourself - this next part is tricky.
10. You're going to die. DON'T FREAK OUT. You DO want your phone rooted right? That's what I thought. Death is only the beginning.
11. Once dead, you'll descend into Hades, where you'll have to fight Cerebus. Good thing you bought that dog now, right? You know exactly how to handle this puppy.
12. After killing him (assuming you did), you need to cut off the LEFT head (there's three, so make sure you cut the right one off).
13. Now, go ahead and talk to the witch who deals with the threads of people's lives, tell her you're just trying to root your SGH I777. She'll understand. Ask her about her "Steel Thread Life Assurance Policies." Be sure to mention me: I get paid by commission.
14. Now, you're back with the living, + 1 left head of the guard of Hades. Take your phone and place it into the head's mouth. Plug your phone in to your computer.
15. Now, go read the thread about how to Easily Root Your phone. They're all updated to make sure you don't trip the flashcounter.
16. ???
17. Profit!
You now made your dear ole ma happy, you own a dog, you died, killed the guard to Hades, came back to life, increased your reading comprehension, learned how to find threads in XDA, you made one less thread about answered questions, and you rooted your phone without having to back anything up beforehand!
Any other questions?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
...I think I love you that answer was so awesome
Sent from my SGH-I777 using XDA App
Auto, every time I start thinking this place is completely overwhelmed by idiots, genius like yours bubbles to the surface.
autonomous-inc said:
12. After killing him (assuming you did), you need to cut off the LEFT head (there's three, so make sure you cut the right one off).
Click to expand...
Click to collapse
THIS IS RIDICULOUS. The left head from my POV, or the left head for Cerberus? Right there I couldn't decide and now my phone is bricked. Thanks a lot.
Related
Ok well, I finally did it. Broke my brick cherry. Screen goes black after galaxy S logo pops up. Was running bionix 1.3 w/ KK. Voodoo does not run on my phone. Went back to stock rom to undo tayutama's lag fix. undid it. Rebooted, got a black screen. Went into recobvery and tried to put in Bionix w/ KK, does a half install reboots gets to galaxy s screen and thats it.
I am a bit of a noob, I've flashed a couple of roms gone back and forth with no problems. I am not adb savvy, just figuring out how to get into it and start it up.
Any help appreciated,... will absolutely paypal you for a case of beer for your time and patience. I am cool calm and collected about this, I know it happens, so I should be pretty easy to work with. will definitely take this as a learning experience.
Have you tried using odin to go back to stock. Also you are going to get flamed for posting this in the dev section.
Sent from my SGH-T959 using Tapatalk
what is odin, how do I get it and get it cranking
Did you wipe/factory reset? From what I've been told, if you can get to recovery, you are not bricked... so I'd try getting into recovery, and wiping everything clean.
When you reverted to stock did you use Odin or Clockwork recovery?
EDIT: Never mind
delete user data and cache?
i used clockwork
You could also try to flash the file from Eugene's froyo that wont brick. Read the instructions sombionix posted in his original 1.3 post
Sent from my SGH-T959 using XDA App
That's not a brick. Learn what brink means FCOL
P.S. WRONG FORUM
http://forum.xda-developers.com/showthread.php?t=739091
Read through this post it will explain odin and its fickity nature.
jrkart99 said:
what is odin, how do I get it and get it cranking
Click to expand...
Click to collapse
Sent from my SGH-T959 using Tapatalk
Download this. It contains everything you need to get back up and running.
1. Make sure phone is off and not plugged into anything.
2. Open Odin
3. Select PIT file
4. Select PDA file
5. Click "Re-Partition" box in Odin
6. Hold volume UP and volume Down while plugging into the computer.
7. Phone will now be in Download mode
8. Odin should show your phone on a COM port (in yellow). If it does not, unplug the phone and plug it back in.
9. Click "Start"
Guys, thank you for your patience and tolerance. I realize wrong forum, torch me. 3.5 seconds of your time to point me in the right direction is worth the hell i'll get. Any other suggestions are welcome, and i promise to post in a more diligent manner next time. Like I said, you guys do great work, I am interested in learning this stuff but its a pretty stiff learning curve.
It is a brick. Although he should have said "soft" brick.
Sent from my SGH-T959 using Tapatalk
Just wondering, what is the difference of brick and door stop?
jrkart99 said:
Guys, thank you for your patience and tolerance. I realize wrong forum, torch me. 3.5 seconds of your time to point me in the right direction is worth the hell i'll get. Any other suggestions are welcome, and i promise to post in a more diligent manner next time. Like I said, you guys do great work, I am interested in learning this stuff but its a pretty stiff learning curve.
Click to expand...
Click to collapse
The post directly above yours tells you step by step what to do. Your phone is fine you just gotta ODIN back to stock.
flipper2006 said:
Just wondering, what is the difference of brick and door stop?
Click to expand...
Click to collapse
They are the same thing. Both are intended to mean that the device is dead, absolutely useless, completely broken, might as well throw it in the garbage, etc.
Unfortunately people have mis-used the term "brick" to describe "won't boot", "almost bricked", and "I'm an idiot" so often that it makes me want to punch babies. Luckily there are no babies present.
had the same issue but fixed it... used odin with the stock but it didn't work... tryin every restore in the book... except the Froyo version... low and behold Eugenes Froyo did the trick... it allowed me to install it and then go back to the rom of my choice... in recovery I repeatly got the error with trying to wipe data... after boot the phone would get stuck on a blank screen with the soft key lit... but (ROM) Froyo ~~~That does not Brick! Downgrading Is Fine --eugene373 did the trick... I'm not a noob but I almost called tmo, to do an exchange... Bionix 1.3 is the only rom I have ever had this problem with... It happened when I attempted to change roms via clockwork...
see i'm already learning. One less possible stupid-ass noob post from me. Learned odin, and the difference between brick, soft brick, and a baby punching brick.
Edit: I realize that, hydro, but the sheer volume of genius here, including yours i'm sure, is a lot to sort through. I want to learn, but just looking at all this info there is no good place to start, that I can decipher. Maybe a thread somewhere and how to get started, a learning section that spells it out for idiots like me. Using Odin, adb, etc etc etc. Keeps the noobs off the dev section. Years from now I hope I can been more of a contributor than a leech. Again, very sorry to put you out.
jrkart99 said:
Ok well, I finally did it. Broke my brick cherry. Screen goes black after galaxy S logo pops up. Was running bionix 1.3 w/ KK. Voodoo does not run on my phone. Went back to stock rom to undo tayutama's lag fix. undid it. Rebooted, got a black screen. Went into recobvery and tried to put in Bionix w/ KK, does a half install reboots gets to galaxy s screen and thats it.
I am a bit of a noob, I've flashed a couple of roms gone back and forth with no problems. I am not adb savvy, just figuring out how to get into it and start it up.
Any help appreciated,... will absolutely paypal you for a case of beer for your time and patience. I am cool calm and collected about this, I know it happens, so I should be pretty easy to work with. will definitely take this as a learning experience.
Click to expand...
Click to collapse
Your file system has become corrupt. Using Odin, Flash Eugene's 2.2 froyo build then flash back to the stock build. This was the only thing that worked for me.
jrkart99 said:
see i'm already learning. One less possible stupid-ass noob post from me. Learned odin, and the difference between brick, soft brick, and a baby punching brick.
Edit: I realize that, hydro, but the sheer volume of genius here, including yours i'm sure, is a lot to sort through. I want to learn, but just looking at all this info there is no good place to start, that I can decipher. Maybe a thread somewhere and how to get started, a learning section that spells it out for idiots like me. Using Odin, adb, etc etc etc. Keeps the noobs off the dev section. Years from now I hope I can been more of a contributor than a leech. Again, very sorry to put you out.
Click to expand...
Click to collapse
did you even bother checking out the thread with "bible" in it at the top of the forum?
Also, you say you realize this isn't Q&A section.....you realize people would have helped you there without wasting other people's time right?
Posts like this also serve to clutter things up and make it even harder to find stuff as well
come on man, you knew better but you did it anyways
That being said, I'm not a total ****...hope you get it fixed
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
Hello thar.
I am no stranger when it comes to flashing recovery, MAGLDR, various NAND rom's and generally faffing around - but that's because I have a HD2, and there's lots and lots of development for it.
I've been looking through the SGS2 fora for a while now and I get the idea that (as expected) things are quite new in regards to root, recovery, roms...it's just not as user friendly as the HD2 from what I can see. I'm no tech newbie but I felt things were easier on the other phone. I'm basically here to don my Noob cap once more and figure things out.
However...
I quickly want to confirm what the values are that i'm looking at, and how I apply this knowledge from my SGS2 into the XDA site so I know exactly what to look for.
So here goes:
Baseband version: I9100XXKDJ
Kernel Version: 2.6.35.7.I9100DXWKE2-CL187606 [email protected] #2
Build Number: GINGERBREAD.XWKE2
So I know i'm on KE2. I haven't installed Kies, but i'm assuming i'm due an upgrade? I'm on O2 UK.
Also, what on earth is this [email protected] Do I have root already??
Many thanks for anyone who can clear these simple questions up for me...
Trust me, it's even easier on this phone. If you just want root but want to stay on stock rom head over to the cf-root thread by Chainfire and flash the ke2 kernel in Odin. It'll give you root and CWM.
Sent from my GT-I9100 using XDA Premium App
MaBlo said:
Trust me, it's even easier on this phone. If you just want root but want to stay on stock rom head over to the cf-root thread by Chainfire and flash the ke2 kernel in Odin. It'll give you root and CWM.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Ah now you see I already understood that bit, I downloaded Odin last night but didn't have the phone til today.
I just want to understand where i'm coming from, the system values i've written out above almost imply i've got root, plus I want to know whether upgrading to KE4 should be done as standard (is it like simply going from Android 2.3.3 to 2.3.4) or is the "KE" thing very much something I should know what i'm doing before I tinker...
Not sure I exactly understand what you mean, but I'll give it a go
Afaik the "KE" thing is simply the kernel/firmware name. I think KF3 or 4 is the newest one.
You normally update through Kies if you're not rooted, but every firmware version is available from XDA. They are simply flashed by Odin, which is incredibly easy. Some roms can also be flashed by CWM if they support it.
Hope this helps and that I didn't misunderstand you.
Edit: I also highly doubt you got root, but it's easy to find out. Just perform a action that require root access.
Sent from my GT-I9100 using XDA Premium App
MaBlo said:
Not sure I exactly understand what you mean, but I'll give it a go
Afaik the "KE" thing is simply the kernel/firmware name. I think KF3 or 4 is the newest one.
You normally update through Kies if you're not rooted, but every firmware version is available from XDA. They are simply flashed by Odin, which is incredibly easy. Some roms can also be flashed by CWM if they support it.
Hope this helps and that I didn't misunderstand you.
Edit: I also highly doubt you got root, but it's easy to find out. Just perform a action that require root access.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your words. I'm a couple of steps closer to unleashing Odin on my phone.
I have gone from a HD2/Dell Streak5 combo to HD2/SGS2 combo. I wish women judged us men on the value/epicness of our phones, if they did i'd be pretty much getting it on right now.
One can dream right? By the way I was also very insecure about rooting my SGS2, everything was different from my Legend. But then I dived in and found out it was much much easier, almost foolproof I would say.
Cheers and enjoy your beast of a phone.
Sent from my GT-I9100 using XDA Premium App
"I wish women judged us men on the value/epicness of our phones, if they did i'd be pretty much getting it on right now"
reading this cheered me up
this phone is incredibly easy to mod out and fiddle with
IF YOU READ I PROMISE YOU WONT BRICK YOUR PHONE
and also make sure the cable doesnt get disconected from the phone while you are hacking/writing firmware because you WILL NOT BE HAPPY
Just follow those two rules and you will be perfect
its very easy to do stuff to this phone, I love it, have fun with yours
I'm currently on a rooted KE2.
Reinstalled the original image so I don't get the exclamation mark, but still rooted.
MyBackup Root won't restore my backups. I get the error "cannot write to SD card".
Now i've noticed there's a change of layout here with this phone. I've got sdcard and external_sd folders. Assuming the backup app is trying to write to external_sd which is literally that, the external sd card, why can't it??
I would understand if MAYBE the internal sd was locked down but even then I know it's not.
dkl_uk said:
Thanks for your words. I'm a couple of steps closer to unleashing Odin on my phone.
I have gone from a HD2/Dell Streak5 combo to HD2/SGS2 combo. I wish women judged us men on the value/epicness of our phones, if they did i'd be pretty much getting it on right now.
Click to expand...
Click to collapse
If that was the case, I wouldn't have had time to join or even watch this forum
Sent from my GT-I9100 using XDA App
Switched to GS2 from my hd2. I'm loving the lighter weight and superior screen =)....Switching ROMs is also a breeze. Hope you're enjoying your experience!
Well i've finally mastered everything I needed to. I have root but also a stock ROM, I have all my apps and homescreen the way I want and yes the lighter phone and amazing screen all make up for the next problem...
I have a pair of £120 Monster headphones and they DON'T FIT!
There's less than a millimetre of a gap but a gap nonetheless. My headphones aren't in fully and the only way to remedy the issue is either to hold them in with a finger or turn the headphone plug so it's pointing to the back of the phone - this then becomes an issue with pockets etc.
Without being able to listen to music on this phone i'm left carrying my HD2 around as if it were an iPod. Not good. Also the SGS2 doesn't recognise the vol-up and vol-down as a method to choose prev & next music tracks in PowerAmp. I'm sure the Dev is on the case though as it is a fairly new phone.
Without music i'm seriously considering selling the handset.
Have you tried pushing the plug down with some amount of force? Mine didn't go all the way down at first either, had to push it. If not you should replace it, they should fit.
Sent from my GT-I9100 using XDA Premium App
MaBlo said:
Have you tried pushing the plug down with some amount of force? Mine didn't go all the way down at first either, had to push it. If not you should replace it, they should fit.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
It's how the plug is seated. If I turn the plug so it's in line with the body of the phone i.e. pointing left or right it refuses to rest fully within the hole. There's an obvious 'spring' effect once I let go of the plug.
If I turn the plug so it's pointing away from me to the back of the phone it sits in there quite nicely. I can only put this down to either the curvature of the plug itself or the tiny little ridge at the join between the gold connector and the L shaped plug itself.
On a side note I did just ram it in there with my palm and it sat quite nicely, then I shook it around a bit (I go to the gym a lot, I was pretending to be kickboxing...) and it stayed in place. Now i'll just wait for the PowerAmp Dev to implement volume button track skipping.
Hey guys,
The problem started last night, i had no sound coming from my speaker. After some checking i found that for some reason the phone was thinking that my headphones are always connected, even if they were in the other room. I tried reflashing it, and i couldn't boot up anymore. Tried flashing new kernel, nothing. Tried flashing stock firmware, nothing. The phone won't accept any firmwares. So i tried to REPARTITION with odin. And i think i got the wrong tutorial
My phone is a gt-i9100, and i repartition it with omap4_all_20110627_emmc.pit
In odin was like this:
pit file selected
auto reboot selected
re-partition selected
f.reset time selected
And start.....all done, green light but the phone won't power on, won't enter recovery/download.
Now what?
Posting questions in the general forum = bad
Flashing an I9100G .pit on an I9100 = worse
JTAG.
JTAG won't help you, because it is not bootloader corruption. Motherboard replacement will fix it.
Sent from my GT-I9100 using xda premium
another one bites the dust
try JTAG anyway,cant hurt.
Oh your wording... too funny...
Sent from my GT-I9100 using xda app-developers app
firmware?
xSurgery said:
Hey guys,
The problem started last night, i had no sound coming from my speaker. After some checking i found that for some reason the phone was thinking that my headphones are always connected, even if they were in the other room. I tried reflashing it, and i couldn't boot up anymore. Tried flashing new kernel, nothing. Tried flashing stock firmware, nothing. The phone won't accept any firmwares. So i tried to REPARTITION with odin. And i think i got the wrong tutorial
My phone is a gt-i9100, and i repartition it with omap4_all_20110627_emmc.pit
In odin was like this:
pit file selected
auto reboot selected
re-partition selected
f.reset time selected
And start.....all done, green light but the phone won't power on, won't enter recovery/download.
Now what?
Click to expand...
Click to collapse
Did you put a firmware in the PDA section? if not go here to get one - sammobile.com/firmware
last_pawn said:
Did you put a firmware in the PDA section? if not go here to get one - sammobile.com/firmware
Click to expand...
Click to collapse
Dude, this thread was last posted in back in October before your post.
That, and it was already established he used a pit file not meant for his device, which is what went wrong.
try force download mode, you need some one to help u
pull out the battery press the home+power+vol down
let the other person put the battery back
eraser0 said:
try force download mode, you need some one to help u
pull out the battery press the home+power+vol down
let the other person put the battery back
Click to expand...
Click to collapse
I give up.
ctomgee said:
I give up.
Click to expand...
Click to collapse
lol
Sent from the little guy
Bunch of boneheads (last_pawn & eraser0 I'm glaring @ you in particular).
ctomgee said:
I give up.
Click to expand...
Click to collapse
They probably are trying to help an iS**t guy now LMFAO
Envoyé depuis mon GT-I9100 avec Tapatalk
Hi all,
so is there any progress on this issue?
I did not want to open a new thread because this thread explains exactly my situation and I am posting here because this thread did not help me.
I have since yesterday the same problem. I unfortunately also repartitioned my Samsung Galaxy S II i9100 with "omap4_all_20110627_emmc.pit" which actually is the wrong one.
(I know it is "stupid" but please do not explicitly state it in your replies, I am already aware of it.)
Is there a possibility fix this issue by repartitioning with the correct one?
Current Situation:
- My phone is not booting up
- not going into the download mode
- not going into the recovery mode
- if I plug into the PC with a USB cord, PC and Odin is not recognizing it
- if I try to charge it, I see no icon at all
- in short: it is dead
Solution I have found so far:
1- replace the motherboard
2- buy a usb jig
3- throw it away
So my question is about second (possible?) solution: if I buy a usb jib will I be able to use Odin to repartition with the right pit file? Did someone have experience or try this method?
I thank you all in advance for your replies.
Ibo
The jig more than likely won't work, but you may as well try one given they cost 1/3rd of sod all.
Option 1 tends to be the only way to fix the phone. And obviously option 3 is always possible (People who use the 'I'm going to smash it/throw it away/etc' line here tend to get ignored for the childish fools they are. We don't care what you do with your phone).
Edit -Yes, using a wrong PIT is the height of stupidity. Despite thousands upon thousands of warnings here/elsewhere not to touch PIT's unless you have a very specific reason for using one (0.000000001% of cases, you were not one of those people), people still do it.
MistahBungle said:
The jig more than likely won't work, but you may as well try one given they cost 1/3rd of sod all.
Option 1 tends to be the only way to fix the phone. And obviously option 3 is always possible (People who use the 'I'm going to smash it/throw it away/etc' line here tend to get ignored for the childish fools they are. We don't care what you do with your phone).
Edit -Yes, using a wrong PIT is the height of stupidity. Despite thousands upon thousands of warnings here/elsewhere not to touch PIT's unless you have a very specific reason for using one (0.000000001% of cases, you were not one of those people), people still do it.
Click to expand...
Click to collapse
Thanks for your answer. I thank you just for the part where you have written "Option 1 tends to be the only way to fix the phone.". This was enough for me to hear considering your experience in this forum. For the rest:
1: What would you do if your phone is not booting up and shows the Samsung logo even you wait 1 hour? Assuming that you already used options in recovery mode and also used Odin to update PDA several times?
2: Then you found a tutorial which says this is for Samsung Galaxy S II no further specifics given other than I9100.
3: Different people have different sense of humor so I do not blame them when I see in many forums where they write throw it away. I think it does not make sense to overreact to such suggestions. For example I just laughed when I read something like this.
Best,
Ibo
1) If I'd tried everything (and I mean everything, over and over and over), I'd assume the NAND is stuffed, bite the bullet & have the motherboard replaced one way or another. I'd either find a 2nd hand one & have a local mobile repair shop/not an authorised Samsung repairer replace it for me, or if I couldn't find one I'd pay an authorised Samsung repair to put a new one in. Or I'd get a new phone.
2) Before I got my phone I did a lot of research/reading/learning. For over a month. When I got my phone, I did even more research/reading/learning. I didn't jump blindly in messing with my phone without knowing what I was doing. If I saw some dodgy tutorial that told me to use a PIT when everything else I'd read said not to touch except for a very specific situation, I wouldn't touch a PIT unless I was in that very specific situation. Knowledge is power & stops you doing silly/desperate things. It's like putting your hand on the stove when you've already learned you'll get burnt if you do.
3) I'm glad you found what I said amusing. That probably speaks to why you broke your phone in the first place. I was deadly serious. From where I sit, a $700+ piece of electronics is too important to me not to take its continued proper functioning very very seriously. I realise some people get a new phone every 6 mths or whatever or don't care. To me, that's wasteful.
Edit - If you're able to have it assessed cheaply/for free, it might (again, less likely than more) even be JTAG'able, but I wouldn't be spending a lot of money up front having it looked at given it's likely not to be.
MistahBungle said:
1) If I'd tried everything (and I mean everything, over and over and over), I'd assume the NAND is stuffed, bite the bullet & have the motherboard replaced one way or another. I'd either find a 2nd hand one & have a local mobile repair shop/not an authorised Samsung repairer replace it for me, or if I couldn't find one I'd pay an authorised Samsung repair to put a new one in. Or I'd get a new phone.
2) Before I got my phone I did a lot of research/reading/learning. For over a month. When I got my phone, I did even more research/reading/learning. I didn't jump blindly in messing with my phone without knowing what I was doing. If I saw some dodgy tutorial that told me to use a PIT when everything else I'd read said not to touch except for a very specific situation, I wouldn't touch a PIT unless I was in that very specific situation. Knowledge is power & stops you doing silly/desperate things. It's like putting your hand on the stove when you've already learned you'll get burnt if you do.
3) I'm glad you found what I said amusing. That probably speaks to why you broke your phone in the first place. I was deadly serious. From where I sit, a $700+ piece of electronics is too important to me not to take its continued proper functioning very very seriously. I realise some people get a new phone every 6 mths or whatever or don't care. To me, that's wasteful.
Click to expand...
Click to collapse
1. It is nice to hear that in any case the motherboard should have been / be repaired. You are right that was an expensive try but even if didn't I had to let the motherboard repaired. It was written the same thing as you said: the motherboard should be repaired so why not try this option: yes awful but if you have no other option and you tried really everything, you just give it a try.
2. I have been using this Samsung Galaxy SII since a couple months after it is first launched (mid 2011) and did not have any problem so far, so I did not have any interest or reasons to learn about flashing or any advanced methods.
3. Sorry there is a misunderstanding there. I found amusing not you have written but when I saw on an android forum where they written whether let the motherboard repaired or throw away/sell parts and buy a new phone instead. This "piece of electronics" is too expensive not only for you, I think for many people including me. That is why I posted here before giving 125€ to an authorised Samsung repairer.
Best,
Ibo
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
MistahBungle said:
Edit - If you're able to have it assessed cheaply/for free, it might (again, less likely than more) even be JTAG'able, but I wouldn't be spending a lot of money up front having it looked at given it's likely not to be.
Click to expand...
Click to collapse
Thanks for the tip. :good: I am now searching for it.
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