Hi,
I'm fully aware of how silly it is to be in this situation. I opened a thread thinking it was in the T-Mobile S3 forum and flashed the downloaded ROM. But regardless, I made an unfortunate mistake.
The ROM was Stockdroid 4.4.2 from the i9300 forum on this site. My phone is a T999v S3. Before beginning any flashing, I rooted and ran Odin to install Philz Touch 6 recovery and "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5". I was bouncing around firmwares looking for something that could fix the "Camera Failed" error (front camera works when charging but not anywhere else, any advice on that would be greatly appreciated), and I guess I lost track of exactly what I was downloading.
Anyway, after flashing the ROM the phone will not boot, and is almost completely unresponsive. The only life I can get out of it is when I connect it to the computer before taking the battery out, then putting it back in. A red light will shine at some point during that. In device manager the S3 is listed as QHSUSB_DLOAD. This leads me to think I can make use of one of the debricking tutorials on this site for the t999v.
The phone is a 16gb model, but I don't have a 16gb card. Before I go out and buy it, I want to know if buying it should solve the problem. I've read the debrick solution will not work with a 2gb card, but I tried anyway with no luck.
If it does work, great. If not, is my only other solution sending the device in for JTAG?
Thanks in advance for any and all help. I know this problem has been an impossible amount of times, but I wanted to pose the issue specifying the exact scenario I'm dealing with.
Yes the De-Brick thread under Developement will/should work. Make sure there is an image for your variant on that thread, before you buy the SD Card.
Once you successfully De-Brick, I will help with the Camera issue. Its pretty easy to fix in most cases.
Great, thank you!
I'll get back today on whether or not the method ends up working. The debrick image I've been using on my 4.4.2 T999v (on Windmobile) was from this thread:
http://forum.xda-developers.com/showthread.php?t=2439367
As for the Camera issue, should I start a new thread, or can I go ahead and post here?
That's correct thread for your Image. Just be sure you grab for T999V. There are other T-Mo variants too.
For the Camera, continue here when done De-Bricking.
Hi, I just got back and loaded the image on a 32GB microsd. The phone booted up just fine!
I followed the rest of the guide and attempted to reinstall the "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5" file using ODIN, but it failed during the process. What do I do from here? I would like to be able to use the phone without the 32gb card being taken up like this. Should I try installing a 4.3 ROM of some sort?
Edit: Tried it again and the flash was successful. Just about to install a recovery image, but assuming the install went well I'm guessing I am brick-free? Thank you for the help, Perseus71.
I'll update my post if I run into any other problems regarding the brick, but for now what should I be doing with the camera issue?
I've tinkered a bit with the camera firmware with no luck, and have flashed 4.3 stock again with no luck. What should I do to resolve this issue?
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Perseus71 said:
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Click to expand...
Click to collapse
Good to know, I'll refrain from using third party camera apps. And even after flashing the above firmware it says Camera Failed.
The problem started on stock 4.3 before any ROM installing/rooting occurred. I tried the obvious clearing app cache, factory reset and wiping dalvik cache, but no luck. Since then I've been installing different ROMs and Camera Firmwares (ZDFE02, ZDFI02, etc), and moving around and setting permissions for SlimISP bin files. I know the rear works when it's being charged, and that the front camera works just fine. I just don't know what I can do to get it working. I've read that replacing the camera itself may not even fix the problem.
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Perseus71 said:
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Click to expand...
Click to collapse
Alright. I flashed the 4.3 image mentioned above with Odin, no problems there. Before flashing I did a dalvik/cache wipe and Factory Reset. When finished, I booted to Stock Recovery, but there was only an option to wipe Cache. Instead I opted to both wipe Cache and do another Factory Reset.
Unfortunately I booted the phone up again, skipping the connect to Internet and Google options, and went directly for the Camera App. I still receive the Camera Failed error.
What should I do from here? Does this mean the Camera itself is faulty? And will replacing it actually solve the problem (or could it be a mainboard issue)?
Also the Camera Firmwares currently on are as follows:
Rear
Camera - ZDFE02
Phone - ZDFI02
Front
Camera & Phone - S5K6A3
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
For ROMs I would simply boot into a custom recovery and flash them, along with kernels, heeding any warning signs in threads. I wouldn't run into any errors, and could swap between 4.3 and 4.4.2 without issues. I didn't extensively test out the ROMs, but it seemed fine.
For Camera Firmware, on a StockMOD 4.3 ROM I dialed *#34971539# to get into the CameraFirmware menu. From there I could write new firmware depending on the SlimISP bin file transferred to the internal root. I can't remember thinking back if the Camera firmware actually changed when I did this, but the Phone firmware did (or maybe vice versa, I'll try again -- I know there was a change after writing).
So I do remember reading you can't downgrade lower than 4.3, that must be true then? If I could go down to ICS I could force the Camera Firmware to change?
What's the target Camera Firmware here? Does it need to be the same as the Phone Firmware (i.e. ZDFI02)?
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Could I use the ZDFI02 firmware from this thread?
http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
I'll find a way to get the Camera Firmware to ZDFI02 and get back to your both.
I going to guess that using that would be ok, but I cannot say for sure since it is for the I9300, which is a very different device from ours.
Sent from my SM-N900T using Tapatalk
Well, I loaded StockMOD 4.3 back on, and while it enables me to write Camera Firmware (no longer greyed out), the Camera Firmware will not change from ZDFE02 to ZDFI02. Do you have any suggestions as to what I can do to get around this? Will downgrading to ICS lead me to another brick?
It shouldn't brick. Can't think of any reason it would. Stability might be more of an issue though.
Sent from my SM-N900T using Tapatalk
Alright, I've loaded on a 4.0.4 ICS ROM. When I input the *#34971539# code, I get the error "Unfortunately factory test has stopped."
Now that an ICS ROM has been loaded, what is the method for flashing the ZDFI02 firmware to CAM?
It was using the dialer code. I guess that since it's an ICS app trying to make changes to your 4.3 firmware it's running into compatibility issues. It sounds like you are doing it correctly, just the versions must be too far apart....apologies for putting you through the hassle of doing all that. It was the best thing I could think to try though. If I think of any other ideas I will certainly let you know. There might be a way to load it using terminal emulator, but I've no idea how you would go about that.
Only other thing would be to try and edit the code of the Factory Test app on 4.3 to enable the Phone to Cam F/W Write option. I had looked into it briefly back on 4.1.2, but Im too much of a novice when it comes to java. I'd still love to know if it's even possible though. We were able to enable JB camera features before the official release by doing the F/W write, so you never know when that could happen again!
Sent from my SM-N900T using Tapatalk
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
It's another sort of shot in the dark, but you could try replacing the camera module. Find a YouTube video showing the S3 disassembly, it really not that difficult, and you can find the camera module online fairly cheap.
Sent from my SM-N900T using Tapatalk
t999
hi friends
my s3 sgh-T999 is bricked:crying:
i can access downloading mode but when i try to put phone in recovery mode phone just show robot logo for a second then restart
i tried every solutions(flash recovery,flash stock or any other roms and ...) here but nothing changed
sometime phone boot and some chines words appear with one button !!
*odin 307 detect phone
http://forum.xda-developers.com/attachment.php?attachmentid=2668840&stc=1&d=1396652278
thanks
If you can get in download mode and it is seen by odin, flash the latest firmware.
Sent from my SM-N900T using Tapatalk
Related
Hey guys,
I've been working on rooting the new Captivate Glide, and unfortunately my kernel flash with ODIN failed (inexplicably). Now the device is complaining I need to perform an emergency recovery, but of course the device isn't listed in the KIES panel.
Apologies if this is covered elsewhere, but I searched and didn't find anything.
Can anyone explain how KIES works? What is a recovery code? Do I need to get one from Samsung? Is there any other way to force it to perform the recovery on my semi-bricked phone?
Wrong forum ...
There isn't a forum for him yet, so this is the best he could do.
Try going to download mode and flashing again! Try again, until it works, redownload the kernel.
Sent from my SGH-I897 using xda premium
Actually, strangely enough ... I entered 3e recovery (out of desperation) and rebooted, and it cleared the flag, allowing it to boot up normally.
I checked the kernel timestamp (cat /proc/version) and it appears to still be the stock kernel, so the NAND update completely failed.
I still would like to figure out how to force a KIES recovery, but at least for the moment I'm back up and running (till I take my next shot ).
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
studacris said:
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
Click to expand...
Click to collapse
Frustrating. The n900 flashing tool was so excellent (and cross-platform). Wonder why Samsung would release such a piece of junk.
Anyway, I'm back in business now and still working on it.
I'd love to try one of the other kernels, but since I don't have any recovery path (stock kernel / image / firmware), I'm really nervous now.
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
So recently I had a Galaxy S3 whose charger port failed and I could no longer use the phone. So I had a replacement sent to me via my phone insurance company.
I stuck with TouchWiz for a few days since the phone was new, and everything worked just fine, camera, snapchat, chrome, you name it. I attempted to use the CMInstaller to remove Touchwiz and go to CM. However, during the installation process, everything appeared to be going smoothly, then the android with its chest open with the red triangle popped up briefly and the phone asked me to choose to root the phone. I hit yes, and the phone rebooted, at first with the CM logo, then it proceeded to boot into TouchWiz, with no sign of Cyanogen.
I did some research and found that this is because the replacement phone has Knox on it, preventing tampering. While I'm fine with TouchWiz for now until I can get a new phone in November, my phone has been acting a bit strange.
I can't download pictures from anywhere, whether its Chrome or Facebook or Twitter (where profile pictures won't even load). In Snapchat, I can only view pictures sent to me, but I can't view videos, I can't send pics or videos, and I can't load stories. Instagram closes when a video post pops up in my feed, but photos are fine. The Spider-Man game that I downloaded from the Play Store won't download the additional file that's needed to even start the game. My camera tells me to insert an SD card before using the camera, even though there is an SD card in the phone that I store music on for Poweramp (which works fine).
Other than these instances, the phone works fine. I'd just like to be able to use the apps I want. I did a factory reset from the settings menu to wipe stuff off the phone and see if that would get these apps to function correctly with no success.
Device info:
Model: SGH-I747
Android 4.4.2
Baseband: I747UCUFNE4
Kernel: 3.4.0-1514807
Build: KOT49H.I747UCUFNE4
I checked with Kies to see what it would do with the Firmware upgrade and initialization, since that was what the guide on here said to do. It's saying it will initialize my phone to 4.1.1 Baseband I747UCDDLK3, but downgrading will brick my phone, if I'm not mistaken.
So I don't know what to do now.
So my question is this: Can/Should I use Kies to attempt to restore my phone or did I permanently bork the hardware?
Try flashing the stock NE4 rom from enewman17s thread in development section. If im not mistaken it will have tge fix for external sd and the insecure kernel should solve the internal sd issues.
This is due to seLinux primarily, not knox. So its something we will have to deal with on every device running stock from now on. The alternative I believe is to format the card and factory reset. If you start everything fresh it should work ok when full stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
The problem I'm having with that idea is that I'm not sure I have root access, so I don't think I can flash a rom. If I can boot into recovery, I'll give it a try, but I'm not positive if it'll work.
Thanks for the tip!
You dont need to be rooted. Just need custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Try flashing the stock NE4 rom from enewman17s thread in development section. If im not mistaken it will have tge fix for external sd and the insecure kernel should solve the internal sd issues.
This is due to seLinux primarily, not knox. So its something we will have to deal with on every device running stock from now on. The alternative I believe is to format the card and factory reset. If you start everything fresh it should work ok when full stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi again,
I tried formatting and factory resetting. So I'm going to try the NE4 ROM, but I can't seem to find it. Would you mind pointing me in the right direction? Thanks for all your help!
This thread may help: http://forum.xda-developers.com/showthread.php?t=2789917
Okay, so I flashed that ROM from enewman's thread and it said it flashed successfully.
After it flashed, I went to do all three wipe options, and it rebooted in the middle of doing so. My phone rebooted normally into TouchWiz, and nothing was wiped and all my apps were still present.
I'm still having the same persistent problems as before. I think attempting another wipe may help, but I figured I'd check in with progress and see if anyone has any suggestions.
Thanks again.
Boot back into recovery and instead of factory resetting, choose Format /data.
This will wipe your internal sd card, just so you know. If that doesn't help, go back to the thread audit13 linked, reflash the rom, then the stock recovery. Reboot recovery and factory reset again. Then reboot and test. Pretty sure choosing format /data will be enough though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
To anyone more of an expert than myself on these matters (which I presume to be a large portion of users here), I'd greatly appreciate any help that can be provided. I'd also like for this thread to be a central collection of baseband/modem functions, behaviors, troubleshooting, etc...
I've had a T-Mobile S4 (SGH-M919) for a while now and have mostly used CyanogenMod derived ROM's and as of lately, more Google Play Edition/Nexus type ROM's (which generally appear to be written for the international i9505 and hence show the model number of my phone to be such; this may or may not be relevant). All of the sudden, the other day during a phone call I received, there was no audio on either end of the call. I couldn't hear the caller nor could the caller hear me. This also happens if I initiate the call. I know for a fact that the media speakers (speakers used during speakerphone) as well as the earpiece speaker are perfectly functional so it's not a case of hardware failure where it works on Bluetooth or speakerphone only. As soon as a call initiates, you hear no ringing or audio once the caller answers other than the tone when the call ends/disconnects. First thing I tried was switching from ART back to Dalvik just for the sake of troubleshooting. Second, I tried clearing the cache (and Dalvik, just for the hell of it). Still no success. So next I try a completely different ROM. I was presently on a GPE ROM with the Samsung kernel so I switched to plain CyanogenMod with a custom kernel. I even went back to a stock ROM! No success either way!!
It was at this point I decided that it had to be a hardware/firmware issue since the issue remained when changing ROM's so I naturally assumed baseband/modem. I don't understand why this issue just magically occurred one day when I hadn't changed anything, but I thought that if I reflashed a clean modem image or and updated one, then maybe it would fix it... I was on MDL so I reflashed the MDL modem. No success. Then (and here's where I f****d up), I tried flashing what I THOUGHT was a stock NB4 firmware file in ODIN. Turns out that despite being labeled as stock, it had a custom kernel built-in and tripped my KNOX counter (FFFFFUUUUUUCCCCCKKKK!!!) Well, since I really only intend to use AOSP/CM based ROM's, it's not such a huge deal for me but still, it sucks.
Here's where I had a break: Yesterday, I tried flashing the MDL modem again, then that didn't work so I tried flashing the MK2 modem. I booted up, made a call, and it worked! First time! Well, that was short lived success because I tried another call immediately after to verify and it started all over again. Now, even reflashing MK2 won't get it to work even once like it did this one time.
Does ANYone who understands baseband and modem firmware much better than I do have any insight or instruction on what I can do? Because of this one issue, I have an otherwise perfectly good S4 that I can't use just lying around. I've had a Nexus 5 for almost a year and love it but I just destroyed the screen after a drop the other day and wanted to switch to the S4 temporarily until the Nexus 6 comes out. ANY IDEAS????
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
faiyo said:
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
Click to expand...
Click to collapse
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
thair7391 said:
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
Click to expand...
Click to collapse
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
faiyo said:
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
Click to expand...
Click to collapse
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
thair7391 said:
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
Click to expand...
Click to collapse
I really have no idea about aosp roms for this device because i only used touchwiz to keep samsung features.. so i have no knowledge about firmware compatibility. I would think the creator of the rom should specify any firmware requirements.
On the thought of hardware failure, and i know you said the speakers work, but did you test the sim card slot? Perhaps it needs to be cleaned? Maybe the sim card is partially failing so try a different card? Maybe you cut it and it's loose (you wont believe the crooked sim cards i've seen). I think it's worth pursuing since you said it worked once and not again.. maybe you had just taken the cover off while flashing stuff and touched/pressed it but it's losing contact again after flexing during use. I dunno dude, the kind of call audio issues i've had were always resolved with a reboot & making sure the modem matches the touchwiz build.
Please make sure you are running a full stock firmware package & keep the touchwiz rom consistent with it. Some firmware packages are partial components
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
For starters, up until a few days ago, I ran all types of ROM with an MK5 boot loader and 3 different modems and never had a call issue. After that said, I read a few months ago about a guy had your same issue. He ended up getting a new sim card and he got is audio back. He also had reception issues before getting the no audio issue.
thair7391 said:
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
Click to expand...
Click to collapse
Try flashing the firmware again, some have to flash it twice for the bootloader to update, which may the trouble. If that doesn't work try a new sim like it was suggested before me
I know it's been a while but I basically gave up and just recently came back to it. I've since bought a Nexus 6 so it's not a priority issue anymore however I would still like to fix this otherwise perfectly fine Galaxy S4 that I have lying around! I seemed to believe that there was a special combination of custom ROM and specifically the MK2 modem that would sometimes cause the audio to intermittently work but it appears I was wrong. I flashed the full stock NH7 firmware/baseband etc back to my phone twice as suggested and NY audio worked! For a few calls that is... Then it stopped working again. Sometimes I could clear cache and reboot and it would work! Once or twice anyways before crapping out again... The bottom line is that there isn't a pattern aside from a cleared cache that makes the audio work again before it stops soon after which unfortunately leads me to believe it's a deep rooted hardware issue in the baseband itself. Anyone else have ideas?
Other than trying a new sim, I can't really think of anything else except to make sure the bootloader really did update. Download Samsung phone info from play store and check bootloader info to make sure it was updated to NH7
Unfortunately it is completely updated. I tried a new SIM and everything works still except audio in phone calls, including ringing. I guess it's hardware... Guess now I just have an internet browsing MP3 player with web browsing capabilities.
Like many other sprint users, I experienced serious problems with 5.1.1. This resulted in battery pulls and even a downloading boot. I starting looking into a fix. After flashing about every ROM for sprint N910P on this website, I either result in bootloop or the same problems persist. The problems are as follows:
-Can't boot, so I have to wait ~5 minutes to try again
-Boots straight to downloading, mmc read fail
-Boots fine
-Crashes to black screen around 80-90% battery (back to problem 1)
I cannot figure how to use odin anymore because it fails on nearly every rom I attempt. My reactivation lock is OFF.
I'll try to provide as much detail as I can, but I'm at my wits end with this phone.
Thanks!
If you can Odin OK1 stock tar, there is another root alternative: root stock with Chainfire Auto Root. CFAR has been updated for Android 5.1.1 Note 4
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Custom ROMs will take longer than 5 minutes to boot initially after flash. TWRP has been known to fail to flash or not properly flash after trying repeatedly to flash wrong tar with Odin or flash with reactivation locked. Which, if any, apply to you? I hope it's not hardware failure...
Sent from my SM-N910P using Tapatalk
Chainfire was going to be my next option. I think the first time I attempted using chainfire through odin, it ended in a bootloop. I haven't tried the update version though. I'll give that a shot.
Is there any way to fix this problem with TWRP (delete it and reflash)?
I'm starting to think its a hardware failure, which would suck because knox is tripped and warranty expired a few days ago anyway I believe.
I downloaded the updated CFAR last night to verify it was updated. It's bundled with Odin 3.10.6 Use the defaults with that for stock OK1 tar.
You should know that CFAR is primarily for rooted stock.
If you want a custom ROM, you may have to use Philz CWM touch recovery for Note 4. TWRP just gets inoperative for some time for some users when tars fail in repeated attempts. Philz' seems to flash where TWRP doesn't if that's the case.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
Sent from my SM-N910P using Tapatalk
Sorry to be the bearer of bad news, but this is most likely a hardware problem. I've had two Note 4's do exactly this. Flashed the stock rom on both with Odin, problems still persisted. It would just get random restarts and sometimes boot into "panic mode", whatever that is. The quality control on these phones is terrible. I baby them and never rooted any of them, yet two of them messed up like that, and all 3 of course have GPS issues. If it worked like it's supposed to it would be amazing, my friend has had one since my first Note with 0 issues, super jealous.
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
bigbabo said:
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
Click to expand...
Click to collapse
To fix the WiFi and camera focus, get the bootloader for OG5 from OP in this thread and flash it in Odin.
https://forum.xda-developers.com/showthread.php?p=66352412
The ones labeled firmware are bootloaders. You don't have to flash the whole OG5 stock tar but you still could. Just make sure the flash restores that bootloader and you should be set.
Likewise, you could still restore a MM backup and restore its bootloader.
I think you should backup your keepsakes in internal memory and wipe internal memory before restoring a backup that crosses Android versions. With backups on extSdCard, you could wipe everything but that but I'd think you could factory reset, wipe internal memory plus the Android folder on extSdCard and have a good transition with the bootloader flash. Otherwise, a factory reset would be the minimum step but may leave some residual information you may not need cluttering your memory along with what you want to keep. Seems I recall some having issues coming back to lollipop from MM without wiping internal memory?
Just curious, do you recall what you wiped going back to lollipop?
Sent from my SM-N920P using Tapatalk
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
bigbabo said:
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
Click to expand...
Click to collapse
Gotcha. Just an old question in the back of my mind from early days of MM. I researched the TWRP thread, the developers recommended a factory reset.
If you've ever noticed internal memory available seemingly smaller than usual, it could be the extraneous folders.
Thanks.
Sent from my SM-N920P using Tapatalk