Hi guys, I'm new to XDA, flashing roms and sadly 'soft bricking.'
Or atleast that's what I think it is. Essentially i downloaded a couple of ROMs that I was testing out; and one of them was for an i9300; my phone is a locked to the optus (australia) network i9305 (4g) (sgS3 LTE [that's what the yanks call it, right?]. I had cwm back up and i had read into the whole ordeal a lot. I did everything it said and it sort of worked; the device was rooted CF-root via ODIN and the device had once been rooted before through framaroot. I checked the root using root checker, and got ready to install the custom ROMs. I copied the .zip to my external SD card and i went into cwm and clicked install or load or whatever. It didnt work-- at first i could get back into cwm but now I CAN NOT GET INTO ANDROID SYSTEM RECOVERY, CLOCKWORK MOD AND IT GETS STUCK ON THE BOOT. I think it's soft bricked because i can still get into download mode.
SO firstly, what steps should i take?
when i connect it (usb cable) to the computer it doesnt show up on kies though its got all the right drivers.
I'm quite lost.
top left corner says:
ODIN MODE
PRODUCT NAME: GT- I9305
CUSTOM BINARY DOWNLOAD: Yes (7 COUNTS)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Does anyone know how i can get out of this nightmare? would it be worth to pay OPTUS $258.01 AUD for them to fix it?
What method have you tried to get into clockworkmod since this happened? Just to clear up any potential lose ends.
Guessing, pulled out battery for 5 secs, put in (make sure it doesn't boot automatically as soon as the battery is back in), hold down these buttons in order for 5 seconds home + volume down + power. You can also try both volumes up/down and up in this combination. They generally may do different things.
Keep calm, as long as we have All in one toolkits or Odin, it's nearly always okay.
Turbine1991 said:
What method have you tried to get into clockworkmod since this happened? Just to clear up any potential lose ends.
Guessing, pulled out battery for 5 secs, put in (make sure it doesn't boot automatically as soon as the battery is back in), hold down these buttons in order for 5 seconds home + volume down + power. You can also try both volumes up/down and up in this combination. They generally may do different things.
Keep calm, as long as we have All in one toolkits or Odin, it's nearly always okay.
Click to expand...
Click to collapse
I haven't tried to get clockwork back. my computer won't even acknowedge the phone plugged in so i dont know?
i;ve done that-- it only gets to download mode
Also, i can't get into any sort of recovery mode (clock work or android system)
i have Odin on the computer, but it doesnt read the phone
Good, download mode is all you need for an AIO or Odin to work. While it may not recognise the device conventionally (generally the software is trying to work in MTP or usb mode), download mode is just fine.
Download Unified Android Toolkit from here: http://www.skipsoft.net/?wpdmpro=skipsoft-unified-android-toolkit-v1-2-8
And it gives pretty good steps to run procedures on your phone. From memory it lets you flash a custom recovery, flash certain roms and a few other things.
[Edit]
You have installed the Samsung usb pc drivers right?
m0n_st4h said:
Hi guys, I'm new to XDA, flashing roms and sadly 'soft bricking.'
Or atleast that's what I think it is. Essentially i downloaded a couple of ROMs that I was testing out; and one of them was for an i9300; my phone is a locked to the optus (australia) network i9305 (4g) (sgS3 LTE [that's what the yanks call it, right?]. I had cwm back up and i had read into the whole ordeal a lot. I did everything it said and it sort of worked; the device was rooted CF-root via ODIN and the device had once been rooted before through framaroot. I checked the root using root checker, and got ready to install the custom ROMs. I copied the .zip to my external SD card and i went into cwm and clicked install or load or whatever. It didnt work-- at first i could get back into cwm but now I CAN NOT GET INTO ANDROID SYSTEM RECOVERY, CLOCKWORK MOD AND IT GETS STUCK ON THE BOOT. I think it's soft bricked because i can still get into download mode.
SO firstly, what steps should i take?
when i connect it (usb cable) to the computer it doesnt show up on kies though its got all the right drivers.
I'm quite lost.
top left corner says:
ODIN MODE
PRODUCT NAME: GT- I9305
CUSTOM BINARY DOWNLOAD: Yes (7 COUNTS)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Does anyone know how i can get out of this nightmare? would it be worth to pay OPTUS $258.01 AUD for them to fix it?
Click to expand...
Click to collapse
Just one thing I would like to point out reading your thread is that you say you downloaded a number of roms including a I9300 your phone is a I9305 (DO NOT FLASH I9300 ON A I9305!!) This can potantially brick your device! Also uninstall Kies if you want to use Odin it interferes with it.
Last but not least you have posted in I9300 thread their is a dedicated I9305 thread here >> http://forum.xda-developers.com/galaxy-s3/help-i9305 <<
tallman43 said:
Just one thing I would like to point out reading your thread is that you say you downloaded a number of roms including a I9300 your phone is a I9305 (DO NOT FLASH I9300 ON A I9305!!) This can potantially brick your device! Also uninstall Kies if you want to use Odin it interferes with it.
Last but not least you have posted in I9300 thread their is a dedicated I9305 thread here >> http://forum.xda-developers.com/galaxy-s3/help-i9305 <<
Click to expand...
Click to collapse
I know, I know, i read it wrong and was excited and all and i messed up big time.
cool will do
thanks
Related
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 everyone,
I am a noob but I have scoured the earth and not been able to find any answer to this or any case of this occurring... yet. However the incidence may increase over the next few days as Vietnamese users update.
I have an unrooted S2 GT-i9100G (the ones released for Asian markets).
I bought it new out of an unopened box from a major retailer and have never installed any CFW.
I was running ICS without a hitch until yesterday (and had previously successfully updated from Gingerbread), when an official update announcement arrived (I'm assuming Jellybean... finally).
Phone ran update then rebooted and bricked, and now gets stuck on the splash screen (Black screen with "Samsung Galaxy S2 GT-I9100G in the middle).
If I enter recovery mode (down, home, power) then it shows me a screen with ODIN mode!
I don't get it. I thought ODIN was not included in stock phones? I'm also assuming this is why the stock FW update bricked the phone.
What steps should I take now? Since it appears ODIN may exist on the phone in some capacity should I hook it up to the PC and try to root the phone?
So far all I have done is cleared the phone memory using the standard recovery mode, and left ODIN mode running whilst unconnected to PC to see what happened (which was nothing). For some reason the phone drains completely in ODIN mode even when connected to a charger.
Thanks for your input on this one.
EDIT: Also please don't tell me to take it back to the retailer. The phone is out of warranty now and Vietnamese retailers don't take any responsibility for their products after sale, so I need to sort this out by myself. Thanks
Down/home/power is download mode, not recovery mode. Recovery mode is vol up/home/power.
You need to find an I9100G stock rom for your carrier/country from somewhere (maybe Samfirmware ?), get into download mode & flash it with Odin (how to do this has been covered thousands of times here; search). If Odin won't work or the phone/PC won't recognise each other, search for threads re: this issue. There's a set of 10-12 troubleshooting steps you need to try in that instance.
MistahBungle said:
Down/home/power is download mode, not recovery mode. Recovery mode is vol up/home/power.
You need to find an I9100G stock rom for your carrier/country from somewhere (maybe Samfirmware ?), get into download mode & flash it with Odin (how to do this has been covered thousands of times here; search). If Odin won't work or the phone/PC won't recognise each other, search for threads re: this issue. There's a set of 10-12 troubleshooting steps you need to try in that instance.
Click to expand...
Click to collapse
Roger that. I'm sure I can figure out how to do all these things quite easily. But how about the fact that Odin is present on the phone? I was under the impression that Odin is an extra application that you install to root your phone and install CFW. My phone is unrooted and stock out of a sealed box, so should I expect to have Odin on it? I don't want to have CFW on my phone and I'm concerned that even after I fix this issue and unbrick the phone, I will have difficulty installing the latest Jellybean XXV region OFW through automatic update.
It also seems strange and contrary to me that I should have to even use unofficial methods in order to fix an official update that was delivered automatically.
Odin is not present on the phone. Download mode is also referred to as 'Odin mode' because you use Odin to flash whatever (normally stock roms) in this mode. Odin is a piece of Samsung software initially used by techs @ service centres but now widely used by people who visit XDA/similar places to flash stuff to their phones.
Edit - You can think it's 'strange or contrary' that you need to do X or Y to fix your phone. That's fine (Personally, I'm not really interested). That's how you can fix your phone. Sorry if I sound standoffish or whatever, it isn't personal at all, but you're just another person with a (slightly, at this point) busted phone who visits here. I've told you how to fix it, so you can either do that or not.
And there it is. Thanks for your guidance
MistahBungle said:
Odin is not present on the phone. Download mode is also referred to as 'Odin mode' because you use Odin to flash whatever (normally stock roms) in this mode. Odin is a piece of Samsung software initially used by techs @ service centres but now widely used by people who visit XDA/similar places to flash stuff to their phones.
Edit - You can think it's 'strange or contrary' that you need to do X or Y to fix your phone. That's fine (Personally, I'm not really interested). That's how you can fix your phone. Sorry if I sound standoffish or whatever, it isn't personal at all, but you're just another person with a (slightly, at this point) busted phone who visits here. I've told you how to fix it, so you can either do that or not.
Click to expand...
Click to collapse
Well until your final post I wasn't aware that download mode was also called Odin mode and that is perfectly normal for a stock phone to say this. I think it's perfectly reasonable for someone who has done a fair bit of research into fixing a stock phone to hear about Odin only in the context of rooting and CFW (pages which I avoid because I'm not interested in CFW), and thus to be surprised when they see Odin mentioned on their stock phone. Now that you've made me aware that this is normal, I'm perfectly capable of finding the info required to fix the phone.
I appreciate your help. I just wanted to mention this as it seems you feel I have asked this question unnecessarily. I hope this points out that if one follows this particular train of thought of fixing a stock phone then its very possible and not unreasonable to arrive at this conclusion.
Hey, so I was trying to flash my friend's s3, and apparently, I did something wrong which got me stuck up at odin mode.
Initially, I could hold the vol up + home + power button to go to recovery, but now, even that won't work as it would just show me
Samsung's logo and a red exclamation mark on top left corner.
I've downloaded the firmware stock and tried to flash it using odin however it just won't work.
It says "NAND Write Start!!!" and it just stops there (stuck forever). It should (as I know it) show a progress bar on my android and
on it's interface to tell how much it has been done, but as soon as I start, the progress bar instantly fills up (on my android, the blue line)
and its just stuck there.
I've tried to take out the battery, clear cache/reset factory, take out sd and sim. But it simply won't work.
It's just stuck on "Downloading....do not turn of target!!!"
I cannot even get the flash counter to reset (I don't know how, since I can only open up odin mode)
counter: 4
binary: yes
Currently, I don't even know if it's suppose to be charging or the battery is just draining out.
Region for this phone is Turkey.
Yes I've also unrooted the phone using KingoRoot (previously, when it could go into recovery) but no luck.
Note: I have searched other threads on this forum but I cannot get anywhere around even close to fix my device.
It's soft-bricked (I assume, of course it is).
Any idea how to fix this?
Odin Screenshot (since it's my first post, it won't allow me to post outside links, sigh,):
http: // i.imgur .com/eBVZ3NN . png
^^ Just been stuck there....
Meanwhile on my android, it just shows a full-blue progress bar. And that downloading do not turn of target.
UPDATE:
THE PROBLEM HAS BEEN RESOLVED. I DOWNLOADED A CUSTOM FIRMWARE, (LUCKILY, CLOCKWORK MOD WORKED, JUST HAD TO WAIT AFTER GOING TO RECOVER)
FLASHED IT THROUGH THERE, WAITED FOR IT TO INSTALL, RESTART. BAM.
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Yeah, wrong firmware I suppose
boomboomer said:
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Click to expand...
Click to collapse
I was seeing this tutorial on how to install KitKat (4.4.4) on Galaxy S3. I must've made a mistake while trying to do so.
In other words, yes, flashing a firmware for another model.
You have a hard brick, sorry.
Yeah, no.
boomboomer said:
You have a hard brick, sorry.
Click to expand...
Click to collapse
No I don't lol. The problem has been solved anyway.
Im' glad to see you didn't give up on this, and came back to let us know what was wrong
I know this could be seen as off-topic, but the reality of devices becoming bricked isn't really possible luckily, it just takes longer to get around sometimes. If the item is worth fixing, then I always say keep at it, because I've never had an android device stay stuck so far. The only thing that really went nuts and refused to work, were 2 of the Iconia A500 tablets that lost access to their memory - but this is a common hardware fault as the RAM chips break away and need reflowing before you can even format the internal memory (it cant even see the SD cards either because the RAM comes and goes - same idea as plugging/unplugging a USB drive in Windows/Linux - it just doesn't know what to believe lol).
Great forum by the way, there's so much great information on here I get lost reading
Hello Everyone,
So recently I got a new S4 and I decided to root and mess around with it a little bit... Didn't go so well.
First KNOX was pissed that I tried that because I had given SU power to SuperSU (I didnt want to use KingUser) so when that happened, SuperSU failed to set itself as the primary SuperUser app. So I decided to install recovery (TWRP) to do it the recover way, scripts and all that. After that, I went ahead and removed KNOX, via the settings menu on the app.
Now I fail to boot into RECOVERY, and I also fail to boot into normal Android mode. When I attempt to boot normally, the SAMSUNG logo comes up then verizon, Okay fine its booting. 5 miutes later, the phone gets hot, and still wont boot.
I cannot charge the normal way, or even use the charging port. I have to take the battery out and put it in a dock. So ODIN is out of the choice.
My Phone Specs:
Samsung Galaxy S4 i545 (Verizon)
1GB SD Card
No recovery or ODIN.
Please help...
If you can't get into download mode then you have a problem.
Without it there isn't much you can do. You also need the pc to recognize your phone.
I'd say flash a custom ROM because new update which I received on stock firmware of I9500 added some security and an app called smart manager which is causing instability. Connect your dead phone to charger and then flash TWRP 2-3 times and don't forget to untick F.rest time and auto reboot. Normally it is ticked, and manually boot to download mode each time I hope you know how to do that. Then try your luck. That's how I did it. And use latest recovery available on the web.
Hit thanks
I believe the Verizon s4 has a locked bootloader (http://forum.xda-developers.com/showthread.php?t=2681316); therefore, you cannot flash a custom ROM or custom recovery.
You may get more replies if you post your question here: http://forum.xda-developers.com/galaxy-s4-verizon/help
Read before posting!
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
thedarkness523 said:
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
Click to expand...
Click to collapse
if the port is physically damaged then you need to
get the port replaced
there is absolutely nothing you can do until you have the usb port repaired
. secondly hold power down while inserting the battery if that doesn't get it into download mode then congratulations you now have a 200.00 dollar brick
the i545 does not support custom recoveries or custom roms outside of modded stock roms attempting to flash one will result in a permabrick as you just found out
Once the usb is repaired if you are still unable to access download mode then you have a big problem. When the port is repaired see if the comouter recognizes the phone as QHUSB_dload, if so, you need jtag, if the computer doesnt recognize the phone then it is most likely damaged beyond repair.
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.