yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] 0asis:
Unable to flash the bootloader with odin pc

Edit: Ok it worked. In fact when I used the standard boot in download mode it didn't worked (volume down+power+menu) and when I used the power buttons from my rom to boot in download mode it worked.
[Galaxy S III General] Notronic:
With Odin v3.04 all steps succesfull ;)
[Galaxy S III General] thegh0sts:
only if you care for the warranty.
[Galaxy S III General] Serdxx:
sorry perka,

can i ask?

so now, to fix this sudden death on SGS3, i need to flash latest FW, XXELLA?

or can i just flashed the bootloader from ur like other user?

is that stash from here : http://perka.zapto. BTU CSCorg/ in .tar?

(the bootloader XXELLA flashed on firmware XXELL5? is that possible?) or should full flash?

i read somewhere, BTU or the csc from UK one be able to get updates from KIES and OTA?

so can you attach BTU csc from ur stash? (sec_csc.BTU.PFS.zip, this right?)

i can't access ur website.(is that from XXELL4?)

need confirm, Latest :

1. bootloader fix sudden death?

2. kernel fix Exynos exploit?

if i wanna flash the entire rom (kernel, fw, bootloader, etc), which one would be better?

From KIES or ODIN? i read some ppl say ODIN, but some say KIES..

Sorry, it really troublesome questions, but i'll really appreciate help.
[Galaxy S III General] thegh0sts:
the only things that are "essential" is the bootloader really as kernels are flashed over when you install customs roms. though firmware for the modem can be flashed via CWM while things like nfc and the camera aren't flashable yet outside of a full firmware flash.
[Galaxy S III General] sssparkkk:
Ok guys, this thread is turning into a really confusing mess!

As I've been having spontaneous reboots a few times last week I'm eager to upgrade the FW in the hopes this might save me from the dreaded sudden-death probelm that's been hitting S3's all over the place here.

However, I'm on a rooted stock firmware that's the newest in the Netherlands (DLIH). Kies won't show me a newer version, and I really don't know whether flashing XXELLA with Odin will give me trouble (will it wipe? will I be unable to restore the phone to a state where I could receive warranty? etc).

So what do you guys suggest, just try it and hope this fixes the sudden-death problem?
[Galaxy S III General] cybdani:
Thanks AndiP!

Can you confirm too that sudden death is fixed in bootloader?

Greetings!
[Galaxy S III General] thegh0sts:
i don't think anyone can tell atm cos the SDS issue just happens and without warning. samsung needs to give an official confirmation.
[Galaxy S III General] Notronic:
Why the red exclamation mark is on screen, when I boot into Recovery?

When I boot normaly the device it is not there...
[Galaxy S III General] 0asis:
When I use normal boot I always have the red mark. Even after the use of triangle away. That's pretty annoying. Damn bootloader
[Galaxy S III General] GrayJack:
Neither of them will work in XXELLA ;)
[Galaxy S III General] TotallydubbedHD:
I can confirm a few things -and this will answer most people's questions.

FIRST:

-Reset counter as I was rooted and on a custom rom -> successfull and worked

-Flashed full firmware

-Counter still hadn't changed as expected

-Flashed CF root v6.4 (not auto root)

-Counter now increased to 1 with status as unofficial

-Mini exclamation mark at top left corner when rebooting

-Reset counter via triangle away

-Counter now back to official and 0

-Mini exclamation gone at top corner HOWEVER re-appeared when entering recovery & after hitting reset on the triangle away app, but on reboot disappeared again. So it is, recovery related, when it appeared back again. If people flash over CF AUTO ROOT however, they will never see the exclamation mark (followed by a triangle away)

-Device status within settings is modified (however I believe that's because of CF root)

SECOND:

-Rooted on XXELLA

-Used triangle away again

-Counter still at official and 0

-Device status within settings is modified (however I believe that's because of CF root)

-Full wipe via CWM

-Battery pull

-Entered download mode - Count back to 1 with system status as official and current binary as custom

-Re-flashed XXELLA stock

-Entered download mode - Count back still at 1 HOWEVER with system status and current binary as official

-Flashed CF AUTO ROOT (2012.12.04 --- CF-Auto-Root) this time

-Entered download mode - Count back is NOW at 2 with system status and current binary both as CUSTOM

-Still no sign of the exclamation mark so far in this second run

-Resetting flash counter using triangle away

-EXCLAMATION MARK comes back at the top left when entering to reset

-After reboot - device status is modified

-Entered download mode - Count back is now at 0 system status and current binary as official

THIRD:

As I was previously rooted before I couldn't check this Exynos Abuse thing properly, so:

-Re-flashed XXELLA stock (remember my counter and everything are already reset from above) - However device settings is modified, due to no wipe.

-Full factory reset via settings

-Device status within settings is now NORMAL

-Installed Exynos-Mem Bug checked : it said it is affected

-Installed CF's app of Exynos Abuse v 1.4 - and I couldn't root, nor fix the exploit.

-I thus believe CF, via his app, in saying the abuse is now fixed

Video will be coming soon ;)

I hope this helps people with the questions.
[Galaxy S III General] Perka:
I will try to make a cache.img in a tar to be flashed with odin.

BTU as default.
[Galaxy S III General] SavanTorian:
any official confirmation from samsung for the sudden death fix @ XXELLA at all? if not , then not. :rolleyes:
[Galaxy S III General] yahyoh:
not yet

and if this is the fix WTH Samsung waiting for ???? they only send the update to UK :eek::eek:
[Galaxy S III General] GrayJack:
For what? Everyone can add his own cache.img and hidden.img to the ROM.

What I want to say: if you have some installed CSC that is not included in XXELLA - you must add cache.img and hidden.img from your latest 4.1.2 ROM to XXELLA tar file - and that's it! After flashing CSC remains the same.

It is a problem (it can be solved - but in not very convenient way) to change CSC on already installed XXELLA - because neither code, nor СSС Select, nor Nitrality won't work on it.
[Galaxy S III General] TotallydubbedHD:
besides actually manually checking - can any of you get into the CSC menu?

I can't with either the app or manually putting the IEMI in the dialler
[Galaxy S III General] Odia:
You can PM me, I will tell you how to reproduce it and why it happens ;)
[Galaxy S III General] pRo_lama:
Hi guys.

I have this PDA, CSC and MODEM. Can I use this fix or I need to change CSC from XEO to BTU and then apply fix. Or I can just make Method #2 with Kies ???Thanks

Android Version: 4.1.2 – Build JZO54K

PDA: I9300XXELKC

CSC: I9300OXXELK4

MODEM: I9300XXELKC
[Galaxy S III General] lockmunk:
hey..can u explain more? i also have same problem with you...
[Galaxy S III General] redondogabriel:
no root, no custom recovery, no custom kernel, all is stock, i flash it via Odin
[Galaxy S III General] Perka:
Found a way to change csc :)

Just need to make a backup and test :) sweet!
[Galaxy S III General] Crest+:
Yep method 2 directly is fine. It will automatically change your csc to default therefore no problem recieving updates .. no need to change csc.
[Galaxy S III General] siapakahaku:
So..the bl contains fix for SD

If i repack XXELLA system.img and boot.img with different cache.img, hidden.img and modem.bin and recovery.img

And then flash with odin, still not fix the bug? And i will have red counter at top left corner when i flash cwm recovery?
[Galaxy S III General] delsus:
Nice Perka apk to follow I take it?
[Galaxy S III General] Perka:
well see :) gimme 1 hour
[Galaxy S III General] delsus:
I will :)
[Galaxy S III General] mrjane:
I did the update via Kies (it appeared regularly not with the entering of the serial, I am not rooted and on stock ROM) and I am still on the old bootloader as far as I can tell, the part:

androidboot.bootloader=I9300XXELLA , androidboot.serialno=4df1e0591c214f97

says:

androidboot.bootloader=I9300XXBLH3 , androidboot.serialno=4df1499303ff5f5b

in my case, why would this happen?

Regards
[Galaxy S III General] 0asis:
I was on a custom rom. So when I pressed the power button for a long time I was able to restart in download mode, recovery mode or normal reboot. If you are on a custom rom like me try to restart your device in download mode by pressing your power button. Then connect to odin and try to flash the bootloader. If odin fails at doing it, unplug and restart your device in download mode by pressing the volume down+menu+power.
[Galaxy S III General] Perka:
here it is, pls spread this thread as I cant post it every time some one ask how to change CSC ;)

enjoy!

http://xdaforums.com/showthread.php?p=36224599#post36224599
[Galaxy S III General] delsus:
Sweet, I'll spread the word :)
[Galaxy S III General] syamsoul:
Want to ask..just for understanding... i just check my csc and it still the same as when i buy this phone which is XME even not in the list of csc which can be chose

My question is, how can it changed when flash rom? And how mine not change? Is it because i didnt factory reset first? When actually the phone select csc , is it from factory or on the first boot?

Tq in advance
[Galaxy S III General] Perka:
Yea, I am no sure why csc dont flash some times, or change.

This is the fw you need to get the cache.img

PDA Modem CSC

I9300XXDLJ1	I9300DXDLI5	I9300OLBDLJ1	10.2012	XME	Malaysia	4.1.1	288630
[Galaxy S III General] :
kies doesn't work, initizialiton whatever doesnt support GT-I9300
[Galaxy S III General] delsus:
Reinstall drivers and try again, if that doesn't work reinstall Kies and try.
[Galaxy S III General] TotallydubbedHD:
I've had 3 people BRICK their devices using KIES (they were telling me this via my site and seeking help) - yup - KIES.

They were even on fully official roms too.

I've had no one brick their devices on ODIN.

I trust ODIN over KIES.

Kies IS Odin, but with a pretty skin and a HORRIBLY slow processing lag.
[Galaxy S III General] Theshawty:
Good. Kies is **** anyhow and you can get along perfectly well without it.
[Galaxy S III General] TotallydubbedHD:
How dare you insult Kies like that!

It has been there since day one, and is a brilliantly engineered software that does everything you need; it even gets you free cookies if you look hard enough behind the coding of the software! Samsung actually send you out some! SO AMAZING!

I'm only joking, but I love cookies.
[Galaxy S III General] Theshawty:
Oh yeah, I love cookies too. And bacon. Man, you gotta love bacon. Bacon's awesome.

*Homer Simpson drewl* Mmmm... Bacon.... *gurgle noise*

Wait, how about, uhm.. Stay with me now.... Uhm, cookies....hold on, I know cookies are awesome, but let me finish. Where was I? Uhm, oh yeah, how about cookies....with BACON on top?! Amazing!
[Galaxy S III General] delsus:
No need to hit on me about it, someone was posting with a Kies problem, I was trying to solve a Kies problem. I know everything you said but some people don't some people want to use Kies over Odin and I have seen someone here say "I prefer Kies over Odin because it's samsung's official way of flashing"

If you want to tell someone all this tell the person have problems with Kies, I not the person trying to help them.
[Galaxy S III General] cyberdroxxx:
My CSC changed to XAELLA from XME ROM. Everything is working and looking good so far since I flashed XXELLA fw.

I'm using it now in Malaysia actually without any problems.
[Galaxy S III General] chudy_85:
hi nice tutorial

but what about busybox??? When i install root using cf auto root and install busybox to my system and use triangleaway to reset my counter i be have custom binary download:NO , current binary: samsung officjal , system status: officjal ??? I ask you because some apps need busybox to work. Can you try how its work when you install busybox and reset status
[Galaxy S III General] TotallydubbedHD:
Sounds like an epic-meal TIME.

I've already eaten my brunch for today, but next time I'll keep that in mind cookies with bacon. Bit[sensor] love cookies.

Cause we [beepin] can.

Add Jack daniels sAUUUceee to it. Youtube money, get to know playa.

:D

OK I'll stop.

(maybe a little more won't hurt)

Oh i know you were quoting someone - just thought to add my input :)

I can't really test no more- as I'm on Perka's deodexed rom.

If you still find it valuable for me to test, then link me a free app that needs "Le busybox"

PS.

This is what Perka has done to his ROM (many other things included, but those are the ones that should "concern you")

Deodexed

Rooted

init.d support

Busybox
[Galaxy S III General] nunomax:
it works as described after root, download mode is ok but recovery shows the exclamation mark
[Galaxy S III General] corkie1:
IF anyone is interested here are my findings

cf root 6.4 works fine on LLA

Triangle away works fine on LLA

Once you defrost sysscope your about device, status goes from modified to normal so you can OTA again (may need to reboot twice after the defrost) so no need to flash stock to OTA
[Galaxy S III General] rmsa786:
Is that using Titanium?
[Galaxy S III General] corkie1:
Yip. Titanium. And on a side note my phone just randomly rebooted while typing this! Has never randomly rebooted in the 6 months I have it. Let's hope LLA isn't buggy......
[Galaxy S III General] chudy_85:
i do it that same as movie but i use cf auto root and reset counter

in download mode i have officjial but when fone is scaning system in seting i have modifited meybe because my csc is xeo

but when i check updates using ota i have Instaled latest firmware

can sombody check this using different csc code

update

Iinstall busybox in xbin and in download mode i have all officjal

info

when have stan modiffide we open again triangleaway and we see that our counter shows 1 but in download mode we have officjal all and counter binary is 0
[Galaxy S III General] rmsa786:
Cheers for that tip! It works! :D Also TA shows as being Official even though its rooted.
[Galaxy S III General] Odia:
DO NOT FLASH THE NEW BOOTS

They contain a blacklist which I think will stop older boots being installed, more news later after I finish my analysis.
[Galaxy S III General] nunomax:
I confirm that - I flashed it via ODIN with new XXELLA and after that I've tried several times to flash the old ones and it doesn't work anymore - it fails on ODIN and forces me to flash the ROM again to get device to work.
[Galaxy S III General] :
2 late :( i flashed via odin do i have the new bootloader?
[Galaxy S III General] Odia:
Thanks for confirmation, do not worry I am sure I will have an older boot which does not appear in the blacklist.
[Galaxy S III General] ricnar456:
Have sense if old bootloaders have sudden death bug protect users from return to dangerous bootloader.

Ricnar

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] yahyoh:
@Odia but what if the new bootloader is the fix for the sudden death or maybe it contain the fix
[Galaxy S III General] corkie1:
What would this prevent you from doing? Why would you need an older bootloader
[Galaxy S III General] zadusimple:
I flashed the new bootloader but triangle away is not working. Is there a way to flash the older boot loader without wipe?

Sent from a better Galaxy designed for humans!
[Galaxy S III General] nunomax:
you cannot remove the little red exclamation in case you root - with triangle away it's working on download mode, but in case you access recovery it will increase the count to 1 - from my experience
[Galaxy S III General] yahyoh:
so what!! that's how it work on Gnote2 BTW

every time u go to recovery ( non stock one's ) it will count 1 in the flash counter :p but without the little red exclamation
[Galaxy S III General] delsus:
Triangle away does work with this bootloader, but if you have a custom kernel or recovery the binary counter seems to be resetting to 1 on reboot, or when you enter recovery. I am using stock recovery and rooted, had a counter of 1, ran triangle away and it is now 0, and sticking there.
[Galaxy S III General] zadusimple:
So is it safe to flash the new bootloader?

Sent from a better Galaxy designed for humans!
[Galaxy S III General] nunomax:
no problem at all - only in case of sudden dead it will show counter 1 on download mode - the only mode reported to be acessed - and SG can refuse warranty - that's why

---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------

noob question, how do you root and stay with stock recovery ?
[Galaxy S III General] Odia:
I can think of at least 1 way to flash the old bootloaders, maybe 2, but second way maybe blocked depending on what they have done inside ARM Trust Zone (tz.img).
[Galaxy S III General] yahyoh:
ohh that sucks :(

maybe u can put the signed SU zip on ur external sd and flash it ( not sure ) but the download mode will show unofficial if u have root i think :/
[Galaxy S III General] 75markus:
confirmed, same for me, i´m unable to flash old ICS bootloader after XXELLA bootloader :eek:

but i didn´t reflash ROM (running CM 10.1), just reflash the new bootloader XXELLA with odin again and you are ready to go :)

so, it´s no biggie for me, i just live with the small ! when booting ...
[Galaxy S III General] delsus:
Use CF Auto root instead of CF Root.

CF Root = CWM

CF Auto Root = Stock recovery.
[Galaxy S III General] thekoRngear:
So, if I flash XXELLA via PC ODIN + Then CF Auto Root via PC ODIN+ Then install TA 2.40 and reset It>> then it will stick to zero, right?
[Galaxy S III General] Perka:
What is boots? Bootloaders?

If so can you guys post the "old" ones?

EDIT: and I dont get it, what is it that you cant do?

EDIT2: And its all this for a small ! ??
[Galaxy S III General] GrayJack:
Taking into account the service changes the motherboard or the whole phone - I don't think it is possible to run download mode after sudden death ;)
[Galaxy S III General] delsus:
Pretty much, download mode will report the the device is official.
[Galaxy S III General] Notronic:
The problem is, when you boot in the Recovery and show to flash counter again,

it goes back to custom and counter is of one again...
[Galaxy S III General] delsus:
Only with custom recovery (CWM or TWRP) it doens't reset to 1 with stock recovery.
[Galaxy S III General] Perka:
Meh I dont get it, if you dont want the counter to go up etc etc dont flash!

Just wait for updates from kies!
[Galaxy S III General] thekoRngear:
What he flashed in the video? CF Root or Auto Root?

Edit: I got it. It was CF Root.
[Galaxy S III General] delsus:
I was just testing for myself after I rooted. I reset my counter from 9 before I flashed stock because I was going to go unrooted.... That idea lasted a long time :p

I'm not scared of a flash counter, just wanted to make sure so I could give first hand advice.
[Galaxy S III General] chudy_85:
i use cf auto root and use triangleAway and i have problem to install android 4.1.2 XXELKC i try donwgrade using 3 file rom and i have file because sboot.img stoped

i fight 30 minet with my fone and i win. If any body have that same problem dont were do it this

install again LLA

when its finish you see android robot and wait

after the extract baterrie before showing samsung logo and put our batteries back and enter the recowery and do it wipe system / data and cache

then select reboot and before showing the samsung logo remove the batteries and put our back and enter the download

and install rom using odin

i installed at this moment the following roms android 4.1.1 and 4.1.2

can somebody August is useful
[Galaxy S III General] Perka:
Really? google what is what and you have your answer ;)

Tip: cf-auto root dont have recovery.
[Galaxy S III General] gaspernemec:
Sudden death fixed by new bootloader or rom/kernel fix? Since I got red exclamation mark after flashing it.....had anyone flashed old bootloader on xella?
[Galaxy S III General] Rob2222:
Hello Odia,

is it possible to access/copy bootloader partitons with dd? It is anywhere in mmcblk0, right? (mmcblk0boot0)

I dd'ed those partitions a while ago into files for backup purposes.

I don't want to restore a old bootloader at the moment, but would it theoretically be possible to restore the old bootloader with dd from such a backkup file?

BR

Rob
[Galaxy S III General] Painman1963:
Thanks

Thanks for the heads up. The only change I made was to use CF Auto Root instead but followed the rest entirely.

OTA now working and status is normal :D
[Galaxy S III General] odsso:
Hey I'm having a sudden death problem that I can't switch to recovery mode nor downloading mode no response at all from the device I don't really find the solution here! :crying:
[Galaxy S III General] delsus:
Are you sure it's sudden death, as in it was working fine, you did nothing and it died. Did your flash fail and it stopped working? Did you loose power running TriangleAway?
[Galaxy S III General] zadusimple:
So what is the first method?

Sent from a better Galaxy designed for humans!
[Galaxy S III General] TotallydubbedHD:
Info about the firmware I found accidentally today:

http://xdaforums.com/showpost.php?p=36235077&postcount=7505
[Galaxy S III General] odsso:
yup its sudden I was using it then left it on the table a sec take it again pressed the home button boom nothing!! I was using jellybean 4.1.2 Cyanogen mode 10 . TriangleAway I didn't use it.
[Galaxy S III General] TotallydubbedHD:
if this is right - samsung are becoming the new apple in the tree.

Which means soon enough, I'll dump their phone in the bin, and get myself one that isn't being a pain in the backside to flash, and do WHAT I WANT with my BOUGHT, UNLOCKED f'in phone.

I'll confirm when I have time.

So basically flash any older version, and it should FAIL in odin correct?

This is after or without a full wipe in recovery?
[Galaxy S III General] Sad56:
Do you use the new bootloader ?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] zadusimple:
So, what are the disadvantages of flashing new bootloader, can someone please summarize? Thanks in advance

Sent from a better Galaxy designed for humans!
[Galaxy S III General] Notronic:
That´s right, but Custom Recovery don´t works.

It´s a red Triangle there...
[Galaxy S III General] TotallydubbedHD:
so far, it is the fact that you can't flash back an old bootloader with ease.

other than that, all positives.
[Galaxy S III General] zadusimple:
But can i flash older Rom using Odin? For example Check Rom ressuruction edition? In case I need it?

Sent from a better Galaxy designed for humans!

---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------

And why will someone need old bootloader, sorry for a dumb question

Sent from a better Galaxy designed for humans!
[Galaxy S III General] TotallydubbedHD:
that's not a dumb question.

Logically I would say no, why would anyone want to go to ICS bootloaders.

Does that mean you can't flash old roms?

That's beyond me too.

I think you can flash roms with the same bootloaders. As to which bootloaders and for which that applies...I have NO IDEA! :confused:
[Galaxy S III General] Rob2222:
Very old S3 bootloaders didn't increment flash counter when installing custom recoveries like CWM.

Newer S3 bootloaders do increment flash counter when using custom recovery.

However, if new bootloader protects from sudden death... who cares flash counter.

BR

Rob
[Galaxy S III General] dkionline:
The problem of most of people is the garanty when the phone brick. You can flash old roms, only the bootloader will be still the same. This change of bootloader can be a start of detecting the problem with sudden death.
[Galaxy S III General] Blazy56:
they fixed the SUDDEN DEATH bug ?
[Galaxy S III General] TotallydubbedHD:
interesting revelation I must say.

Well we shall see what Odia (or anyone else as a matter of fact) finds in his analysis.

PS. Flashing back to stock + counter reset is for warranty and eBay purposes ;)

That's the reason over 79,000 have watched my S3 video, and over 60,000 on the two S1 videos
[Galaxy S III General] yahyoh:
no one know :fingers-crossed: