Related
Hello ppl,
i got a big problem, i hope someone can help me.
A friend of mine, gave me his galaxy s 2 to fix it. It just showed the battery icon with a circle running into it.
I fixed it with the JIG and got into download mode.
Everything is fine until now, even the flash with Odin shows success, but the phone just wont start up.
It doesnt matter what i do, or flash, its stuck in the samsung galaxy s II screen.
Download Mode is working, but Recovery not. When i try to enter the recovery mode, the phone hangs with the same screen like above.
Is there anything i could try to fix this?
Thank you
geminga
Okay relax, as you can get into download mode, there's a chance that you can still fix it.
I think you're running the wrong kernel or modem here.
I advice you to freshly install a new rom, and then install a CF-Rooted kernel that allows you to get back into recovery.
Once you got that worked out, get into recovery and select Wipe/factory reset. It should boot now.
If this still does not solve your problem, install VillainRom 2.0 using the process described in the thread. I had the bootloop problem too, but Wiping, Flashing and Wiping again did the trick for me.
Thank you mate I will try this later. Im will report if I was successful. (i hope so)
I flashed 2.3.4 ROM with Odin and then CF-Recovery but i can still not access recovery mode. It shows the yellow triangel but still hangs with the samsung galaxy screen.
I think that phone has become a nice paperweight...
As 2.3.4 is a test release i would try older stable firmware .
Flash a stock 2,3,3 rom via Odin and see if it boots .
jje
Is there something for Samsung that completely replaces everything including ROM,recovery and such things?
From my desire I know, if a RUU can't boot your phone it is 100% bricked. So I need something like that for that sgs2, to be sure that this is no hardware failure...
I will try some flashes and report after that.
Sent from my HTC Pyramid using XDA App
what i would do is install one of these carrier branded ROMs http://forum.xda-developers.com/showthread.php?t=1113928
and see if it boots, if it does then flash the cfroot [specific to the carrier version you choose e.g. KF2] make sure thats the right one. that should give you recovery as prodygee has said. then do a full wipe, system, data, cache, dalvik and reboot.
afaik this should work. that's worked for me on numerous bootloops!
Hope this helps, Rumble
solved [Arrow Galaxy s 2 wont start]
i just followed this link... >>1.Make sure that your phone is Samsung Galaxy S2 not any other.If you try this process on any other phone then the phone will be damaged.
2.Create a backup of your all useful phone data with the help of backup apps that ensure your phone data.
3.This process will take several minutes or may be hours so make sure that your phone battery consumption is maximum.
4.Remove the SIM card and external storage SD card.
5.Download both these files.
Download Gingerbread 2.3.4 XXKGI Firmware
Odin3 v 1.83
Procedure for Update Samsung Galaxy S2 GT I9100 to Gingerbread XXKG1 2.3.4 Firmware.
1. Open the Odin.exe file you will see the window image on your screen.
2. Switch off your phone then press and hold the Volume Button with the Power Key and HOME to turn the phone into the download mode.
3. Now connect your phone via USB cable to the computer. After connectivity you will see the window screen in which you see the COM ID 5 as a yellow color.
4. Now add the following files in the corresponding options:
PIT – u1_02_20110310_emmc_EXT4.pit
PDA – CODE_I9100XXKG1_CL349526_REV02_user_low_ship.tar
Phone – MODEM_I9100XXKG1_REV_02_CL1034110.tar
CSC- GT-I9100-CSC-MULTI-OXAKG1.tar
5. Click on the "Start button". Then updation process is start and wait for some time.Please don't interrupt your device will installation.
6. When the installation is completed reboot your phone and remove cable connectivity.The previous version of this firmware is also stored in cache memory.Remove your previous firmware version by dialing*2767*3855#.Now Update and check the latest version by dialing *#1234#.
it worked perfectly for me
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
Hello.
I have a problem. When I bought my SGS2, I had a branded software (GINGERBREAD). I decided to update it to ICS. Everything went well, but I played a little bit with Android and messed up some things. My power screen did not appear. Phone was just turning off, while I was holding the power button, instead of showing up the power screen, where I could be able to turn off the flight mode for example. Simply, it was just straightly turning off. And I did not have lockscreen. When I pressed the lock key, the screen just got dark, and, when I pressed it again, the screen went on, without the lock screen to tap and move. It just took me straightly to the screen I had had before. I decided to wipe everything, but it did not help. I searched the Net and found my branded ROM, that I seemingly had pre-installed on my phone. After flashing I hoped everything to go well. Unfortunately, it did not solve the problem. I could not even make a call or access the internet. It said, that I do not have access to the network and asked me to put my sim card in, when I had it done. That was weird. I tried to install KI3 ROM, that I found on the net. It restored my Android to 2.3.5 and fixed the problems. But now, when I try to update my Android to ICS, the problems appear again. I just got stuck on 2.3.5 and I do not see any working way to update my Android.
What is funny, even after wiping, on the home screen, when the phone should ask me to type my google account to synchronize and all that things, it just takes me straightly to the home screen. It looks like the data about my account is saved somewhere on PC, and even the wipe does not seem to delete the data. That is rediculous. But this is about ICS only. Gingerbread is OK.
If you could, give me some real working links. I might used some damaged ROMs or something like that. I do not know, I have no clue. I've been trying to fix that since I got the problem, so I am really hopeless.
Thanks in advance.
Batorun. said:
Hello.
I have a problem. When I bought my SGS2, I had a branded software (GINGERBREAD). I decided to update it to ICS. Everything went well, but I played a little bit with Android and messed up some things. My power screen did not appear. Phone was just turning off, while I was holding the power button, instead of showing up the power screen, where I could be able to turn off the flight mode for example. Simply, it was just straightly turning off. And I did not have lockscreen. When I pressed the lock key, the screen just got dark, and, when I pressed it again, the screen went on, without the lock screen to tap and move. It just took me straightly to the screen I had had before. I decided to wipe everything, but it did not help. I searched the Net and found my branded ROM, that I seemingly had pre-installed on my phone. After flashing I hoped everything to go well. Unfortunately, it did not solve the problem. I could not even make a call or access the internet. It said, that I do not have access to the network and asked me to put my sim card in, when I had it done. That was weird. I tried to install KI3 ROM, that I found on the net. It restored my Android to 2.3.5 and fixed the problems. But now, when I try to update my Android to ICS, the problems appear again. I just got stuck on 2.3.5 and I do not see any working way to update my Android.
What is funny, even after wiping, on the home screen, when the phone should ask me to type my google account to synchronize and all that things, it just takes me straightly to the home screen. It looks like the data about my account is saved somewhere on PC, and even the wipe does not seem to delete the data. That is rediculous. But this is about ICS only. Gingerbread is OK.
If you could, give me some real working links. I might used some damaged ROMs or something like that. I do not know, I have no clue. I've been trying to fix that since I got the problem, so I am really hopeless.
Thanks in advance.
Click to expand...
Click to collapse
1. Download a stock firmware. But, register first.
2. Download Odin.
3. Happy flashing.
I have tried to use Odin. I do not know, which link shall I choose. On the site, you gave me link to, there are a lot of ROMs. Which is the stock?
They are all stock. Where did you purchase your phone (location, carrier), do you have the i9100 or other (i9100t, i9100G, i9100p etc), is it branded.
I am from Poland, so I bought my phone in Poland. The carrier is Play and I have the original I9100. I have already tried to re-install stock firmware and then ICS, but I have no lock screen and no power menu. I also have no connection, it says put a sim card in, even, when it is in. Wipe does not help. I do not even have the first-start screen, when it asks you to type your google account data and synchronize. It just installs and updates aps and that is it. That is weird. It was OK before, but it got screwed up.
Batorun. said:
I am from Poland, so I bought my phone in Poland. The carrier is Play and I have the original I9100. I have already tried to re-install stock firmware and then ICS, but I have no lock screen and no power menu. I also have no connection, it says put a sim card in, even, when it is in. Wipe does not help. I do not even have the first-start screen, when it asks you to type your google account data and synchronize. It just installs and updates aps and that is it. That is weird. It was OK before, but it got screwed up.
Click to expand...
Click to collapse
Like i said, flash the stock firmware. Sammobile.com>register>FIRMWARE>select your device, region etc>download.
I did, I tried to use the older version of Odin (1.3), and it helped a little bit, but I can not still update Android to ICS properly. I just get sometimes lock-up screen and/or a lot of red messages in recovery mode and I can not boot my system up.
Batorun. said:
I did, I tried to use the older version of Odin (1.3), and it helped a little bit, but I can not still update Android to ICS properly. I just get sometimes lock-up screen and/or a lot of red messages in recovery mode and I can not boot my system up.
Click to expand...
Click to collapse
Use CHECKFUS to download your providers or your matching original ICS firmware and flash via ODIN .
Problems then suggest a full wipe of the phone and sd card .
....................................
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery if no CWM recovery flash root from .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
JJEgan said:
Use CHECKFUS to download your providers or your matching original ICS firmware and flash via ODIN .
Problems then suggest a full wipe of the phone and sd card .
....................................
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery if no CWM recovery flash root from .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Click to expand...
Click to collapse
I will try that. But, one more question. Shall I use the PC version of CHECKFUS or the mobile one?
Use the PC version, which will enable you to download the rom & decrypt the package automatically. Connect your phone to PC via USB, fire up Odin, and choose the rom package you download with Checkfus in the PDA section. Flash.
Batorun. said:
I will try that. But, one more question. Shall I use the PC version of CHECKFUS or the mobile one?
Click to expand...
Click to collapse
Currently, I did the steps you gave me above and now Odin is flashing my stock kernel (at least, it is supposed to be my stock ROM). Stay tuned.
@ REFRESH.
After flashing, recovery mode vomited with a lot of red messages with errors again. As it was a 3 files ROM, I selected PIT and checked re-partition. Should I leave these options untouched, even when it is the 3 files ROM?
Batorun. said:
@ REFRESH.
After flashing, recovery mode vomited with a lot of red messages with errors again. As it was a 3 files ROM, I selected PIT and checked re-partition. Should I leave these options untouched, even when it is the 3 files ROM?
Click to expand...
Click to collapse
The advice on XDA is never use PIT and never repartition .
jje
I did, but it did not help. What about trying to unmount these directories instead of just formatting in CWM RECOVERY?
Do a full wipe again...select PDA on Odin for rom file...select CSC also and insert the same firmware file u have inserted into the PDA onto the CDC..... It will change ur sales code back to the stock firmware and wipe all the crap that was on there before.do not select any other option on the odin board other than the ones that should already be ticked/selected
Sent from my GT-I9100 using XDA
I've managed to fix that.
I just had to use a command prompt from Play Store, to change a line of code in one file.
Alright, so here's my problem:
I just upgraded to the Galaxy S III yesterday, and today decided to try to 'root' the device. So I found the Toolkit here on XDA (from here), and went through the initial steps without any issues (driver installation, device recognition, etc..).
I then went to the 'rooting option' menu, where I selected the first--and most basic --option, which was to only install Super User, and the push the permissions.
I was following the automated guide, opened Odin, selected the correct file, 'boot-insecure-i9300xxale8-gsm.tar', and made sure only 'auto-restart' and F.reset time' were checked, and clicked 'start'. The flash appeared to have gone well, but when it tried to restart, the phone never rebooted. I attempted to reboot into download mode (Vol. Down + Home + Power), but the device was unresponsive. I then browsed around the forums a bit looking for other methods, including taking the battery out for several minutes, then putting it back in whilst holding down the 'download mode' button combination, and other various variations of that method; yet again, none prevailed.
The device gives no indicator lights when plugged in, no light up when the power button is held down, and is overall seemingly unresponsive. However, when I hold down the 'home' button alone - after about 30 seconds - a green vertical battery appears on the screen, with a little white loading indicator on it, but vanishes after about 5 seconds or so, and the device becomes unresponsive once more.
The device is not being recognized by my computer whatsoever, no beeps or anything when plugged in.
Any ideas as to what I can do?
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Simonetti2011 said:
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Click to expand...
Click to collapse
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Samsung don't seem to really care if you have rooted or not, so far about 4 people in 2 days on this and other for mums have returned phones because they have possibly bricked them, all got them exchanged with out a problem.
To unroot and return your galaxy S3 to stock for warranty watch this. http://www.youtube.com/watch?v=_8Tga_yKywc&feature=youtube_gdata_player
Zenno said:
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Click to expand...
Click to collapse
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
JJEgan said:
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
Click to expand...
Click to collapse
I tried to reboot the stock firmware 'boot-stock-i9300xxale8-gsm.tar', but when Odin failed to reboot the phone, and I manually put it back into download mode, it still said my binary was 'Custom'.
Should I be trying to flash that under 'Bootloader' in Odin or something? Because I've been doing 'PDA' and it hasn't been working.
Download an original, stock ROM from samsung-updates.com or use checkFus downloader.
That is what you'll flash.
This is the one I use: http://samsung-updates.com/get/1932/Samsung_Firmware_GT-I9300_DBT_I9300XXALF6_Android_4_0_4.html
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
How to get out of hard brick to download mode
Zenno said:
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
Click to expand...
Click to collapse
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Pull the Batteery
jiafu790617 said:
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Click to expand...
Click to collapse
Remove the battery for about 2 minutes, replace it and immediately try to go into download mode. This worked for me
same problem
Hard bricked it too, flashed a wrong rom made for international model, i have the att model are you sure taking out the battery works?
Zenno said:
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
Click to expand...
Click to collapse
I have the same problem! Do you know how you got into download mode?
Surge411 said:
I have the same problem! Do you know how you got into download mode?
Click to expand...
Click to collapse
Just keep trying,I must have removed the battery and pressed the buttons over six times to get into download mode. Hope you get there.
Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
if it's a sudden death, there's no way of recovering the data
Katanaqui said:
Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
Click to expand...
Click to collapse
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
chap rriespr
JJEgan said:
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
Click to expand...
Click to collapse
Ahh thanks, I had a read of a few of these but I missed the 'for the ultimate noob' one
I've got the USB drivers installed correctly on my pc, I think the phone just won't boot up far enough to do whatever it does to be mass storage at its end.
I've tried pulling my files via ADB as well and nothing.
My problem is there doesn't seem to be a way of getting my data off my phone onto my pc as my phone won't boot. So as a long shot, I'm trying to fix the booting problem by flashing it, hopefully without wiping any data, so then I could boot properly and rescue my files.
My question is what would be the best way to go about attempting this: flashing the whole stock firmware file, or just the boot loader file?
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
JJEgan said:
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
Click to expand...
Click to collapse
I thought SD meant a soft brick, ie. stuck in bootloop but with the possibility of recovery/download modes, whereas a dead phone is hard bricked?
Ok thanks
Sd means "softbrick" or "sudden death" depending on who abbreviates it.
Sudden death is a full hardware brick ( no chance of recovery), softbrick can be fixed through recovery, download mode and/or jig
Sent from my GT-I9300 using xda premium