Sadly, 4 of my friend birck their phone when they are flashing the new Bada 2.0. Do you have any solution to bring their phone back
WTH !!!!!
How did they brick them???
Is the flashing was killed in the bootloader step or any other step
if in the bootloader then it is full brick and the will need a fix with JTAG
If in any other step just reflash the files again
Best Regards
One of them forgot to check Full download, other didn't load the usb driver. Others can't understand what they did wrong. But they cant switch to Download mode now.
same one can help you maybe need JTAG
Sometimes, pulling the battery out for a few minutes, works. Otherwise, service is needed.
Thank you for your suggestions, I will tell your ideas to my friends. Hope one of them works.
bad luck
its working great here, except for video recording xD..
and i cant connect to kies, so my contacts are not usable
Nobody cant brick wave, just litlle difficult to reflash. But dont worry you can reflash it !!!
secretwhite said:
Sadly, 4 of my friend birck their phone when they are flashing the new Bada 2.0. Do you have any solution to bring their phone back
Click to expand...
Click to collapse
The obvious 1st question to ask is to what did they try and flash it to?
The current Bada 2.0 is ONLY for the S8530 Wave II and NOT the S8500 Wave I
If they tried to flash it on the Wave I then "Theres your problem!!" Like Jamie Hinaman from Mythbusters would say
toxicdust said:
The obvious 1st question to ask is to what did they try and flash it to?
The current Bada 2.0 is ONLY for the S8530 Wave II and NOT the S8500 Wave I
If they tried to flash it on the Wave I then "Theres your problem!!" Like Jamie Hinaman from Mythbusters would say
Click to expand...
Click to collapse
Like I said in my second post, one of them dorgot to check Full download, other forgot to load new usb driver. And they all have Wave II
secretwhite said:
Like I said in my second post, one of them dorgot to check Full download, other forgot to load new usb driver. And they all have Wave II
Click to expand...
Click to collapse
Than I retract my statement
Usually once the bootloader has been loaded you can just reload it without doing to bootfiles again and it should work. But if their bootloader is screwed they will have to take it in to my knowledge.
Just a thought though... Were some of theirs branded? Because i know the bootloaders for branded phones are a bit different?
Their bootfiles screwed probably. I2m still searching for any solution
secretwhite said:
Their bootfiles screwed probably. I2m still searching for any solution
Click to expand...
Click to collapse
I'll google some for you as well but seeing as we dont know much from the new bootfiles i doubt there will be anything.
As a suggestion to them let them open up Kies and then plug in the phone in whatever state it may be.
There is a emergency recover mode that it should enter if it cant boot and Kies will then just revert to the latest "available" firmware.
Hope this helps but I will see if i can find something else that might help as well
They have one problem with Kies. It asks some kind of password but they cant find that password. This is their last solution unless someone tell different solution.
secretwhite said:
They have one problem with Kies. It asks some kind of password but they cant find that password. This is their last solution unless someone tell different solution.
Click to expand...
Click to collapse
Ye i dont know the password either. It should provide it on the phone itself from what i could understand when it goes into recovery mode.
If its not displayed on the phone you wont have a code to put in there
I have no idea for S8530... but for chinese S8500 few Bootloader combinations were different. Some structure differences.
If you or your friends all from China... maybe chinese Firmware not allow this bada 2.0 Firmware...
Best Regards
@kadavil i have yesterday synced my contacts, kies is no showing firmware version but it worked for me on 2.0. It is like hidden, the version dont shows up, have you installed the new drivers in the folder before?
I2m from Turkey so my friends. We couldn't repair their phone and they will send their phone to service tomorrow. Thanks for your solution but complete kernel change ruin our repaie attempt.
@ secretwhite
Sorry, my fault. i'm sometimes blind and very tired...
Anyway. Their are some Operator/Branding related differences ... example chinese FW from S8500:
ZN...
ZC...
Or for instance adress changes S8500/S8530...
From S8530 seems more Bootloader Versions...
Maybe you should post your prior FW Version, before dead.
So maybe other users from turkey prevent "damage" their Wave II...
Best Regards
I also got same problem, my SW ver. is middle east but i tried to flash an Europe vers. of bada 2.0. it was stacked at flash starting point and i can still able to put to download mode, can i re flash it back to bada 1.2 or should try again 2.0 or any other method pls, help.
mylove90 said:
WTH !!!!!
How did they brick them???
Is the flashing was killed in the bootloader step or any other step
if in the bootloader then it is full brick and the will need a fix with JTAG
If in any other step just reflash the files again
Best Regards
Click to expand...
Click to collapse
Related
I dont think the 3 button recovery mode "fix" that samsung released for Bell Canada i9000m and that was ported to work for other models is really a "Fix".
As dicussed in other threads, the original bug is on the PCB. It's a timing issue on the motherboard. The "fix" installs a software hook in the 4th level bootloader to the 3 buttons in order to trigger the recovery mode.
If you brick your phone such that it does not get to the 4BL stage ...
OR
If your phone freezes even after the 4BL stage ...
then you are **** out of luck.
Only a phone that had the 3BR working before the fix or a phone that gets a MB changed will be able to recover from being bricked.
This fix is only slightly better than installing a software that triggers recovery or using adb to force recovery mode. Basically it only works in conditions where you would not need recovery in the first place.
thats an assumption, but where is the proof and source?
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
bigl666 said:
thats an assumption, but where is the proof and source?
Click to expand...
Click to collapse
I did say "I think".... but added an ? to the title.
Based my opinion on these posts:
http://forum.xda-developers.com/showpost.php?p=8217641&postcount=390
and the serious part of this one:
http://forum.xda-developers.com/showpost.php?p=8156981&postcount=287
My reply from another thread: http://forum.xda-developers.com/showthread.php?p=8230653
That was my first hypothetis when Samsung released the fix.
That's why I asked technical details and get some after contacting Samsung technical department, to finally speak with a tech, instead of those clueless helpdesk first and secondline helpdesk coworkers. But he couldn't give me more pointers, other than the original working 3br devices do not use the spl at all.
My hypothetis seems right if the bootloader gets overwritten by other firmware who's using spl on the respective partition.
My assumption, like I said before in this thread, is that the original 3br working devices gets triggered via the pcb, which loads the pbl with the safemode, if not on a dedicated module, maybe... That way, the users of such device can always be assured they can flash every firmware. This is how it's done with other many devices too. And that's exactly why I don't buy the story of 'not'-controlled batches by another guy here on the forums in another thread. I can understand why and that's why I'm so disappointed they continue to ship the phone with Android.
If you are like me, you need to test new firmware releases in order to test your own written code in Eclipse. Plus, I want the latest releases...
That's why I suggested to get your mobo replaced now you have the change, before Samsung goes with the spl fix as a standard procedure for future bricked phones.
But, for now, we will not know, unless somebody is disassembling a working 3br and a non working 3br device and have the electronic skills to confirm this.
Click to expand...
Click to collapse
blackdeath09 said:
I don't know about you but for me the recovery menu fix works great. I rooted my phone after I used that fix with the update.zip method so unless you have proves I think is better to not scary users.
Click to expand...
Click to collapse
There is no proof, if there was, there was probably a fix already or at least the technical details published.
xtrememorph said:
I thought three limit was cause by the telco not Samsung? Read it from a post where the telco confirm they disable it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, I got my phone from a Samsung distro, not from any provider and it has 3br disabled.
blackdeath09 said:
The idea is I don't think Samsung replaced the motherboard of the mobile phones and the prove is that Samsung Canada or something posted a method to enable recovery mode back.
Click to expand...
Click to collapse
That could be, then if you have 3br enabled with a firmware without the integrated fix back, it's probably a new phone without replacement.
The prove that a temporary fix exist doesn't mean it's permanent, which is for the original 3br enabled devices.
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
blackdeath09 said:
So then someone should brick his phone after installed the fix and see if he can repair it back (as a user said in the original thread)
Click to expand...
Click to collapse
Under what kind of circumstances?
That doesn't prove anything, other than the fix works if the sbl isn't overwritten.
Then flash back to a firmware who does without the fix and tell me the results.
I've read in http://forum.xda-developers.com/showthread.php?p=8230653 that someone flashed back and the fix is gone. Now you have your proof this fix isn't permanent, like I already said a bunch of times. I believe it was firmware JM1 if I can remember correctly. It was tested one time though. Try it and please report your results back.
Proof will come when someone bricks a phone other than by flashing firmware and can not use the 3BR combo even though the "fix" was applied.
Prroving that the "Fix" works is just about impossible. No reports of the condition described above will constitute proof that it works.
I do have an idea for a test:
- With battery fully charged, USB unplugged and phone off,
- Initiate 3BR.
- Calculate time to reach recovery screen.
Compare "fixed" phone with originally working one.
If different assume that fix is not as good as a real working 3BR phone.
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
Click to expand...
Click to collapse
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
davidke said:
Like I said, proof comes when someone recovers from a brick OTHER than because of a bad flash.
Because, in general, that doesnt touch the BL.
Click to expand...
Click to collapse
why does it really matter? isn't that normally the problem anywayz, bricking from a bad flash?
but then again, this appears to be one of those you can't prove anything to be true, but only to be false scenarios...
TriC_101 said:
My Buddy just had a bad flash and and bricked the phone.. and the recovery saved him so yes it does work....
he did not have the 3 buttons working before but did the update and started flashing roms.. and it saved him... its not a hardware issue.. its always been software.
so it does work.. if this fix didn't come out he would have a good door stop.
Click to expand...
Click to collapse
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Casio1987 said:
I hope Richthofen and / or some other members can exclude this theory by hexcomparing bml1 from working and not working 3br devices and analyze that, so we can exclude that. If it matches, then it's probably a hardware issue. Like I told you before... Android already adressed the safemode space. So the parameters must come via the 3 buttons by pcb. You are happy now?
Click to expand...
Click to collapse
It seems BML1 to BML4 that triggers 3BR recovery mode are differents between countries and could be related to CSC version.
So it seems to be a software problem.
Until you dont flash BLM/SPL everything will be fine, just check before flashing.
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Richthofen said:
I find it hard to believe that it would be a hardware issue.
The first retail European I9000 phones had I9000XXJF3 factory firmware version.
As far as I know all of them had a functional 3-button "wake" function for download and recovery modes.
When Samsung started using I9000XXJM1 as a factory firmware, I have seen only one phone with a functional "3-button wake". And even with that one I could not tell if it was a brand new one or a factory refurbished one.
For some odd reason the first release using the new secondary bootloader was I9000XXJM1. All of the previous versions (from I9000XXJE2 thru I9000XWJFF) have been using the same bootloader. As far as I know none of these phones ever had problems.
Also there is no indication that Samsung would have modified the hardware.
Samsung always makes bulletin about the changes in hardware and I have not seen any. Also the hardware revision has remained the same from the start.
Click to expand...
Click to collapse
Very odd indeed, because how is it possible that some have working 3br and others not with the same firmware jm1, coming from the same csc, coming from the same batch? Maybe the 8gb differs from the 16gb (I don't think so). Maybe asked too much, but it would be great if people can start publishing all their bml's, with the exception of the containing imei.
Because the safemode must be somewhere and it isn't in bml4.
Maybe there is a special ic for it, but it's locked for the 3br disabled phones and it's overridden by the sbl.
Are you sure there isn't a special module with the safemode in it?
That would clarify why the hw still preserves the same revision.
Casio1987 said:
I disagree.
Without pcb, rom and human-machine-interaction, there is no way the bootloader will load. So you are telling me it's not a hardware issue that 3br isn't working? I fully disagree. IT IS. Why? Because Android already have the recovery / download mode adressesed... Please study mobile phone architecture or at least computer architecture and how the android kernel and os works.
No one knows the exact architecture of sgs here, but one thing is for sure. 3br isn't working, because it doesn't get handled BEFORE spl... And if it is, it's disabled on purpose in bml1 and otherwise there is probably another rom, handling all 3 buttons first, before launching ipl.
Please tell your buddy to flash back to JM1 and let his phone brick and post back your results...
Click to expand...
Click to collapse
I do know how phone architecture works and computer architecture as well....... in the end its very simple... it works its saved lots of people from having a bricked phone.. and the recovery mode is different between countries. besides you should not be flashing the SPL/BLM in the 1st place. and like you said your self you don't know how the exact architecture works on the SGS so how can you say its not a software issue. if you fully don't understand it.
There's to many people have brick wave i and ii
and they dont have second battery to reflash again or they dont know how to do to reflash !!!
If you dont have other battery or you're not know how to reflash dont flash this firmware !!!
The problem its bootfiles on news firmware !!!
Before flash take's last bootfiles like KG6 !!!
Tigrouzen said:
There's to many people have brick wave i and ii
and they dont have second battery to reflash again or they dont know how to do to reflash !!!
If you dont have other battery or you're not know how to reflash dont flash this firmware !!!
Click to expand...
Click to collapse
If ppl follow the flashing instructions you wont brick your phone
I flashed mine rought 12 times today between KG7 and KG6 with various hacking in between to try and get the CSC pre config's working
If you just follow the tutorial you wont brick your phone. Dont get clever. Just follow the instructions
toxicdust said:
If ppl follow the flashing instructions you wont brick your phone
I flashed mine rought 12 times today between KG7 and KG6 with various hacking in between to try and get the CSC pre config's working
If you just follow the tutorial you wont brick your phone. Dont get clever. Just follow the instructions
Click to expand...
Click to collapse
Im make to many flash never got this problem and make's to many modified firmware too
Pro flasher have a same problem maybe your Wave you buy it unlocked.
Having flashed my wave through various firmwares, never once has it bricked, it was bought with no sim lock etc so I didn't have to fiddle with it. Follow a tutorial and you will be fine guys
Read my latest comment in "Warning from Samfirmware - Dont Use Custom Bada 2.0 ROMS" and my thread "XPKG7 CSC pre-config doesn't work...". Those are the only two issues with this firmware.
We find the problem its bootfiles !!!
We flashed with KG6 bootfiles
i dont understand why everyone has to open a new thread who recognized a danger coming up. i mean its their problem if they cant wait...
first time flash got a blue and green screen with serial port error (my hand knocked my phone dwn and got disconnected i guess)
second time, no issues
Tigrouzen said:
We find the problem its bootfiles !!!
We flashed with KG6 bootfiles
Click to expand...
Click to collapse
so flashing with KG6 bootfile in KG7 resolves the problem of CSC pre configration.!!!?
I feel that KG7 is more unstable than KG6, it restarts often
hellseekar said:
so flashing with KG6 bootfile in KG7 resolves the problem of CSC pre configration.!!!?
Click to expand...
Click to collapse
To clarify
NOTHING resolves the CSC pre config issue
A new version will most likely fix this but currently nothing fixes it.
Yes you can, you have to activate region code by default with trix but it only works for the code you activate
Hello,
I can't turn on my phone.
"Samsung Wave" text appears, then bada animation shows up and the phone restarts.
I've tried to install different firmware versions via Bootloader (JID, JK3, KL6) and it didn't help.
Maybe somebody has an idea how to fix it, but I have one more question.
Is it possible to change Product Code only with access to Download Mode?
I mean by PSAS/RevSkill or any other tool without enabling Diagnostic Mode in service menu?
I need to fix my phone or change Product Code and then just send it for warranty.
Thank you.
As we not know, what you made before...
1.
You have not more access easily to filesystem to change Product Code for instance...
2.
You can try to see which problem your S8500 has.
Flash MID RC2 file. Then you could see Bluescreen, with additional Infos about Restart...
I need to fix my phone or change Product Code and then just send it for warranty.
Click to expand...
Click to collapse
If other problem like hardware...
Product Code is NO problem... nobody will punish you for wrong Product Code...
Best Regards
adfree said:
As we not know, what you made before...
Click to expand...
Click to collapse
I did nothing. I just turned off the phone and I can't turn it on again...
adfree said:
2.
You can try to see which problem your S8500 has.
Flash MID RC2 file. Then you could see Bluescreen, with additional Infos about Restart...
Click to expand...
Click to collapse
Here are photos of bluescreen:
Original branded firmware (bada 1.0):
i.imgur.com/GBiS4.jpg
i.imgur.com/RCRMq.jpg
KJ1 firmware (bada 2.0):
i.imgur.com/PcLHQ.jpg
i.imgur.com/DFRMy.jpg
These infos means nothing to me so thank you for your help.
Here are photos of bluescreen:
Click to expand...
Click to collapse
Thank you.
I did nothing. I just turned off the phone and I can't turn it on again...
Click to expand...
Click to collapse
Problem seems in starting CP... this is the second Qualcomm processor...
ideas.
1.
Check if amss.bin and dbl.mbn will be flashed WITHOUT Errors...
2.
Maybe NV items erased...
Product Code is also stored as NV item...
This would be bad. As no idea how to check/restore without full access to handset...
3.
Hardware damage... something is not more alive...
I need to fix my phone or change Product Code and then just send it for warranty.
Click to expand...
Click to collapse
I think you should try service... for repair.
I think its NOT your fault. If you not play to much with some Unlock techniques or JTAG... Hardware experiments.
Never seen this before... if Multiloader can't fix this. Then handset itself has bigger problems.
Best Regards
Fixed, please remove.
Hi everyone,
Have just purchased a new Galaxy Y here in China and restored to original factory settings however everything is in Chinese which isn't a problem as I can change the language to English however all the default Google Apps are missing and replaced with Chinese equivalents it seems so I'm unable to use them.
So... how can I restore it to a version of Android something functional for me? I'm on mac os x lion with vmware for any windows apps I need and am computer literate enough to attempt anything like flashing a device / updating a rom but have no idea where to start with this. Have read some docs on Odin but they made little sense at first because I don't quite know what steps I need to take in order to carry out this task. I've found various Roms but these are India, Netherlands, Greece versions, does anyone know of a UK version?
Any pointers would help greatly, thanks in advance!
Update: Just came across http://forum.xda-developers.com/showthread.php?t=1465800 so am reading through here however I'm not sure which ROM to go for, the European pack work with sim cards in Asia?
Rich
first thing that the initial setup offers after full reset, is to change the language. It's the button on the the right hand side of the screen. if you press the green android, it's too late. then you must navigate to language setup by memory.
mai77 said:
first thing that the initial setup offers after full reset, is to change the language. It's the button on the the right hand side of the screen. if you press the green android, it's too late. then you must navigate to language setup by memory.
Click to expand...
Click to collapse
I've changed the language but it's a custom Chinese rom as China bans everything google so I need to get it on a normal UK Android setup or something, maybe the European pack from the aforementioned link?
Current versions as follows:
PDA: S5360ZCKK2
PHONE: S5360ZCKK2
CSC: S5360ZHKK2
richd86 said:
I've changed the language but it's a custom Chinese rom as China bans everything google so I need to get it on a normal UK Android setup or something, maybe the European pack from the aforementioned link?
Current versions as follows:
PDA: S5360ZCKK2
PHONE: S5360ZCKK2
CSC: S5360ZHKK2
Click to expand...
Click to collapse
Try and check Docky stock Rom under android development. He has european firmware. Flash it via Odin. There are guide how to flash via Odin in his thread if im not mistaken. Hope it helps.
Sent from my GT-S5360 using XDA App
axilefoo said:
Try and check Docky stock Rom under android development. He has european firmware. Flash it via Odin. There are guide how to flash via Odin in his thread if im not mistaken. Hope it helps.
Sent from my GT-S5360 using XDA App
Click to expand...
Click to collapse
Thank you for this, am just looking at Docky's stock roms now. Seems like the phone isn't locked to any specific network as accepts both Hong Kong and UK sim cards at the moment. I'm a little confused about setting the CSC and provider/region stuff after flashing it, basically I'm in Asia for the next 10 months and will have various sim cards from different countries and want them all to work. Possible do you think? Or will I have to flash to country specific firmware/csc relative to the sim card I'm inserting?
richd86 said:
Thank you for this, am just looking at Docky's stock roms now. Seems like the phone isn't locked to any specific network as accepts both Hong Kong and UK sim cards at the moment. I'm a little confused about setting the CSC and provider/region stuff after flashing it, basically I'm in Asia for the next 10 months and will have various sim cards from different countries and want them all to work. Possible do you think? Or will I have to flash to country specific firmware/csc relative to the sim card I'm inserting?
Click to expand...
Click to collapse
Well, Im in Asia country too. I tried Docky's Custom ROM which is based on XX which is European firmware and my phone works together with the SIM provider and network. So, the CSC is basically the language supported by your phone (based on my experience). Thus, Im sure you can use European firmware when you are in Asia country
axilefoo said:
Well, Im in Asia country too. I tried Docky's Custom ROM which is based on XX which is European firmware and my phone works together with the SIM provider and network. So, the CSC is basically the language supported by your phone (based on my experience). Thus, Im sure you can use European firmware when you are in Asia country
Click to expand...
Click to collapse
Small world hehe I'm currently downloading S5360_XXLA2_OXXLA2_XXLA2_by_Doky.zip which seems to be the latest european multilingual build so hopefully that will do the trick. I'll let you know how I get on, thanks for the tips.
richd86 said:
Small world hehe I'm currently downloading S5360_XXLA2_OXXLA2_XXLA2_by_Doky.zip which seems to be the latest european multilingual build so hopefully that will do the trick. I'll let you know how I get on, thanks for the tips.
Click to expand...
Click to collapse
Cool. Cant wait to hear from you soon. Good luck
I think the simpliest way to solve this is to update its firmware via samsung kies, besides its the official update you can get and you'll be sure it'll be safe. Ive updated mine through this method and havent tried the ODIN thing. Good luck though
axilefoo said:
Cool. Cant wait to hear from you soon. Good luck
Click to expand...
Click to collapse
Woo hoooo I have a working phone, or should I say a phone which I can understand. It took a while because I couldn't find a decent internet connection where I was but having found one the process, following Doky's instructions, was painless - what a result! Thanks for your help!
richd86 said:
Woo hoooo I have a working phone, or should I say a phone which I can understand. It took a while because I couldn't find a decent internet connection where I was but having found one the process, following Doky's instructions, was painless - what a result! Thanks for your help!
Click to expand...
Click to collapse
No problem! Enjoy
Asian driver for Galaxy Young ?
richd86 said:
Woo hoooo I have a working phone, or should I say a phone which I can understand....
Click to expand...
Click to collapse
Hi,
I really appreciate all the posting which is done on this site, and it has helped me many times (as I often act as the 'family' technician who can fix things).
But this time, I inherited a bricked Vietnamese Galaxy Young. The issue I have is that event though I installed ODIN in its most recent release, the phone in DOWNLOAD mode is not recognized on the 2 computers I usually use on other Samsung phones.
Is there an Asian-specific driver which needs to be used?
Alas, the phone was backed up using the CWM backup, but it refuses to boot into CWM (just hangs at logo). The only mode it boots into is Downlaod mode. But it need to be recognized correctly before Odin can do anything
Thanks for suggestions
Marc, from France
mwrmwr said:
Hi,
I really appreciate all the posting which is done on this site, and it has helped me many times (as I often act as the 'family' technician who can fix things).
But this time, I inherited a bricked Vietnamese Galaxy Young. The issue I have is that event though I installed ODIN in its most recent release, the phone in DOWNLOAD mode is not recognized on the 2 computers I usually use on other Samsung phones.
Is there an Asian-specific driver which needs to be used?
Alas, the phone was backed up using the CWM backup, but it refuses to boot into CWM (just hangs at logo). The only mode it boots into is Downlaod mode. But it need to be recognized correctly before Odin can do anything
Thanks for suggestions
Marc, from France
Click to expand...
Click to collapse
make sure samsung usb drivers are installed - use rear usb ports not front ones and you can try a different usb cable (there is no specific regional driver just a generic samsung usb driver)
once in download mode connect usb cable to pc
push vol up on phone to start connection (wait a 30 secs in case drivers start installing)
open odin 3.07
if it is connected it will say com then a number in a coloured box under com:id on the left hand side
Hi,
Can anyone help... I bricked my S20 Ultra SM-G9880 and tried using odin3 to flash firmware but it is asking for the Super Image so fails the process.
It say on screen; An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software but when I download this it says the S20 is not compatible.
Please can anyone help it was a lot of money?
[email protected] said:
Hi,
Can anyone help... I bricked my S20 Ultra SM-G9880 and tried using odin3 to flash firmware but it is asking for the Super Image so fails the process.
It say on screen; An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software but when I download this it says the S20 is not compatible.
Please can anyone help it was a lot of money?
Click to expand...
Click to collapse
first off, what did you do to brick an expensive phone? Is it because you can't wait for the update to come along that you tried switching different Firmware without back reading some threads beforehand?? i'm not here to offend you or belittle you, in fact we have the same device and variant, HK- SM-G9880 to be precise.
mimsiroll said:
first off, what did you do to brick an expensive phone? Is it because you can't wait for the update to come along that you tried switching different Firmware without back reading some threads beforehand?? i'm not here to offend you or belittle you, in fact we have the same device and variant, HK- SM-G9880 to be precise.
Click to expand...
Click to collapse
I was trying to change rom to HK instead of Taiwan because I thought it might get rid of the chinese writing and be more western friendly... Wasn't really thinking... it was an expensive mistake.
Is there away to fix?
[email protected] said:
I was trying to change rom to HK instead of Taiwan because I thought it might get rid of the chinese writing and be more western friendly... Wasn't really thinking... it was an expensive mistake.
Is there away to fix?
Click to expand...
Click to collapse
You probably have to read this topic about samkey so just dig this thread and read about the samkey. How it can fix your phone depends on what youll choose otherwise i can still suggest using samsung switch from pc and do an emergency installation but as always find a topic about it first and do the most suitable thing for you.
https://forum.xda-developers.com/galaxy-s20/how-to/free-csc-change-apk-s20-t4116015
really? lol
hes not brick bricked.. that screen is an odin download mode screen.. he can simple use odin to reflash stock firmware to the device lol
elliwigy said:
really? lol
hes not brick bricked.. that screen is an odin download mode screen.. he can simple use odin to reflash stock firmware to the device lol
Click to expand...
Click to collapse
Hi thanks for comment... I flashed odin but it didn't remove lock. Maybe because it is a modern phone? I have given it to a local phone repair shop so hopefully they will fix for me.
[email protected] said:
Hi thanks for comment... I flashed odin but it didn't remove lock. Maybe because it is a modern phone? I have given it to a local phone repair shop so hopefully they will fix for me.
Click to expand...
Click to collapse
dunno wat lock u mean
Hi Folks,
I posted this thread and just wanted to thank everyone who offered advice. I have managed to fix the phone now.
I flashed latest firmware with Odin and included .PIT file i extract from the CSC file.
So pleased to have it back!
Many thanks to @[email protected], this method worked as a charm.