[Q] Attempting to install custom ROM - Galaxy S III Q&A, Help & Troubleshooting

Hi everyone. I've had my I9305 for about a year now. When I got it, I rooted the phone. Now, I've been out of the rooting/custom ROM scene since then, and I'm trying my best to figure out how to do what I'm trying to do.
I want to make CyanogenMod my OS. After much researching and googling I've learned that the best way for me to continue is to restore my device to stock condition and start from scratch. This is after trying to boot into Download mode and trying to flash Clockwork Touch 6.0.3.1 .
Note: I've made sure all my connections are good, attached the USB cable to the back of the motherboard (no USB hubs) and tried different USB cords. The phone is fully charged. No SIM card or SD card in the device.
So far I've tried using Heimdall 1.4RC2 to flash CWT. It proceeds very quickly and does not show a blue progress bar on the phone.
I then tried to use ODIN to flash the stock recovery. That one also proceeds very quickly and does not show a green button until I remove the device from the computer.
Now, I can no longer boot the device. I get as far as the first Samsung logo and after half a second it disappears and turns off.
It might be valuable to note that I cannot boot into recovery mode. When I press the button combination I get the blue dialog above the Samsung logo but it disappears in half a second and the device appears to turn off. The reason I say it appears to, is because the screen turns black and the power button no longer turns it on until I remove and replace the battery.
Good news is I can still boot into Download Mode.
I really do not want to continue at this point because I am too afraid of bricking the device.
The phone is not vital, as I've bought an LG G2 to use as my main device and will not be rooting or fooling around with it.
I would more or less like to use this Galaxy S3 as a teaching tool.
I hope I've provided enough information and hope someone can be a guide for me!
Thx to all,
Mike

Hey,
Sounds like you are having a driver issue on your pc.
1. Charge your phone!!
2. Assuming you are using windows, try google for i9300 usb drivers. After installing flash philz recovery via odin and try to reboot to recovery.
Good luck!

Or you could install Samsung Kies to get the USB drivers.
Also, don't forget to turn on USB Debug mode in the developer settings.
A good resource I found when trying to root and install a custom recovery was Android Geeks. They have many tutorials. (disclaimer: I am not affiliated with Android Geeks at all)
I recommend you to root and install a custom recovery using ODIN. I've done precisely this, and I use CWM and have no problem. I've tried many roms and it works like a charm (currently on Temasek's 4.4 ROM).

>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .

JJEgan said:
>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
This is where I am confused... After reading all of those two posts I'm still unsure about what to do.
I cannot boot into my device and therefore can not install proper drivers or enable USB debugging.
I have went ahead and installed "Samsung Galaxy S3 Unified Toolkit v7.0.0" to try and guide me along this complicated process.
After following the instructions given by the toolkit (to a tee) I am unable to get a serial number at the top of the menu, and therefore cannot continue with that program.
So is the first step in this whole process getting the recovery to work? If so, where should I start since I cannot even boot into it nor talk to my phone properly with my current drivers.
The only thing I have working right now is Download Mode.
The screen shows the following text:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
I am unable to find the answer to my problem at this point...
If someone needs more information in order to help me don't hesitate to ask.
Thx everyone,
Mike
NOTE: I tried using the recovery.img file included with the above mentioned toolkit with Heimdall and I was able to successfully boot into recovery mode. I did a data cache reset and also a factory reset but I am still unable to boot into the android OS.
NOTE2: I downloaded the stock rom for my device, which I later found out was codenamed d2att or SGH-I747. Mine is actually the Canadian Bell SGH-I747M. Roms for the d2att still work on my phone though. So I flashed the ROM using ODIN after I installed the drivers using the zadig.exe file included with the Heimdall package. The flash worked like a charm. When my phone rebooted it immediately booted into recovery with some errors in red (those of which I can't remember). When I rebooted my device shows the glowing Samsung logo and stays there. It does not load into the OS.

u should search "softbrick" thread I think
thats happen to me in my first experience installing custom roms, in xda dont worry if u're phone softbrick or hardbrick. because there's answer in every problem u have. search search search, dont give up man!

ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M

JJEgan said:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M
Click to expand...
Click to collapse
My bad, I only found out half way through what phone I actually had. I will post in the right forum.

Related

Tested method for rooting Chinese Galaxy S2 I9100G

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?

[Q] GT-i9100 Bootloop & Device not recognized

Hey guys,
a friend's Galaxy S2 (GT-i9100) hangs in a boot loop after updating Android (she says). She asked my if i could rescue her photo's, contacts, etc...
Booting Phone to Download-Mode works, connecting then via USB Windows 8 device manager prints USB\DEVICE_DESCRIPTOR_FAILURE as Hardware-ID.
There's no custom ROM installed, the device is not rooted and there's no CWM installed.
In Download mode, there's no option to "apply update from external sd card".
Tried "wipe cache partition", still boot loop.
Any ideas?!
EDIT:
I've tried to use/install various drivers. But IMHO if there's no Hardware ID / Vendor ID in the Windows Device Manager, Windows can't decide which driver matches for this device. So, if there's no device driver loaded, there's no chance for Odin or adb?! Correct me if I'm wrong.
Same as everyone else who's trying to do an Odin flash & having problems; Hopper8's 'Odin troubleshooting' thread stickied in General - go through the troubleshooting steps methodically (pay particular attention to the ones that relate to connectivity as that's the problem you're obviously having). Don't be surprised if your only option is to use another PC though given previous instances like yours I've seen.
Also, why would there be an option to 'update from external sd card in download mode ? You seem to be confused between it & recovery.
Download mode is very 'low level'; the only option you have is to get a stock rom from Samfirmware & flash it with Odin. This may/may not fix the problem. If it does, no data will be lost. But it's quite possible you may need to do a factory reset after the flash to fix, or even in some cases, flash the 3 part firmware linked in the thread I mentioned - in both cases this will wipe the phone.
Yes, you're right, i've mixed up Download & Recovery Mode. But i hope you know what my problem is.
Tried these steps (although another laptop using Windows 7), but no success.
I have another GT-i9100 which is successfully recognized by Windows 7 & 8 using Odin v1.85.
Is here any chance to extract / backup the user data from the device?
Btw:
If I boot it in Reocvery Mode, and choose "apply update from sdcard", it's possible to browse through /storage/sdcard0. It's soo depressing to see the user data and have no chance to backup them :silly:
Unless you either get a stock rom on the phone or get the phone & PC to connect to each other so you can maybe use ADB to pull the data, you have no other way to access that data.
If after trying everything in that thread for a day or two & you still have no joy, I'd be looking at replacing the USB board in the phone (you mentioning another I9100 can connect to the same machine just fine makes me suspect this might be the cause). This is a more & more common fault with the I9100 as the period since it was released increases, and this will absolutely cause the connectivity issues you're seeing. Unfortunately, you don't really have a way to test for this definitively, best you can do is replace it & see if if works.
However, fortunately, this is easy & cheap (~US$10) to do yourself. If you decide to go down this path, search for KeithRoss39's guide in General (search for 'replacing USB charger board'/similar). This guide has all the info you need to get it done painlessly.

Stuck in Early Stage of Chainfires' Root Canal

Hello to all,
This is copy of HELP post i added on --[GT-I930x/T/N][SHV-E210*][SHW-M440S] CF-Auto-Root--. It appears that forum is not active anymore. HOPE YOU CAN HELP ME SOLVE MY MINOR PROBLEM:
Dear Doctor,
I really wanted this [THE ROOT] to work on the first go, but as i learned in kindergarten: A noob stays a noob. At least for a while.
In ODIN, after I did EVERYTHING Master Chinfire said to do, I hit "Start", but the proccess stops and says "Succeed 0/ Failed 1".
So i couldn't finish with the download
+
I can't figure how to attach a screen shot of th error for you.
Please help,
TNX
P.S.
I have tried to ro read different posts on the subject but never found a problem similer to mine. The only solution people offered was to download SuperSU directly through the phone. But in order to do that, i need to open a google account, which is one of the reasons i wish to root the phone on the first place.
What is the phone's model number? Boot into download mode to find it.
audit13 said:
What is the phone's model number? Boot into download mode to find it.
Click to expand...
Click to collapse
When i enter download mode, it says:
ODIN MODE
Product Name: GT-I9300
Custon Binary Download: No
Current Binary: Samsung Official
System Status: Official
Flash twrp to the phone: https://twrp.me/devices/samsunggalaxys3internationalexynos.html
Flash supersu using twrp to get root: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Can someone share a link to stock firmware. Cant seem to find it anywhere.
Did you check sammobile.com?

To all the SAMSUNG/ANDROID GRANDMASTERS out there.

Greetings,
Both my devices are stuck in bootloop but they are facing different issues; details are as followed:
Devices Information:
- Manufacturer: SAMSUNG
- Devices Model: SM-J200GU
- Devices Nickname: j2lte
- Region: XME
- Firmware: J200GUDXS3AQG2
- Baseband: J200GUOLB3APC1
PC info:
WIndows 7 Ultimate SP1 with latest updates
Java 8 Update 144.
______________________________________________________________________________________
I know there are thousands of similar threads, most solutions I found were "enable USB debugging", "use ADB Fastboot", "reinstall drivers" and so on but trust me, I've tried every single options I could; few of them are:
REINSTALLED both Android and Samsung USB drivers (from version 1.3.8.5 to 1.5.6.3), whether you mean both installed together or separately
REINSTALLED Minimal ADB and FASTBOOT (1.3, 1.4, 1.4.2, 1.43)
TRIED using different versions of ODIN. (v1.85, v3.09, v3.10.6, v3.11, v3.12)
_____________________________________________________________________________________
Issue for Device #1: PC UNABLE TO DETECT DEVICE
Screen Options: Stock Recovery, Bootloader, Bootsplash/Bootlogo
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
I have tried 3 different cables from SAMSUNG OFFICIAL, Lenovo and another off-market (REMAX) respectively on all the 8 USB PORTS that I have, and yes I have reinstalled the USB PORTS and also DISABLED and re-ENABLING it. I am able to boot into stock recovery but it's written "E: UNABLE TO MOUNT /SYSTEM" when I tried to perform HARD RESET. This only happens after I flashed the latest Firmware (J200GUDXS3AQG2).
_____________________________________________________________________________________
Issue for Device #2: PC ABLE TO DETECT DEVICE
Screen Options: Bootlogo/Bootsplash ONLY
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: OFFICIAL
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED
No matter what key combination I pressed, IT ONLY BOOTS INTO BOOTLOADER MODE. Yes, not even a chance to peek at the BOOTSPLASH/BOOTLOGO screen. Stock firmware flashing was SUCCESSFUL but it BOOTS back to the damn same BOOTLOADER page (without all the details), able to flash TWRP (v2.87, v3.0.0, v3.0.2, v3.1.1) SUCCESSFULLY but FRP LOCK is ON.
_____________________________________________________________________________________
I hope the details given are sufficient enough for all you GRANDMASTERS, HACKERS, DEVELOPERS or even PASSER-BYs to provide me with a solution other than what I have done. In summary;
Device #1: PC unable to detect device, HARD RESET successful with ERROR "E: unable to mount /system".
Device #2: Tried flashing TWRP but FRP Lock ON, tried flashing stock firmware SUCCESSFULLY but boot into BOOTLOADER mode again, unable to enter stock recovery page or any other screens EXCEPT FOR THE BOOTLOADER.
_____________________________________________________________________________________
Thank you in advance & have a great day.
No one?
DaRdamnDoG said:
No one?
Click to expand...
Click to collapse
Have you tried using a different windows computer ?
George Malas said:
Have you tried using a different windows computer ?
Click to expand...
Click to collapse
Device #1 has been fixed, apparently another third party USB cable managed to get my PC to detect it in bootloader mode, the rest was easy.
As for Device #2, I was told by mobile shop owner that in recent months many of Samsung devices (especially Galaxy S7 variants and Galaxy Notes) had the same issue as I mentioned and he explains further that it is some sort of the manufacturers' effort or tactic to encourage mobile users to upgrade our devices.
How big of a ****ing asshole is Samsung to do such thing. Really ? They want to kill your ,quote on quote ,old device just so you can buy a new one. Just so I can clear things up in my mind , you mentioned above that you tried flashing TWRP on device #2 but FRP Lock was ON. But FRP Lock has nothing to do with TWRP. FRP Lock is Factory Reset Protection which purpose is to prevent someone from setting up the phone without knowing the credentials of the Google Account previously linked with the device. As long as your bootloader is unlocked , you can hop on TWRP ,flash a custom ROM and your problem should be solved.

Tab3 SM-110 Firmware Upgrade Issue

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

Categories

Resources