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
Related
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
Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
I once went into CWM, mounts and storage and formatted everything... Worked for me. Well if by worked you mean hard bricked
Sent from my GT-I9100 using Tapatalk 2
DPluss said:
Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
Click to expand...
Click to collapse
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Moving to Q&A, please post all future questions there.
Thanks
The-Hulk
Poroto said:
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Click to expand...
Click to collapse
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Deleted.
I would try using a firmware not meant for your phone and pull the plug out half way through flashing it with odin.
Then hope it gets hot around the camera and wont come on.....lol
Jokesy said:
Let's be reasonable here.
1. If you are not the first owner of the phone, then you might not be lucky with warranty service.
2. What are the issues you are facing? Can you list them?
Click to expand...
Click to collapse
umm.. i'm the second owner, of course first, i will go and see my provider, and ask them about the warranty(will not bring the phone in first lol)!
Basicly the warranty sheet has no personal information, just the phone type, the IMEI, and the date when the other bought it!
The issues are, serious overheating around the camera area...it can never be interrupted, if the phone is on, it keeps overheating after about half an hour, I don't know what is the ideal temperature of a working device but after an hour I can't hold my phone without a thick case(or gloves lol)! It heavily affects the camera, focus has major issues, sometimes it says "can't connect to camera", touchscreen can be a little laggy when its hot...When I bought it from previous owner I didn't noticed it because on forums people kept complaining about heating, but then I realized that I was an idiot...I tried stock official roms, GB,CSI, and now JB, nothing changed!
DPluss said:
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Click to expand...
Click to collapse
it only works if you have a faulty emmc chip
Rick Roll said:
it only works if you have a faulty emmc chip
Click to expand...
Click to collapse
How do I know that? My phone was first out in 31.10.2011.
DPluss said:
How do I know that? My phone was first out in 31.10.2011.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=es
Deleted.
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Jokesy said:
Ok.
very simple way to hard brick your phone.
Flash the wrong bootloader!
PS: first confirm that you can claim warranty service.
Click to expand...
Click to collapse
I will confirm it!
So for example if I flash another phones boot.img throught Odin than it's a full disaster that can never be repaired?
Thank you!
Siyah kernel 3.1rc6 lol
DPluss said:
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Click to expand...
Click to collapse
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
theunderling said:
Siyah kernel 3.1rc6 lol
Click to expand...
Click to collapse
Lol, yeah, S3 kernel, I think that should work... I really want to do something that can't be reversed
What do you think? If I flash it, it would still go to the first screen? The one that says "Samsung Galaxy S2", or no response for ever?
Poroto said:
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
Click to expand...
Click to collapse
Thanks! I almost have all the info I need! Umm.. so if I wipe it's unreversable, and if I flash a wrong bootloader or kernel? Could Jtag service fix that?
Deleted.
Jokesy said:
boot.img as far as i know is the kernel.
1. you need to download bootloader.tar Galaxy NOte GT N7000 (or any other samsung phone) and flash as pda via odin
or
2. you can download Galaxy SII bootloader.tar here.
then remove your cable as soon as odin starts writing the bootloader.
Gameover!
Click to expand...
Click to collapse
Thanks, haha I think I will try to pull out the cable when the flashing start but first I will ask my provider about the warranty of course
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.
Hopefully this is the right topic to ask my questions:
I have a S2 i9100. The phone is not working anymore, i can acces the recovery and flash a rom but it is booting and not getting further then the boot animation. No bootloop, just stuck at the bootanimation.
Can't connect to Odin. Anyone having a suggestion how to get it working again? I regularly flash roms on a HTC, this Samsung is new for me. I saw the topics about soft-bricks but imo is this something different.
Thanks in advance!
Look for hopper8's troubleshooting guide.
What did you tried to flash anyway?
If you can access recovery you can flash a custom kernel. That'll enable you to flash pretty much whatever you want.
Sent from the little guy
gastonw said:
Look for hopper8's troubleshooting guide.
What did you tried to flash anyway?
If you can access recovery you can flash a custom kernel. That'll enable you to flash pretty much whatever you want.
Sent from the little guy
Click to expand...
Click to collapse
The phone broke when a collegue was using it. It had CM10.1 and after some strange behaviour a reboot caused the non-booting problem. Zo a factory wipe and trying to flash another ROM, (something like Wanamlite), still the phone won't boot.
Basically i want to flash a rooted stock ROM.
Read Hopper's thread as advised.
Thanks a lot. Did that before and i think i've got the eMMc brick situation. Thanks for your help!
If the phone was running CM10.1 then brickbug is NOT the cause.
Brickbug affects stock ICS.....not custom JB..........
Sent from either my S2 or my W via XDA developers app
gastonw said:
Look for hopper8's troubleshooting guide.
What did you tried to flash anyway?
If you can access recovery you can flash a custom kernel. That'll enable you to flash pretty much whatever you want.
Sent from the little guy
Click to expand...
Click to collapse
Well, i can flash a custom kernel and i can flash another ROM. But the phone's still not booting. Hanging on the bootlogo.
The only option left seems to be the pit flashing.
It was indeed not the brick bug, i runned a control tool and the memory seems fine.
You're able to flash a ROM and custom kernel so you want to flash a pit file?
By doing that you might not be able to flash anything afterwards.
Sent from the little guy
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.