Database Info

[Q] Rooting SGS2 GT-i9210

I just got a brand new SGS2 GT-i9210 from sweden. After unsimlocking it, it perfectly works on our experimental 4G (2.6Ghz) network in France.
I tried to root it, but the zergrush doomlord rootkit v4 does not work properly, it ends with the "Hellions with BLUE flames" error.
I used this rootkit with different SGS2 4G/LTE smartphone and never had problem, it always worked.
I was just wondering if someone could help me to root this GT-i9210...
Thanks in advance for your replies

I'd love to get into this as soon as I've got rid of the Tele2 simlock on my i9210. Any tips on reliable unlock code providers for this phone?

As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
Edit: Probably better to link to the OCAU thread http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584

xrobau said:
As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584
Click to expand...
Click to collapse
I don't dare to belive you.
The root method you refer to in your link is for models sold on the US market, in Europe this model is branded GT-I9210 (EU) and is similar, but not identical to the models in US or Canada.
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
I wish somebody could fix a reliable root method for GT-I9210.

I'm the guy who wrote that post on Whirlpool. I have a pair of GT-I9210Ts, both of which are now rooted using CWM and superuser.zip.
Note that this doesn't actually CHANGE anything on the phone. So it's not going to brick it. All it does is install CWM, and then uses CWM to install superuser.zip. I can't possibly see how it's possible to brick the phone doing this.

F5:ad said:
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
Click to expand...
Click to collapse
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?

That's.. very very strange. Someone else reported it, but I have no idea why this happened. You're not touching ANYTHING to do with the buttons. All you're doing is updating the recovery.img and then installing a package. I've rooted three phones now, and haven't had that problem.
Can you read http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218 and tell me if you did anything different?

briteway said:
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?
Click to expand...
Click to collapse
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\

xrobau said:
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\
Click to expand...
Click to collapse
The method you have posted is one I have already tried, 2hrs after getting my phone from Telstra. Back button and Menu buttons blank out and no longer work.
No one should use this method until it is specifically tried and tested for the phone.
EDIT: Just to assist you a bit further with the method.
- A full factory reset was completed, not working.
- Telstra firmware downloaded, installed, factory reset, not working.
- Dialled *#*#2663#*#* - Selected Touch Key F/W to upgrade, not working.
----- Phone F/W was marked as 0x4, Part F/W was 0x0.
I believe this was the issue, the fact that there was a number mismatch.

Those with the GT-I9210 visit this link for Original EU Rom.
www"dot"sammobile"dot"com
As I mentioned on OCAU, I didn't have much of a problem.
"xrobau" Did you have any moment when the buttons did not work?

Hi,
Any updates on this phone rooting procedure?
This generic firmware will work in Portuguese operators? Any European tested it?
Thanks
Sent from my GT-I9210 using XDA

It's in Portuguese. Translate with Google. A friend of mine did root gt-i9210. I've used this method to root mine.
http://stuffandroid.blogspot.pt/2012/04/como-fazer-root-no-samsung-galaxy-s-ii.html
Sent from my GT-I9210 using XDA

In my case the keys stopped working after flashing first time a kernel with cwm recovery. The phone also didn't boot anymore. The kernel itself was backuped with the very same cwm.
Before I flashed the kernels with odin and also with "dd" command. No problems with the keys.
Based on these things I got the feeling that there could be something wrong with cwm.
I could not fix it so far.

I'm not sure whether my post would be valid any longer on a thread more than a year old.
Anyway, if someone needs a pre-rooted version of the latest stock Jelly Bean 4.1.2 XXUAMF1 COV (GT-I9210), they can do so from this thread, post #4:
http://forum.xda-developers.com/showthread.php?p=34712551
Flashed it via Odin & using it without any issues on my S II LTE GT-I9210T.
Jp
:good:

[Q] Flashed to cm-10.1.0-d2vzw.zip, Now The Camera Doesn't Work.

Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10

Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1

CZory91 said:
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
Click to expand...
Click to collapse
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.

Sythrix said:
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Click to expand...
Click to collapse
Well. Good and bad news. Good news is it's fixed. Bad news is there is no way that I can find of updating the firmware/modem while running an AOSP ROM. The first try worked great, wanted to see if I could update the firmware, no go. Restarted from the beginning again to see if taking the OTA updates while not rooted would allow me to have it work when rooted. Updates went through, everything went fine. Camera didn't work on AOSP still. So at least it works... I can deal without the firmware I guess, definitely worth a working camera and fully stable CM10.1.
Had some issues with the root, however a few tries at it and it eventually worked. This requires no input on your screen (first try SU popped up on me and I granted access, it rebooted and didn't root correctly) Edit: This time around I granted it and it worked. Heck if I know what/why. Just just keep doing it until it works, worked for me. Don't press anything the first try, then do so the second, etc.. Start it as soon as your device is connected to your computer and let it do it's thing. Don't let it have the chance to switch from its "installer" mode on the phone to a media device (unsure if that was the problem, but that seemed to be the reason why after the second round, 4th attempt).
Also, I had to battery pull and wipe data on the stock recovery listed as optional on the first link after it was rooted (WAIT UNTIL ODIN SAYS PASS before pulling the battery out when it's at the boot logo).
The only other thing I would say is that my phone initially came with the VRBLK3, and that may be the reason why this worked for me. Don't know. If your phone shipped with a different version, and my process doesn't work for you, try finding an MD5 with your shipped firmware version that will odin you to that version, and then continue with the root.

This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip

Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.

Sythrix said:
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Click to expand...
Click to collapse
It's in the first post on both CM10.1 threads (Q&A and Developer forums).

Sythrix said:
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Click to expand...
Click to collapse
Props on providing all that data with your question.. wish everyone was as thorough as that when needing help..
Sent from my Nexus 7 using Tapatalk 4 Beta

Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Did not and still does not work for me.
Sent from my SCH-I535 using Tapatalk 4 Beta

[Q] Rebbots, No Boots, and other power issues

Alright, so I need a little help here deciding what to do next.
My girlfriend has the SGH-T959v with android 2.2.1 on it.
It had been randomly shutting down when the screen turned off. It was much the same as the Samsung Captivate had its issues.
It also wouldn't charge sometimes and would also not turn on unless the battery was removed.
Well, I replaced the battery with an OEM one from a mobile store.
Now there are no more random shutdowns but there's a whole slew of different issues.
If the phone is turned off you have to remove the battery, put it back in, plug it in quickly, and then turn it on.
If the phone charges too long all the signal stops working until a reboot.
The phone always thinks it's charging even when the battery is draining.
It's a pretty irritating problem especially with the reboot issue because if we're out and away from electricity and it gets turned off accidentally then there's nothing we can do till we get back to the charger.
Has anyone had these issues and solved them with a new ROM?
I had the random shutdowns on my Captivate and solved it with CyanogenMod. I'm thinking about flashing but I don't want to wipe it all and then have it not work or brick the thing (it is unlocked on Straight Talk so I also don't want to relock it to T-Mobile)
Some foresight would be appreciated before I move forward with it.
Thanks

Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.

Yes, flashing a better ROM will help in certain cases

pisherthefisher said:
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Click to expand...
Click to collapse
Actually my question was whether or not anyone has had this issue.
I'm trying to see if it's a known firmware problem or a known hardware problem so I don't waste my time.
I don't have all day everyday to backup the phone and flash and test and then reinstall all the apps.
Thanks for the contribution though.
That being said would anyone suggest a TW ROM for this? I don't want to change the functionality because she's used to TouchWiz and not tech savvy

Now I must throw in, you should search around for a TW styled ROM. I don't know if we have one or not, but I can tell you that looking yourself will be a lot quicker then waiting for somebody to feel sorry for you, search for it, and give you a link to it.

Ignore those guys. Dont flash a custom rom YET.
http://forum.xda-developers.com/showthread.php?t=1822626
Read that post follow the directions. I suggest reading the thread it links to while backing up the phone. Then while actually doing the flashing with heimdal follow it.
Now be sure to follow eollies directions of flashing the kernel after the initial boot or wifi will be broken.
This will wipe her phone out and reflash everything plus give you root access to remove bloat and add things like titanium backup.
---------- Post added at 07:49 PM ---------- Previous post was at 07:37 PM ----------
Whoops looks like eollies pulled the file from dropbox.
Just follow the directions in the thread by lumin30 that eollie links too.
I forgot to say why I suggest using a one click. This device sometimes just needs to be reset to factory. And Using a one click will remove all stuff not suppose to be hanging around.

Here's another one that I find much more simple.
Heimdall One Click back to Stock for the T959V

I have the grimlin remover one click on my computer I can upload it later

Cooptx said:
I have the grimlin remover one click on my computer I can upload it later
Click to expand...
Click to collapse
I have it also, but cant get it to upload for whatever reason. So.....
Here's the link: http://forum.xda-developers.com/showthread.php?t=1500427 Post #41 has a working DL. get it, unzip, run it. Maybe it helps him.

Use the heimdall one clicks they are 2.3.3 stock touchwiz. Like I said follow lumin30's guide to the letter. He is a recognized contributor for a damn good reason. That guide has also been featured on the portal. I would flash the antonx kernel after for root and then flash bhundvens latest kernel. This will allow just a bit more control and troubleshooting if something happens.

Alright, I was just throwing it out there xD

Really guys? You're not even answering his question and linking him to old guides that are complicated. If someone needs to go to a stock KJ6 rom just link them to lumin's guide!
Anyway, I doubt you will find anyone on these forums who are still running the 2.2.1 stock rom, I personally haven't run it in over 2 years when I first bought my phone.
Samsung has released an official update from Froyo (what her phone is running) to Gingerbread (the last officially released version for this phone).
I recommend you try that, but know that there is a long-sms bug. If you go over 140 characters the message will get cut off and you will get a "message sending failed" notice when you try to send it. You can instead try to use a 3rd party app like handcent or gosms that will split the message for you if it goes beyond 140 characters.
If you would like an easy to follow, reliable guide WITH PICTURES, then go ahead and follow lumins' guide:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Just remember that everything on her phone will get wiped, but you can use google to back up contacts. It sounds like it'll be worth it.
Again, lumin's guide will allow you to upgrade her phone to the last official rom Samsung released for our phone.
Good luck!

I wonder if Samsung kies is still upgrading.

[Q] LIkely a idiot noob question, but I dun goofed and idk how ot fix it...

Basic rundown, I bought an HTC One M8 on tmoblie yesterday, coming off an iphone 4. I've heard you have have have to root your android devices, so that was one of the very first things I did. Shortly after, I was trying to figure out exactly what I could do with the root, and decided to flash a custom ROM. I tried the Google Play edition posted on the dev section of this same forum. Everything worked as planned, except for one huge problem: my data no longer works. I can connect to wifi fine, as well as send texts, but no 4g lte access anymore. Idk if this is a common problem, if I'm doing something simple wrong, etc. I made a backup in TWRP, and saved it to my desktop, and tried restoring my phone to see if that would help, but I must have dne something wrong there too, as it doesn't show any files when I try to restore under TWRP.
I would greatly appreciate any and all help or tips. I'm new to the android rooting scene and should have taken it more slowly. I thought I had done sufficient research, but I guess I ****ed the pooch somewhere along the way. Thanks in advance.

watchmuu said:
Basic rundown, I bought an HTC One M8 on tmoblie yesterday, coming off an iphone 4. I've heard you have have have to root your android devices, so that was one of the very first things I did. Shortly after, I was trying to figure out exactly what I could do with the root, and decided to flash a custom ROM. I tried the Google Play edition posted on the dev section of this same forum. Everything worked as planned, except for one huge problem: my data no longer works. I can connect to wifi fine, as well as send texts, but no 4g lte access anymore. Idk if this is a common problem, if I'm doing something simple wrong, etc. I made a backup in TWRP, and saved it to my desktop, and tried restoring my phone to see if that would help, but I must have dne something wrong there too, as it doesn't show any files when I try to restore under TWRP.
I would greatly appreciate any and all help or tips. I'm new to the android rooting scene and should have taken it more slowly. I thought I had done sufficient research, but I guess I ****ed the pooch somewhere along the way. Thanks in advance.
Click to expand...
Click to collapse
Try the Tmobile M8 forum

[Q] In need of modem drivers?

Hello everyone
I was on 44S and then updated to 05Q. Then, I flashed official nighlies and was on nightlies for a few days. I just flashed them and nothing else. I wanted to return to stock because of SMS issues, and I used this tool: TOOLBOX
I used v5. The download links weren't working on xda but I tried somewhere else and found a link to v5. Anyway, I used that, and now I'm back to stock. However, my reception has been spotty. Not only at home, but now where I'm studying too. I haven't been here for a month, but now that I am back here again, I definately notice a difference... Could this be because of modem drivers? What do you guys think I should do? If the toolbox is incomplete and doesn't flash everything needed when going back to stock, what should I use then?
Thanks in advance

Why are you using a toolbox in the first place? It really isn't needed, and as you've found out they're more trouble than they're worth. Go and follow the instructions in section 8 of my guide thread to flash the stock images.

timmaaa said:
Why are you using a toolbox in the first place? It really isn't needed, and as you've found out they're more trouble than they're worth. Go and follow the instructions in section 8 of my guide thread to flash the stock images.
Click to expand...
Click to collapse
Will do. Thank you for the help. I did see your thread, but rejected it because of having to use adb commands... (Lazyness, basically). Well, I learned my lesson. Thank you once again for helping me, I'm going to follow your thread!