Hi, how can i test safely galaxy5.0 kernel, there is method to start once a kernel without flashing or from other source than SGP5.0 NADN, without possiblity of brick ?
Arlicc said:
Hi, how can i test safely galaxy5.0 kernel, there is method to start once a kernel without flashing or from other source than SGP5.0 NADN, without possiblity of brick ?
Click to expand...
Click to collapse
Using Fastboot you can flash a kernel for one boot only. I'm not sure if it can restore your device if something goes wrong. I reckon just do a backup and try to make sure nothing is wrong in your kernel.
Supermaster34 said:
Using Fastboot you can flash a kernel for one boot only. I'm not sure if it can restore your device if something goes wrong. I reckon just do a backup and try to make sure nothing is wrong in your kernel.
Click to expand...
Click to collapse
Just use fastboot from adb console, i dont need to install anything on the SGP ?
Arlicc said:
Hi, how can i test safely galaxy5.0 kernel, there is method to start once a kernel without flashing or from other source than SGP5.0 NADN, without possiblity of brick ?
Click to expand...
Click to collapse
You can flash it freely because..... according to my experiences, any brick can be cured by odin, except hard brick occurred by bootloader error
Sent from my SHW-M110S using xda premium
Neodymium said:
You can flash it freely because..... according to my experiences, any brick can be cured by odin, except hard brick occurred by bootloader error
Sent from my SHW-M110S using xda premium
Click to expand...
Click to collapse
Yea, i have got a case with my friend, after flashing rumarid r14 kernel by odin, he have got pernament brick without hope to come back, he was trying unbrickable ressurector on linux, but 0 reaction from SGP5.
what is more risky, installing kernel via ODIN or CWM ?
Arlicc said:
what is more risky, installing kernel via ODIN or CWM ?
Click to expand...
Click to collapse
I would consider odin much more risky. After all, in cwm you can make it check signatures for integrity, and there are no cables to accidently unplug.
Sent from my 5.0 USA GenGin + ICS theme
Mevordel said:
I would consider odin much more risky. After all, in cwm you can make it check signatures for integrity, and there are no cables to accidently unplug.
Sent from my 5.0 USA GenGin + ICS theme
Click to expand...
Click to collapse
How to force CWM to check signatures?
Sent from my GT-I9000 using XDA
Install zip -> toggle signature verification
(Of course, not all zips are signed to start with...)
Sent from my 5.0 USA GenGin + ICS theme
Related
Hey guys I need to return my phone to be fixed, but have a slight problem. The firmware is all stock except for when it boots up it says it is a GT-I9100. This is left from a previous flash that I did, but I went back to stock and never bothered to fix that, because it didn't really bug me. Now my phone won't recognize a charger or any usb plugs. My question is will Samsung/AT&T still accept my phone for replacement with this? If not is there anyway I can fix the boot screen without plugging my phone in? Thanks guys sorry for the noob question, but I am not really sure what to do and this is kind of a specific problem, so I couldn't find anything in the search. Once again really appreciate any help!
Play dumb and say it's always said that you didn't know the model number of your phone was a 727 lol
*** No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced. ***
crusecontrl said:
Play dumb and say it's always said that you didn't know the model number of your phone was a 727 lol
*** No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced. ***
Click to expand...
Click to collapse
777 you mean? This isn't the skyrocket forums
Sent from my SGH-I777 using Tapatalk 2 Beta-5
crusecontrl said:
Play dumb and say it's always said that you didn't know the model number of your phone was a 727 lol
Click to expand...
Click to collapse
No, don't do that.
You can either use Mobile Odin to remove it, or do a complete Return to Stock using Odin.
mattdm said:
No, don't do that.
You can either use Mobile Odin to remove it, or do a complete Return to Stock using Odin.
Click to expand...
Click to collapse
Can I use Mobile Odin with a stock firmware? Seems like you shouldn't be able to flash your phone from your device.
snowcamo said:
Can I use Mobile Odin with a stock firmware? Seems like you shouldn't be able to flash your phone from your device.
Click to expand...
Click to collapse
You're absolutely right. For some reason I thought you were stock rooted...my mistake. Use my second option then.
As long as you root it, you can use Mobile Odin. Not like it matters anyway, you just need to get rid of the GT-I9100 and then flash back to stock again, thus eliminating root.
Did Odin one-click back to stock not work for you? Because it sounds like you might have flashed I9100 bootloaders and flashing I777 bootloaders should fix it (which if I'm not mkstaken, the one click does include). Someone correct me on both points if I'm wrong , I'm simply conjecturing.
Sent from my SGH-I777 using XDA
It would be great if I could just flash the bootloaders, but I can't connect my phone to my computer
Some folks have reported that they could get their phone to connect via usb after cleaning the usb port with alcohol. Have you tried that?
Can you get into dl mode?
Sent from my SGH-I777 using XDA
creepyncrawly said:
Some folks have reported that they could get their phone to connect via usb after cleaning the usb port with alcohol. Have you tried that?
Click to expand...
Click to collapse
Yea I tried this, didn't work. I could probably get it into download mode, if I borrowed someones battery, but I am not sure why that matters if the computer won't detect it.
I finally got my phone to connect after cleaning it for like an hour, I just have to hold it at a certain angle. Everytime I try and flash the bootloader I get a fail though, I am using odin 1.8.5 and the bootloader here http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199. After it fails I have to reflash using the one click no bootloader here http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199. Is there any one click with the stock bootloaders someone could please link me to? Thanks once again guys
Both links appear to be the same.
Anyway, why would you flash the bootloader?
votinh said:
Both links appear to be the same.
Anyway, why would you flash the bootloader?
Click to expand...
Click to collapse
That was my suggestion, I thought it might be an I9100 bootloader that he flashed which causes the GT-I 9100 to show up on boot, and he wants it back at stock for returning. Again I could be wrong, and of course flashing bootloaders is very dangerous, especially with your faulty USB connection (I didn't know it was faulty when I posted before).
EDIT: Did you ever try rooting so you can go the Mobile Odin route (which would be much safer)?
Sent from my SGH-I777 using XDA
karate104 said:
That was my suggestion, I thought it might be an I9100 bootloader that he flashed which causes the GT-I 9100 to show up on boot, and he wants it back at stock for returning. Again I could be wrong, and of course flashing bootloaders is very dangerous, especially with your faulty USB connection (I didn't know it was faulty when I posted before).
EDIT: Did you ever try rooting so you can go the Mobile Odin route (which would be much safer)?
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
No I never tried that, would you recommend that? This is the screen I get when it boots http://img2.garfield.in/images/garfield/logoold_350x583.jpg, but my phone is a sgh-I777. That means it is the wrong bootloader right? Or am I misunderstanding something? Feel so useless haha, thanks guys.
Edit:
votinh said:
Both links appear to be the same.
Anyway, why would you flash the bootloader?
Click to expand...
Click to collapse
Meant to post this for bootloader link http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46, and I want to get it back to the stock loader so I can send it in for repair.
snowcamo said:
No I never tried that, would you recommend that? This is the screen I get when it boots http://img2.garfield.in/images/garfield/logoold_350x583.jpg, but my phone is a sgh-I777. That means it is the wrong bootloader right? Or am I misunderstanding something? Feel so useless haha, thanks guys.
Click to expand...
Click to collapse
I know that's the screen you're referring to, bootloader is just my random guess.
mattdm said:
No, don't do that.
You can either use Mobile Odin to remove it, or do a complete Return to Stock using Odin.
Click to expand...
Click to collapse
Since your USB connection is buggy, and since flashing bootloaders is really dangerous anyway, I'd try this instead. If it doesn't help, let us know.
EDIT: what does your flash counter say when you boot in to download mode?
karate104 said:
what does your flash counter say when you boot in to download mode?
Click to expand...
Click to collapse
This first, please. This will tell you which bootloader you currently have.
If the usb connection is lost while the bootloader is flashing, the phone will hard brik, and will require jtag repair to recover, which costs about $50 to $60. Therefore, it is necessary to know what the phone status really is before taking that risk.
If you determine that you really do have the I9100 secondary bootloader, then you put the I777 UCKH7 sbl.tar in the PDA slot of Odin3 v1.85. Or you could flash the I777UCKH7-CL503881 FULL Odin3 One-click Downloader which includes the param.lfs and the secondary bootloader.
Mobile Odin will not flash bootloaders or param.lfs
creepyncrawly said:
This first, please. This will tell you which bootloader you currently have.
If the usb connection is lost while the bootloader is flashing, the phone will hard brik, and will require jtag repair to recover, which costs about $50 to $60. Therefore, it is necessary to know what the phone status really is before taking that risk.
If you determine that you really do have the I9100 secondary bootloader, then you put the I777 UCKH7 sbl.tar in the PDA slot of Odin3 v1.85. Or you could flash the I777UCKH7-CL503881 FULL Odin3 One-click Downloader which includes the param.lfs and the secondary bootloader.
Mobile Odin will not flash bootloaders or param.lfs
Click to expand...
Click to collapse
Where can I get the full one click? On the download custom binary: no. Samsung official. Model: GT-I9100. Thanks
snowcamo said:
Where can I get the full one click? On the download custom binary: no. Samsung official. Model: GT-I9100. Thanks
Click to expand...
Click to collapse
Huzzah, I guessed right! You flashed I9100 secondary bootloaders.
Read this thread (I suggest reading the OP closely), paying special attention to 3) Special Problems. The downloads you need are here.
karate104 said:
Huzzah, I guessed right! You flashed I9100 secondary bootloaders.
Read this thread (I suggest reading the OP closely), paying special attention to 3) Special Problems. The downloads you need are here.
Click to expand...
Click to collapse
Whenever I try to do this with odin it fails . I think I just need the one click with bootloaders, but I can't find it.
hi,
this morning i downloaded a i9305's stock rom in order to port it in my device (i9300) by using dsixda kitchen port tool. i ve flashed the edited rom and i got bootloop, then i tried to go to recovery i got black screen mixed with blue line (like a panic kernel). i pulled out the battery, flashed a stock rom by odin. the results are : touchscreen not responding, phone very slow to boot up
i tried everythings to restore it (factory reset, wipe dalvik cache, formated system, flashed original rom, full s/w with pit,pda,modem,csc....please help me
thanks
Allthough it is considered very risky try to flash stock fw with repartition ticked and pit file
Sent from my GT-I9300 using xda app-developers app
yes i know but any solution ?
Stay a way from pit files if it boots .
jje
so no response ?
no one can help me ?
You have asked got reply's tried most that can be advised all that is left is a paid for service repair .
jje
If you haven't tried already - I would repartition with pit first. (Make sure repartition is ticked)
If that fails then its possible the bootloader has been somewhat damaged. how far does the boot progress?
would need a sboot.bin that is within a tar file to flash via Odin - bit risky though!
edit
(can get sboot.bin.tar file from here http://forum.xda-developers.com/showthread.php?t=1916796
but that thread is for phone s that do not go into download mode)
but research, so you are conffident about what your doing
AbuYahya said:
If you haven't tried already - I would repartition with pit first. (Make sure repartition is ticked)
If that fails then its possible the bootloader has been somewhat damaged. how far does the boot progress?
would need a sbin file to flash via Odin - bit risky though!
Click to expand...
Click to collapse
where i can get sbin ?
edit: i ve tried this but no changes !
machu28 said:
where i can get sbin ?
Click to expand...
Click to collapse
Although I have flashed sboot.bin files on prev devices I have not done it on the SGS3.
I have left a clarification request on the aforementioned page
edit
there is also one post at this thread: http://forum.xda-developers.com/showthread.php?t=1918667&page=2
You're the second person I've heard that this happened to (Same screen corruption, touch not working afterwards), glad to know this wasn't related to my kernel. Seems that you have a wrong Melfas firmware going on on your device now.
machu28 said:
edit: i ve tried this but no changes !
Click to expand...
Click to collapse
if bootloaders and PIT with repartitioned and a stock ROM and Modem all together failed.
then likely need to to open phone to sort it out
------->know some experienced doing it or
------>service centre
possible hardware failure
AndreiLux said:
You're the second person I've heard that this happened to (Same screen corruption, touch not working afterwards), glad to know this wasn't related to my kernel. Seems that you have a wrong Melfas firmware going on on your device now.
Click to expand...
Click to collapse
any idea how to restore it ?
AbuYahya said:
if bootloaders and PIT with repartitioned and a stock ROM and Modem all together failed.
then likely need to to open phone to sort it out
------->know some experienced doing it or
------>service centre
possible hardware failure
Click to expand...
Click to collapse
isn't a problem of drivers binary ?
machu28 said:
where i can get sbin ?
edit: i ve tried this but no changes !
Click to expand...
Click to collapse
machu28 said:
isn't a problem of drivers binary ?
Click to expand...
Click to collapse
I'm not sure what your asking?
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
if your flashing is unsuccessful/failed on Odin, then you could try the SDcard technique
But personally I would send for warranty repair.
machu28 said:
any idea how to restore it ?
Click to expand...
Click to collapse
No, not right now, sorry. By the way this is now a hardware problem, you won't fix it through flashing anything.
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
Click to expand...
Click to collapse
Some things are hardware firmwares and have nothing to do with the ROM, the touchscreen is one of them.
AbuYahya said:
I'm not sure what your asking?
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
if your flashing is unsuccessful/failed on Odin, then you could try the SDcard technique
But personally I would send for warranty repair.
Click to expand...
Click to collapse
yes send it for repair is my last option. unbelievable that software kills hardware !!
Some things are hardware firmwares and have nothing to do with the ROM, the touchscreen is one of them.
Click to expand...
Click to collapse
can i use "nand erase all" in odin ?
machu28 said:
can i use "nand erase all" in odin ?
Click to expand...
Click to collapse
No. The firmware isn't on the NAND.
Hi
I know that when you flash a rom using odin, the bootloader gets updated, which means that there is a higher risk of hard brick in case the process is interrupted. But what about CMW flashing? Does flashing a new rom.zip file with CWM also changes the bootloader?
If the phone is brickbug free, is it safe to say that the worst that can happen after a bad CWM flash is a sidt brick, while bad flashing using odin may result in a hard brick??
Does flashing a kernel (CWM) changes the bootloader as well?
Thanks
Does flashing a new rom.zip file with CWM also changes the bootloader?
Click to expand...
Click to collapse
No.
przemcio510 said:
No.
Click to expand...
Click to collapse
Thanks
Does that mean that there is no chance of getting a Hard brick by flashing a bad rom.zip file? I'm asking because recently I've started experiencing in flashing roms that I pre-modified myself (using winrar like delete useless apk's from system/app folder and adding compatible mods and modifying the updater script or replacing the kernel zImage..). So far the only mess I got myself into was a soft brick (bootloop) because I wasn't aware of the max 512MB limit to the system folder, but I managed to recover from this by odin). I just need to be sure that I wont end up with a hard brick (except for emmc bug which i do not have).
Thanks
Does that mean that there is no chance of getting a Hard brick by flashing a bad rom.zip file?
Click to expand...
Click to collapse
Right.
But, ROM zips include kernels, so don't flash i9100g ROM to i9100, because it will replace previous kernel and you will end up with bricked phone.
przemcio510 said:
Right.
But, ROM zips include kernels, so don't flash i9100g ROM to i9100, because it will replace previous kernel and you will end up with bricked phone.
Click to expand...
Click to collapse
Only a softbrick though.
Sent from my deep fried potato
You don't say?
Flashing i9100G kernel to i9100 leads to HARDbrick.
przemcio510 said:
You don't say?
Flashing i9100G kernel to i9100 leads to HARDbrick.
Click to expand...
Click to collapse
I really didnt know that....
Sent from my deep fried potato
I have a backup of my stock rom from when I got the phone and I would like to restore that back but it won't let me. When in recovery and I hit restore I get "E:Can't mount /sdcard" so I try advanced restore and then I get "E:Can't mount sdcard" and finally I tried restore from internal sdcard and then I get an error saying "Couldn't open directory. No files found." bearing in mind I don't have any sd card inserted but it's how I always used to do it. So I tried going to mounts and storage then mounting the sd card from there but get an error saying "Error mounting /sdcard!".
What do I do please?
Tried re flashing the recovery or trying another recovery?
Sent from my Vivid 4G using xda app-developers app
oggta said:
Tried re flashing the recovery or trying another recovery?
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
It's the only recovery I have, but how would I go about re flashing it? Just put it in a .zip or something?
have you tried looking for another recovery or looking into the android development for your phone.
shouldnt be that hard to put one on, in fact if it becomes that hard, it should only be as hard as running a few ADB commands. look for one that you like and check out the instructions
f8ct said:
It's the only recovery I have, but how would I go about re flashing it? Just put it in a .zip or something?
Click to expand...
Click to collapse
No , hes talking about kernel. You need to try a different kernel (they include cwm recovery).
Flash the kernel/recovery you used when backing up the rom.
TheATHEiST said:
No , hes talking about kernel. You need to try a different kernel (they include cwm recovery).
Flash the kernel/recovery you used when backing up the rom.
Click to expand...
Click to collapse
I can't even remember what kernel I was using back then. It was 2 years ago now.
I'm not sure if it's all worth it, I'm only recycling it at the O2 store for money, does it matter? Is installing custom roms illegal? Because my only worry is them testing it by turning it on or something and seeing that I'm running cMIUI.
f8ct said:
I can't even remember what kernel I was using back then. It was 2 years ago now.
I'm not sure if it's all worth it, I'm only recycling it at the O2 store for money, does it matter? Is installing custom roms illegal? Because my only worry is them testing it by turning it on or something and seeing that I'm running cMIUI.
Click to expand...
Click to collapse
Dude don't worry and that phone is worth the fix. As far as I c it you don't even have it that bad. What atheist said is correct.
All you need to do is look for a recovery / kernel that most of the time come together and flash it. Just read the instructions on that post.
After all you're in the right place to get your phone hooked up and fixed whenever u have problems. Don't be nervous about it. Unless u want a new phone lol.
Sent from my Vivid 4G using xda app-developers app
oggta said:
Dude don't worry and that phone is worth the fix. As far as I c it you don't even have it that bad. What atheist said is correct.
All you need to do is look for a recovery / kernel that most of the time come together and flash it. Just read the instructions on that post.
After all you're in the right place to get your phone hooked up and fixed whenever u have problems. Don't be nervous about it. Unless u want a new phone lol.
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
Well I already have a new phone man, I'm just getting rid of this one at a store who will pay me money for it. But I wasn't sure whether to flash the stock back or not in case they checked.
best bet then is just put it back to stock and wipe it like new
oggta said:
best bet then is just put it back to stock and wipe it like new
Click to expand...
Click to collapse
That's what I would like to do but can't work out how really. Is there just a stock ROM I could flash instead of having to restore my last backup of one?
f8ct said:
That's what I would like to do but can't work out how really. Is there just a stock ROM I could flash instead of having to restore my last backup of one?
Click to expand...
Click to collapse
Yes, official releases from Samsung at sammobile.com. Flash through Odin.
Sent from the Matrix
Donnie Sins said:
Yes, official releases from Samsung at sammobile.com. Flash through Odin.
Sent from the Matrix
Click to expand...
Click to collapse
I have Odin, I have the stock tar md5 file or whatever it is. I think the only thing I'm missing is the OPS files which I can't find because the only link I found was dead. Any help please?
The tar.md5 file is all you need. Flash it in the PDA section of Odin as previously advised.
MistahBungle said:
The tar.md5 file is all you need. Flash it in the PDA section of Odin as previously advised.
Click to expand...
Click to collapse
Right. I have to boot my phone into download mode too right? Power button + home button + volume down? Because I'm doing this and it's not working. Stuck on 'SetupConnection..' at the moment.
edit: it finished and said "Complete(Write) operation failed."
Anyone know why this isn't working? :s
can't get to Download Mode?
Time for usb jig.
or this thread.
Sorry, I typed that out wrong. I'm in download mode (I think) but I'm getting those errors that I posted about when I have it plugged in with Odin opened..
Install/Reinstall Kies and shut it all up before you open odin, then flash.
from sii xda-ded
gastonw said:
Install/Reinstall Kies and shut it all up before you open odin, then flash.
from sii xda-ded
Click to expand...
Click to collapse
I totally forgot about kies man, never even had it installed. It seems to have worked, and I'm on a stock ROM now but when I boot up it's stuck on the Samsung Galaxy S II logo where it keeps illuminating..
I'm not sure if that matters, if the store I take it to for money does end up testing it, at least they can see it turns on, just boot loops for some reason? :/
f8ct said:
I totally forgot about kies man, never even had it installed. It seems to have worked, and I'm on a stock ROM now but when I boot up it's stuck on the Samsung Galaxy S II logo where it keeps illuminating..
I'm not sure if that matters, if the store I take it to for money does end up testing it, at least they can see it turns on, just boot loops for some reason? :/
Click to expand...
Click to collapse
Wipe data/factory reset in recovery, should sort it.
Sent from my GT-I9100 using Tapatalk 2
My samsung galaxy s3 is stock 4.1.2 and I flashed a kernel and now it won't boot for anything won't even tell me if it's charging not sure if it will show up on Odin I just downloaded kies so hopefully that works, any ideas on what to do about it?
If it is wholly dead the only chance is a usb jig to restore bootloader. If you flashed a kernel for a different model then prepare to pay for a new motherboard.
Sent from my GT-I9300 using Tapatalk
What kernel you flashed??
It seems that you have flagged a wrong version of kernel for your android version...
Do specify your kernel and it's version cause you may have flashed kernel for 4.3 based roms...
Sent from my GT-I9300
Killerrr321 said:
My samsung galaxy s3 is stock 4.1.2 and I flashed a kernel and now it won't boot for anything won't even tell me if it's charging not sure if it will show up on Odin I just downloaded kies so hopefully that works, any ideas on what to do about it?
Click to expand...
Click to collapse
if you start a thread please mention details(flashed rom,kernal etc),then members can help you
Isn't the kernel (boot.img) independant of the bootloader and recovery? If so, why not simply load up the recovery and flash another kernel?
Kernel - This is always supplied with a ROM. It is the beating heart of Android. The ROM cannot function without the kernel. Since all ROMs include a kernel, if you're using a custom Kernel then flash a ROM, you will need to reflash the kernel again.
Please note, unlike the Galaxy S2 (and like almost every other modern android device) the kernel and recovery are independent. There is no link between recovery and kernel. Kernels are boot.img files.
Bootloader - this is what handles what you boot into. When you see the black Galaxy s III text, thats the bootloader. Its job is to handle the boot. It is responsible for booting into android, or if you manipulate the buttons in a certain way, it will boot into recovery or download mode. PLEASE NOTE, i9300/5 Bootloader is NOT LOCKED. DO NOT TRY TO UNLOCK IT. Only some US variants have a locked bootloader...
Download mode is part of the bootloader itself. Again, it is a mini OS. It is designed for flashing stock (official) ROMs onto the phone (Which you can do using Odin). It is also used by Samsung to detect the status of your phone (if you have modified it or not).
If you have (or had before rooting) an official ROM above 4.1.1, Your bootloader flash counter in download mode will change to "1" at every boot, if you have a custom kernel or recovery - even if you reset it with Triangle Away. See the return for warranty link later in this post to get around this.
To access download mode, turn off your phone. Home volume down + home then press power.
Click to expand...
Click to collapse
Source
If you read the op you will see why.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If you read the op you will see why.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I'll be quiet frank here and say that I'm rather clueless unless you're insinuating that flashing the incorrect kernel can somehow brick the device.
If so, how can it brick it if it is independent of the bootloader?
P.S. I'm not trying to sound like a know-it-all. I literally just want to learn since from what I've read, quoted and linked in my previous post; that's how I understood it.
Can you please enlighten me?
Apologies for veering off topic a bit.
Killing the bootloader is unusual, granted, but the wrong kernel will certainly blow the digitiser so blowing the cpu or emmc isn't impossible.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Killing the bootloader is unusual, granted, but the wrong kernel will certainly blow the digitiser so blowing the cpu or emmc isn't impossible.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Oh, I was not aware that kernels are capable of frying hardware. Thanks for the heads up. :good: I'll be sure to be a lot more careful when flashing then. It's not like there are a lot of kernels for the i9300 out there but still, better safe than sorry.
With regards to the original problem of the opening poster, I suppose he should probably bring it to a qualified technician for checking if he can't access Recovery or Download Mode.