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
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.
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD
Hi all,
I've managed to royally mess up my Galaxy S2, and I could really do with a bit of help! It was running a rooted stock rom.
The problem started when I attempted to install the Orange Signal Booster using instructions from this thread. I think the killer was replacing default.prop in system.
At this point the phone would crash a couple of seconds after the unlock screen appeared. I could get as far as dragging down and clicking settings before the entire thing hangs. I got similar results in safe mode. I also tried wiping cache etc in CWM but to no avail. I'm backed up, so I tried a factory reset, but I'm having a similar issue. The language selection screen appears, I press start and the phone freezes again.
I'd really appreciate some help!
BTW, my phone's USB port doesn't work so I'm looking for a solution that can be done within recovery. This is a separate issue and I believe it is unrelated as I have managed fine for over a year.
With a dead usb port you're pretty much screwed. The best and fail proof solution is to reflash stock rom using odin because it will wipe and reflash all partitions that were used before.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.