Its been couple of months I am trying to root my Galaxy S2 I9100G which was bought from China. I made deep research on XDA Forum to find any easy method! Several threads out there. At first I tried to follow this thread
The above thread founded helpful for maximum users with any problem. I tried by the provided steps with their "Superatmos (version 2.1 is very stable and recommended)" Kernel.....And it worked...rooted...but vibration function was disable (other users also had this type of problem). Then tried also to check hardware of my phone and everything was fine..I was keep looking for solution and someone on that thread said to "Flash Again With Original Stock Kernel". Well then I flashed again with INDIAN Stock Kernel...........and the result------ my phone was not booting up, only the Yellow Triangle was showing with Samsung Logo. I was just to pull my hairs when I found that many other people had this type of problem and the reason is HARD BRICKED..!!!!
Luckily my phone was restarted in download mode, and then I flashed again with "Superatmos_v3.0_XXLA1" Kernel. and voila! it restarted, booted, rooted and vibration was working again....!
Please note- Binary counter / Yellow Triangle will show. please check this pdf file by the thread-owner --http://db.tt/BwlUTGIl
The only reason for sharing my details above by thinking, its possible that other users may have this kinda problem. so this thread would be make them to relax a little bit. Now below I am repeating the steps for Rooting a Chinese Galaxy S2 I9100G with links. (Followed to Paras Lehana's original thread http://forum.xda-developers.com/showthread.php?t=1570377)
1) Download Odin and install -- View attachment Odin3-v1.85.zip
2) Download this Superatmos Kernel file -- View attachment superatmos_v3.0_XXLA1.tar Believe me it will work any problem. You may try other version, but I Superatmos ver 2.1 which is recommended most wont work...anymore.
3) Go to Download Mode : Turn off phone. Hold vol down+home+turn on button. Release the on button after phone is turning on. After a few second, release all buttons. After that vol up.
4) Run Odin, connect phone with usb cable, yellow COMx will be shown in Odin. (Re-partition should not be ticked (no pit file is required here)
5) Select PDA button, choose the downloaded kernel file (usually a .tar file)
6) Click Start, a PASS will be shown if succeed.
That's it. you are rooted. please check other guidance for CWM Recovery / Super User / Remove Triangle / Binary Counter etc. on the thread-owner's pdf file.
Note: Users who don't wanna flash their Chinese ROM with any other but still wanna access Google/Play etc. they could follow above steps. And after rooting please follow this thread --- http://forum.xda-developers.com/showthread.php?p=29464673
Also users may follow below steps for replacing their Chinese ROM to Any Other.(After ROOT)
This method requirement is root access and Mobile Odin Pro only. Even if the phone are rooted with doomlord’s method and you chose not to have CWM support, it will work too
1) Download the stock firmware and copy it to the root of sdcard (internal). “tar” and “tar.md5”will be supported also.
please check on Sammobile for stock frimwares.
2) Install Mobile Odin Pro
you could search on google for Mobile Odin Pro to get shared pro version file.
3) Run the application and from “Open file …” select file that you just copied into the phone
4) If Everroot option is not ticked itself, please tick it if you want the phone to be automatically rooted during the process
5) I will recommend to tick all three options inside Everroot
6) And also please ticked the wipe data option but it is optional, but can reduce any bugs
7) Start the flashing
8) Result : root access, no CWM support, no busybox
Followed the original post----http://forum.xda-developers.com/showthread.php?t=1570377
I just wanted to associate together all required steps posted on XDA by some real professionals. So it will be easier for those people who is still searching on for Rooing Methods for Chinese Galaxy S2 I9100G.
Thanks
tried it, but couldn't get it to work
Thanks for that.
I have an SGS2
Model number GT-9100G
Android version 4.04
Baseband version I9100GZCLPL
Kernel version 3.0.8-1067026
Build number IMM76D.ZCLPL
On download screen
PRODUCT NAME: GT-i9100G_CHN_CHN
*#1234# gives
PDA: I9100GZCLPL
PHONE: I9100GZCLPL
CSC: I9100GOZHLPL
Build Info: Fri Oct 5 14:28:15 KST 2012
I tried flashing with the 3.0 XXLA1 tar as above and when the phone reboots it gets stuck on the first Samsung screen.
I can't get the old superatmos 2.1 kernel anymore (the "very stable and recommended' version) because the file has disappeared from Mediafire.
The old link was http://www.mediafire.com/?14qqbaw311b3wpm
I also tried 2.1.1 and 2.2 from http://www.android-hilfe.de/2869772-post2.html ... and I think 3.2 as well. They have the same problem.
I was a bit scared but downloaded the old I9100GOZHLPL file from
http://sampro.pl/firmware/android/samsung-i9100g/
and put the .tar.md5 file in the "PDA" box, clicked Start and that always takes it back to where it was (ie working again!).
I read through lots of threads here and followed all the little small instructions: USB debug mode on on phone, PIN off, KIES uninstalled on computer, no SD card. But battery and SIM card still in. The only bit I didn't follow was the "you have to install v1.0 first" advice from http://forum.xda-developers.com/showpost.php?p=22421729&postcount=150 because it wasn't in this post. And of course I would like to repeat what you did _exactly_ by getting the 2.1 kernel but can't find it anywhere anymore.
A Chinese page at http://zhidao.baidu.com/question/510191290.html talks about SuperOneClick working but I haven't tried it.
Another page at http://androidforums.com/galaxy-s2-...37-galaxy-s2-gt-i9100g-all-things-root-4.html talks about a ROM that works on all phones except the Chinese variant
Any suggestions?
Hello! So after some research in the forum, and seeing that it can be "easy" to root your phone, even with a locked bootloader, I decided to look into doing this with my Verizon Galaxy Note II to get familiar with custom ROMs. I had been running on 4.1.2
Please redirect me to relevant forum information for DIY or feel free to contribute any help below. Also, feel free to shame me for not finding it myself, as I couldn't find it myself.
I used "NoYouVerizon-GalaxyNote2-Casual R515" to root my phone and about 5-10 seconds through the installation it errored out and showed "Disconnected". It stated that I needed the relevant drivers from Adam Outlet which I accepted to download, but I did not re-recognize my phone afterwards while in the download screen. But, since it error, I get the incompatible firmware yellow triangle of frustration. I can't seem to use any software such as Odin, most likely because my bootloader is still locked?, so I'm going to ask you experts for help while I research a way to get it out of this mode.
Edit: Also, I have the issue where Odin states "Can't open the serial(COM) port" which causes a failure. Attempted to flash root66_VZW_Stock_etc
Edit2: Was a Samsung Kies issue. Uninstalled and able to start root66 on Odin. Processing now
Edit3: Was able to wipe/reboot in recovery mode to get back to stock. Now I'm curious of why Casual had the error. Any suggestions from the error file uploaded?
Edit 4: I have my phone back up and working with root access. Though I'm unsure how I have root access without doing much to unlock the bootloader from verizon, I guess this works. Any commentary welcome.
Any help would sincerely, 100% be appreciated!
Can anyone help me unbrick my phone? I can't seem to get anywhere with steps to create debrick.img file that works with my device. I rooted my device and some went wrong at a restart and now all I get is a black screen. I can't get anywhere with recovery. I have tried odin to flash stock rom without any success getting device to accept any downloads.
You can see this blog post for unbrick your phone :
http://unbrick.itcse.com/unbrick-soft-bricked-at-t-samsung-galaxy-mega-sgh-i527/
I recently attempted flash a ROM onto my Tab3 SM-110 using TWRP, flashing that on using a .tar.md5 file which was compatible with the device. For some reason I've encountered a screen which informs me that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again," When I attempted to flash the .zip using TWRP. I don't know if this was because the ROM was incompatible, or if it simply ran out of power before it finished, as I wasn't there to watch it. So, following the helpful instructions that the device gave me, I installed Kies. It told me that my device wasn't supported, and Emergency Firmware Recovery doesn't find the device either.
I then moved to Odin, finding the firmware for the device on Sammobile. It was the correct software for the device, and I attempted to flash it on using Odin v3.12. The program gets stuck as File Analysis, and doesn't do anything until the battery of the tablet runs out and then the screen constantly turns on and off and continuously connects and reconnects. I searched the internet for this issues, and I've tired things such as waiting to plug in the device until Odin loads the .tar.md5 file completely, checking Re-Partition in the options, and attempting to reinstall the driver. I've tried putting the file in the AL, BP, CP, and CSC sections all at the same time, and individually; Nothing seems to help. The file from Sammobile was the Canadian T110UEUAOD1_T110XACAOD1_T110UEUAOD1_HOME.tar.md5, as I bought the device in Canada.
I've even tried setting up ADB and attempting to reboot the tablet into Download mode as another forum instructed. ADB couldn't find the device, and I was stuck there too. I did everything required for the setup, including downloading the entire thing from SDK and setting the environment variables on Windows. ADB does work on my Samsung S5 phone, so it isn't an issue with ADB itself, but with the tablet.
This is a relatively new buy, and thus I really don't want to loose it. I've been trying this for about a week now, and I'm open to almost any suggestions. I've also tried changing computers, changing ports, using official Samsung chargers, etc. If anyone knows anything, even if you regret to inform me that I cannot save the device, it would save me the stress of staying up well into the night searching desperately to fix it. The device cannot boot out of this message, which means no recovery, download, or any other type of actual booting; I've tried removing the battery to prevent the screen from popping up. I'm also given limited time with Odin, as the device doesn't want to charge when plugged into anything but an official Samsung Adapter, and thus I can't spend hours with the tablet connected to the computer.
If this helps, although I'm not exactly sure if it would, here are some specific numbers and information that is listed around the device and on the screen:
Product Name: SM-T110
Current Binary: Samsung Official
System Status: Custom
H/W Version: 0.2
IC: 649E-SMT110
FCC ID: A3JLSMT110
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!