Hello, I am having wifi problems after flashing any file to my phone. After phone reboots when you try and click on the wifi button it stays inactive. I was wondering if anyone else has had his same problem and has been able to fix it??
Note 2
Rooted Stock Touchwiz 4.3
CWM Recovery
Have you tried the wifi fix?
http://d-h.st/6qX
Flash via Odin
I've been seeing these patches for 4.3 everywhere. Any chance they work with kitkat as well? I have my phone setup exactly the way I like and don't wanna flash and regret right this moment.
Sent from my SPH-L900 using Tapatalk
i flashed the fix via odin..and it worked until I rebooted my phone....at which point wifi wouldnt even turn on
Odin flash of Wifi Fix still fails after many attempts!?!?!
I'm loving 4.3, but I really miss WiFi!!
I went from long time use of Mack's All Star rom to STS MK4 v1.1
I followed the steps on that thread: http://forum.xda-developers.com/showthread.php?t=2121063
and also Lorjay's thread that it referenced: http://forum.xda-developers.com/showthread.php?t=2541395
I followed these steps:
1) I backed up my device on TWRP
2) Wiped cache, dalvic cache and system (I didn't do a factory reset at this point--probably should have but didn't realize)
3) Flashed the following files in order in one action in TWRP:
a) STS_MK4_v1.1_ODEXED.zip
b) MK4 Modem.zip
c) STS_v1.1_Add_On_SprintAndroidExtension.zip
d) STS_MK4_SystemUI_Morph_v1.zip
4) I rebooted the phone through TWRP
5) Once the phone booted up fully, I shut it down so I could do an Odin Flash
6) I started up Odin3 v1.85
7) I started my phone in Odin Download mode
8) I connected my phone to the USB cord and Odin said <ID:0/005> Added!! The ID:COM lit up Yellow and said 0:[COM5]
9) I clicked the PDA button and selected patch.tar.md5
10) I hit Start button and it gave me a big red FAIL!
The message box said the patch.tar.md5 is valid
It said Get PIT for mapping... Firmware update start.. tz.img NAND Write Start!! blank line Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
11) I had F.Reset Time and Auto Reboot checked and nothing else (according to the instructions I read)
12) At this point the phone appears to still be in Download mode, but if I restart Odin it will not recognize the phone unless I reboot it into Download again.
I have tried a different version of Odin (3.09), different computers, different USB ports, different USB cords, downloaded the patch file from different websites. I extracted it using WinRar. I downloaded Kies and installed new drivers.
So far nothing changes the basic result. I have read many posts and websites about using Odin. The only thing sticks out is that some talk about something turning blue when the phone is plugged into the USB and I have never seen anything blue, only yellow in 1.85 and light green in 3.09. I also have USB debugging set in the Developer Options
Perhaps it is still something driver related, but the drivers appear to be working for everything else.
The phone seems to be working great except for wifi, which is a big deal. I imagine the wifi fix will do the trick; but there seems to be some communications problem between Odin and the phone.
I'm open to reconsidering anything and everything, but the only solution offered to others with this problem so far is "use a different computer" and I've already done that and much more.
Any help would be much appreciated. I don't really want to go back to 4.whatever I had before.
Related
DOWNGRADE BEFORE I COULD UPGRADE
I had to jump through a lot of hoops to help a friend upgrade their Samsung Continuum (on Verizon) to the new Froyo 2.2.2 (EC09). I had previously rooted the phone, which was still on DL17, and that was now crashing the official upgrade. So I thought I'd document what finally worked, for anyone else who's struggling with the same. Not guaranteeing my procedure will work, of course.
Mostly, I've summarized and rewritten the other instructions I found buried in and amongst the other discussion threads. After successfully restoring 'stock' the official Froyo upgrade finally worked.
PRE-REQUISITES
- locate the thread, [DEV] Continuum DataBase [EC09][DL17][EC03][EC07]
- download the following files:
Samsung i400 USB driver
"DL17 Factory stock rom+radio+kernel (odex) all in one odin flash"
(the resulting unzipped file is 'Continuum-Stock-DL17.tar.md5')
ODIN flash-tool
- download the updated "EC07" PIT file (the "DL17" PIT didn't work for me!)
Samsung_I500_VZW_PIT.PIT
PROCEDURE
Install the Samsung i400 USB drivers
Remove battery from phone (not sure if this is necessary but some threads advised it, and after several failed attempts I was desperately trying everything. In any case, it didn't interfere with a successful imaging!)
Connect the phone on USB
Hold VOL-DOWN plus PWR buttons until the built-in 'Flashing' screen appears (should be immediate)
Confirm that the computer detected the phone over USB
If not, re-run the Samsung USB Driver install and select 'Repair')
run ODIN
Confirm that there is a yellow 'COM' status showing in the top-left.
If not, ODIN isn't connected to the phone!
Click on 'PIT' button and select the 'Samsung_I500_VZW_PIT.PIT'
UNCHECK the checkbox option for 'Re-partition'
Click on 'PDA' button and select the 'Continuum-Stock-DL17.tar.md5' file
Click START
You should see a steady stream of status updates in the bottom-left window as well as a progress bar in the top-left (labeled "factoryfs")
The update should take about 10 minutes, then the phone will reboot. The reboot takes about 2 minutes and there is nothing shown on the phone!
NOTES
I originally tried using the (DL17) 'SCH-i4000-VZW-Continuum.pit' but it didn't work.
I also tried it both with and without the re-partition option; neither worked
At one point the phone stopped being recognized on USB. I simply re-ran the Samsung USB Driver install and selected 'Repair'. Then the phone was recognized again.
Hello forums,
I just got the hint I posted my question in the wrong forum. Here again the relevant information:
I pulled my note 2 out of my pocket and there was this "Samsung Galaxy Note II - N7105" logo showing. Since then I tried to reboot the phone but nothing helps.
Then I somewhere read something about "safe boot mode" (volume down + power). Since I tried this the screen gets completely scrambled black and white (like old television with no signal).
I tried several things since yesterday. I am able to get into download mode (vol down + home + power). With odin first I tried to flash the original rom.
The error is "There is no PIT partition". Then I tried to flash the cf-autoroot kernel - no success.
Then I tried to get a communication with the device by using adb console - no success. The device doesn't show up in connected devices list.
Since odin reports a missing (read: corrupted) PIT partition, I need the correct PIT-file for my official rom, right?
This is the ROM i've dl'ed from sammobile: N7105XXDMB2_N7105DTMDMA1_DTM
It _should_ be the version that actually was on my phone. Now I need the correct PIT file for that rom. Any idea where I can get that?
Leo
You can try the pitfile in this thread:
http://forum.xda-developers.com/showthread.php?p=37688128
it seems I don't have any luck. odin hangs at <ID:0/005> SetupConnection..
I think i'll save my time and get a replacement...
I don't want to be a pessimist but it looks like you have SDS (Sudden Death Syndrome)
I don't think that's too pesimistic - just realistic
Have requested an RMA
Hello XDA!
So, idiot that I am, I decided today would be a great time to root my Galaxy S III (SGH-T999N version). It was running Jellybean 4.3, so it had fewer root options than other, older Jellybean versions, but I still found a root file on here. I put it into USB debugging mode, downloaded the driver, Odin, and the root file. I also backed the phone up on Kies, and have that on my PC., I did everything right, and... it failed. I tried again without doing anything to the phone (read: kept it in download mode), but it failed again with a different root file. So, I turned it off, sad that I wasn't able to root it, and I came upon the dreaded 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' screen.
After hours of searching, I saw two different solutions: downloading the 4.3 OS from online, and using Odin to flash that to the phone, or using Kies to reformat the phone. I've been trying Kies, but Kies 3 isn't recognizing the phone, and won't allow me to restore or to reformat the phone. I'm still waiting on the download of Jellybean 4.3 to finish so that I can try that (Odin HAS been recognizing the phone). While I wait, I wanted to know if other users have had similar problems that they've solved, or where I've gone wrong, and what I can fix.
As for additional details:
- I CAN put the phone into Download mode. I CANNOT do a factory reset through Vol. Up+Home+Power
- The status screen with 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' also has this information at the top:
ODIN MODE
PRODUCT NAME: SGH-T999N
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWAREV: 1
- The phone is carried by Metro-PCS
Thanks in advance!
Okay, turns out the downloaded Jellybean 4.3 OS did the trick. For future people who run into this issue:
1. Have Odin 3.07 or higher downloaded (Odds are that you have this due to your phone's current state).
2. Download a copy of the OS you want from here: samsung-updates.com/device/?id=SCH-I535 Go to the dropdown menu on the left-hand side, and select your phone. Don't know/remeber your phone's identifier? Open up the back, remove the battery, and there should be a white sticker with your phone's model at the top. WARNING! Unless you plan to pay, these downloads will take a while. Do this when you can have your computer on for 4+ hours.
3. Once the download is complete, unzip the file, and place it in a location that you can easily find with Odin.
4. Open Odin, and make sure that Auto Reboot and F. Reset time are the only options checked. If there are other options selected, uncheck them and proceed.
5. Click the "PDA" button, and select your copy of the Android OS from where it was stored. Assuming everything has gone correctly, a message should appear in the Odin status box along the lines of "Check MD5... Do not unplug the cable...". Wait for the message "Leave CS..." to appear before proceeding.
6. Once "Leave CS..." has appeared, put your phone into Download mode (Turn it off, then restart by holding down the Vol. Down, Home, and Power keys until you get a screen that has informed you that you are in download mode.). Then, plug your usb cable into your PC/Laptop, and then into the USB outlet on the phone.
7. Once Odin has noted that your phone is attached, you can press "Start", and assuming all steps have been followed correctly, the new OS should download, and your phone will reboot, fully functional. If you are lucky like me, it will even have kept all of your settings!
Hello 2 days ago my smartphone (n7100 @phantom_V13_N7100XXUFNI2_XEO with agni kernel) restarted many times for no reasons.
I went to Touch recovery and wiped cache , did not help at all.
Later my phone just restarted and couldn't work, stuck at samsung n7100 logo so i thought i have to flash it with odin.
I've pulled my laptop from old desk - because it has Xp installed, I installed all samsung usb drivers, odin and tried to flash some stock roms i've always recivd NAND WRITE START FAIL
so i borrowed from my friend USB cable from S3.
I downloaded from samfirmwares N7100XXUFNI2_N7100XEOFNI1_XEO so the latest for Poland, added package (md.5) at Ap option via odin 3.09 and it flashed but while selecting country and other options it restarted.
And here i'm stuck at Samsung Galaxy Note ][ Gt-n7100 all over again... I tried going into recovery (now i have stock recovery) wipe data/cache and pull of battery, next i puted battery in download mode and again odin 3.09 md.5 file N7100XXUFNI2_N7100XEOFNI1_XEO at Ap and problem goes again. Now it doesn't even go into android configuration just bootlop
And ideas?
If anyone is intrested i fixed it by myself! All thanks to xda, google and my friends USB cable.
For endless problems with nand write fail i used friends cable from his S3 and laptop with clean Xp sp3 + samsung usb drivers
Main reason for whole problem was... battery ! It has 4.05 V instead of 4.35 V so after i flash system via odin and unplug it from cable it destroys the "android setup files"
If You're not sure if its battery or not try this one.
1. Install usb drivers
2. Install odin ( 3.09 worked for me )
3. download firmware ( 4.4 XEO (Poland version ) worked for me.
4. go into phone twrp/normal recovery and wipe cache, data like u always do
5. put downloaded package in AP section, UNCHECK auto restart in options
6. plug phone & start flashing
7. after odin is finished, unplug the phone connect it to charger and restart it.
8. keep Yours finger crossed
9. voi'la system is working
10. buy yourself a nice original battery
I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!
Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!
The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.
Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!
I had similar problem. What I did is just change the USB cable to new.