Related
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
obones said:
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
Click to expand...
Click to collapse
Not sure if you do or not but do you need to have Htc Sync installed for the drivers?
I do have HTC Sync installed
Are you rooted? You need root to do this. If you are then why not use fake flash or unrevoked to enter recovery.
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
obones said:
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
Click to expand...
Click to collapse
Recovery-windows.bat won't work unless you are rooted. The screen with the red triangle isn't actually recovery mode. The .bat file you would run pushes the recovery to the phone.
If you are not going to root, then you can get an app from the market that puts your phone on silent as you switch it off, and then back to normal when it's booted. This disables the boot sound. It's called silent boot I think.
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
obones said:
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
Click to expand...
Click to collapse
try fake flash? ive never used it so i duno if u need to be rooted
Fake flash needs root. No custom recovery will work without root. Quite simply, if you are not rooted you will not have write access to /system
please help.
i try to install froyo rom.
after flash FroYo_inkreDroid (14.07.2010) rom (throught standart flashrom procedures by update.zip) the device will not boot into os. i try update modem and after this the device win not booting to recovery mode.
i try press both combination (back key + power and volume down + power). the result of both combination is: 7 short vibro signals and black screen.
please help me, how me recovery my device.
thnx and sorry for my english.
your going to have to root it.
Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App
I get a force close every time I try to put the camera in sport mode. I did search for threads dealing with this problem and found some. The problem is that I don't understand most of the terminology. Would someone be nice enough to give me step by step instructions on how to fix this. It is really aggravating.
Its basically a good example of poor coding by Samsung.
along the lines of adding a new line of code in the middle of the old causing everything to shift up or down..
The fix(s)
You need to be rooted.
flash one of the roms that have the fix included(read the details for your selected rom)
or..
use the original fix (don't need to be rooted for this one)
http://forum.xda-developers.com/showthread.php?t=970452
you would download the file, and flash it with odin. for the original.
pretty simple really.
All the roms have instructions on first page as does the "fix"
Since you are having problems with terminology ill walk the odin method
make sure you have the Samsung drivers installed
http://forum.xda-developers.com/showthread.php?t=728929
download the camera fix . its a .tar file
download odin
extract odin
put your phone into download mode.
you do this by (from an off state) holding 1 on your physical keyboard and the power button at the same time.
open odin (click the "odin 3+v1.6.exe icon in the folder you extracted to)
connect your usb (you should see one of the com squares light up" mine is always on com 4")
click on "pda button" browse and set the camera fix .tar there
unclick where it says F.reset time
click start
let it run
your done
I am not the best at explanations. But i would like to see you get this fixed
I attached a zip of odin and the camera fix .tar for simplicity
Did it understand what tmspyder was telling you? If you did give him a thanks
Sent From My Evo Killer!
tmspyder said:
Its basically a good example of poor coding by Samsung.
along the lines of adding a new line of code in the middle of the old causing everything to shift up or down..
The fix(s)
You need to be rooted.
flash one of the roms that have the fix included(read the details for your selected rom)
or..
use the original fix (don't need to be rooted for this one)
http://forum.xda-developers.com/showthread.php?t=970452
you would download the file, and flash it with odin. for the original.
pretty simple really.
All the roms have instructions on first page as does the "fix"
Since you are having problems with terminology ill walk the odin method
make sure you have the Samsung drivers installed
http://forum.xda-developers.com/showthread.php?t=728929
download the camera fix . its a .tar file
download odin
extract odin
put your phone into download mode.
you do this by (from an off state) holding 1 on your physical keyboard and the power button at the same time.
open odin (click the "odin 3+v1.6.exe icon in the folder you extracted to)
connect your usb (you should see one of the com squares light up" mine is always on com 4")
click on "pda button" browse and set the camera fix .tar there
unclick where it says F.reset time
click start
let it run
your done
I am not the best at explanations. But i would like to see you get this fixed
I attached a zip of odin and the camera fix .tar for simplicity
Click to expand...
Click to collapse
musclehead84 said:
Did it understand what tmspyder was telling you? If you did give him a thanks
Sent From My Evo Killer!
Click to expand...
Click to collapse
Thanks for the info Tmspyder. I just got off a 12 hour shift and am exhausted. I think I got the gist of it but am going to get some sleep first, read it again, and then reread what you posted. I just want to be sure of what I'm doing so I don't turn my phone into a "brick".
you wont brick. one of the great things about the epic and odin.. it is a 1/1,000,000 shot at real damage
Ok, I followed the directions, but the phone did not reboot automatically. It still says downloading... What should I do?
NVM, pulled the battery, put it back into download mode, repeated the process and it worked fine. No clue why it didn't work the first time.
This morning, before even started with rooting, my brand new Galaxy Tab 3 10.1 (GT-P5210) went into the Odin Download modus without any problem.
But, the Odin software isn't able to even see the Tab 3 itself. Just the Odin screen and nothing else.
I have tried to reset or power down the device, with all possible keys and key combinations. But no luck so far.
Does anyone else have a suggestion ?
is128ae said:
This morning, before even started with rooting, my brand new Galaxy Tab 3 10.1 (GT-P5210) went into the Odin Download modus without any problem.
But, the Odin software isn't able to even see the Tab 3 itself. Just the Odin screen and nothing else.
I have tried to reset or power down the device, with all possible keys and key combinations. But no luck so far.
Does anyone else have a suggestion ?
Click to expand...
Click to collapse
To manually exit Download mode, you have to hold the Power button for at least 10 seconds (or more). It should then reboot normally if you haven't changed anything.
To get your PC to recognize your Tab, you need to download and install the Samsung USB drivers (or just install KIES). Also go ahead and make sure USB debugging is turned on in Developer settings (to make troubleshooting easier in the future if necessary).
gr8nole said:
To manually exit Download mode, you have to hold the Power button for at least 10 seconds (or more). It should then reboot normally if you haven't changed anything.
To get your PC to recognize your Tab, you need to download and install the Samsung USB drivers (or just install KIES). Also go ahead and make sure USB debugging is turned on in Developer settings (to make troubleshooting easier in the future if necessary).
Click to expand...
Click to collapse
Thanks for your relply. Problem is, I can hold down the power button until my hand falls off.
It won't power down
..... After 8 hours the tablet went down, because of an empty battery.....
Now waiting for it to have power enough stored to boot again....
HELP! i have same problem.
is128ae said:
..... After 8 hours the tablet went down, because of an empty battery.....
Now waiting for it to have power enough stored to boot again....
Click to expand...
Click to collapse
Did it boot up again normally after you recharged? Is it all normal now? Im really worried please reply.
:crying:
FSN8iN said:
Did it boot up again normally after you recharged? Is it all normal now? Im really worried please reply.
:crying:
Click to expand...
Click to collapse
Yes it booted up without a problem.
It only took a time (long! > 8hrs !) for the battery to be fully charged.
I have the same issue, TAB3 10-1.
I entered Odin Download Mode and the device wont switch down when power button pressed. I disconnected the cable and the screen still remains.
So I have to wait hours and hours till the tablet will discharge.
By the way that file pre-rooted md5 did not download at all and I have to download manually - 30kbit/sec is hell of a speed = aprox 16 hours and errors during download are very likely, phew.
PS - jailbreaking iPhone is far more easy
Yep, the tab 3 GT-5210 with x86 processor wont reboot from odin mode. Ive tried the suggestions here and elsewhere and agree with the others in this thread. Ive held down the power button for minutes by hand, and now it has been about 20 mins and counting with tape holding it down. Odin 3.09 can see the device and talk to it, but it wont reboot it without a flash. Ive seen suggestions elsewhere that flashing a blank file will work around the issue and cause the auto reboot to happen, but it does not. Odin fails to load the file, then does nothing and does not auto reboot. When I disconnected the tab from the pc after playing with odin, the battery part of the tab was warm so it had been charging off the pc Ive been searching quite a while, it seems the only way to get out of odin mode is to wait for it to go flat as discussed here.
---------- Post added at 10:54 AM ---------- Previous post was at 10:29 AM ----------
Ok, I created a way to do this.
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS! :good:
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.
And when you did this were you able to install a new recovery w/o the old one being reinstalled?
Sorry, wrong message
antus said:
Yep, the tab 3 GT-5210 with x86 processor wont reboot from odin mode. Ive tried the suggestions here and elsewhere and agree with the others in this thread. Ive held down the power button for minutes by hand, and now it has been about 20 mins and counting with tape holding it down. Odin 3.09 can see the device and talk to it, but it wont reboot it without a flash. Ive seen suggestions elsewhere that flashing a blank file will work around the issue and cause the auto reboot to happen, but it does not. Odin fails to load the file, then does nothing and does not auto reboot. When I disconnected the tab from the pc after playing with odin, the battery part of the tab was warm so it had been charging off the pc Ive been searching quite a while, it seems the only way to get out of odin mode is to wait for it to go flat as discussed here.
---------- Post added at 10:54 AM ---------- Previous post was at 10:29 AM ----------
Ok, I created a way to do this.
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS! :good:
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.
Click to expand...
Click to collapse
you're the man! Thank you!
could some one explain it in detail
Firstly you need odin 3.09. My version contains "Odin3 v3.09.exe" which is 2290688 bytes with an MD5 sum of 46947de16219dcbec41c8290353ad50c
Open the exe in your favorite hex editor and at offset 712A change 75 to EB. This disables the "no bin file is selected" error message, so you can do nothing and cause the reboot.
This screen shot was taken after the reboot. Configure the app like this and click start. It'll do nothing, reboot, and say PASS!
due to being < 10 posts I cant post this link. But you can resassemble it. Mods, if you want to verify this link and fix my post, go ahead.
http: // i.imgur.com / X41Cq3s.png
If your not confident with odin and dont want to risk your tablet, your better of waiting for the battery to go flat. But if you understand the risks and what ive done here, maybe it'll save you the wait.
Click to expand...
Click to collapse
nevermind I fixed it already
[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
This was originally posted in the I337M forum as that's what I have, but here you go!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here