I'm fairly new to custom roms and flashing. On my AT&T Galaxy S3, I decided to update to 4.3. However, I tried updating ota using the About Phone > Software Update, however, that wasn't working for me (It kept saying: No updates available). I knew this wasn't true, so I searched around and found an option (In which all I had to use was the stock recovery and flash it on there, so I did. However, I found out about Knox and how rooting is not an option with knox, so I decided to look into custom roms. I got a custom recovery, noticed warranty bit 1, don't really care about that since I'm out of warranty anyways. So I flashed a lot of custom roms and their versions (Cm 10.2/11, Paranoid Android, Slim Bean, Illusion, and more) only to find out that I can't play any videos (browser, youtube, 3rd party apps, gallery, and even recording camera didn't work)(Also audio doesn't work at all). Now I want to switch back to regular stock 4.3 using the same file I used before. I tried flashing with a custom recovery (twrp and cwm) and it kept giving me:
(assert failed: file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2:user/release-keys" ||
file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB:user/release-keys"
E:Error in /sdcard/update43.zip
(status 7)
Installation aborted)
I searched around, and other people got this error mostly on a nexus when trying to get back to stock firmware. I found out that I need the stock recovery for the samsung galaxy s3 At&t, which I've searched around, and I can't find. Does anyone know a thread, or can upload their at&t samsung galaxy s3 stock recovery?
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
codemonkey98 said:
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
Click to expand...
Click to collapse
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
danman0 said:
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
Click to expand...
Click to collapse
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
n_alvarez2007 said:
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
Click to expand...
Click to collapse
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
danman0 said:
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
Click to expand...
Click to collapse
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
danman0 said:
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Ali7000 said:
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Click to expand...
Click to collapse
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
danman0 said:
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
Click to expand...
Click to collapse
http://www.sammobile.com/2013/11/20/android-4-3-rolling-out-for-the-att-galaxy-s-iii/ Just a news update
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
COfatboy said:
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
Click to expand...
Click to collapse
I am flashing this right now. I hope that this will work. It turns out that only mxplayer videos work, and no other third party video app. I looked around and these issues are most likely from not updated binaries or something, as mentioned in some threads.
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
danman0 said:
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
danman0 said:
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
Click to expand...
Click to collapse
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
BCSC said:
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
Click to expand...
Click to collapse
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
danman0 said:
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
Click to expand...
Click to collapse
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx? Have you Factory wiped since discovering these issues?
BCSC said:
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx?
Click to expand...
Click to collapse
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
danman0 said:
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
Click to expand...
Click to collapse
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached. See here:http://forum.xda-developers.com/showthread.php?t=2540998
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
BCSC said:
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
Click to expand...
Click to collapse
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
danman0 said:
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I'd recommend heading here and installing the upndwn4par stock ROM again. You did flash the one with the bootloader via that link you sent me. This link does not contain that bootloader. It has already been removed. Flash this and then wipe everything (cache,dalvik and full wipe/factory reset). http://forum.xda-developers.com/showthread.php?t=2540998. This could fix your video/audio issue.
s for your IMEI problem you may find your answer here: http://forum.xda-developers.com/showthread.php?t=2374063
Related
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You will need to update to the latest bootloader (which is different from modem).
If you're on T-Mobile, you'll want UVDMD5: http://forum.xda-developers.com/showthread.php?t=2282603
If you're on WindMobile (or SGH-T999V), you'll want VLDLL1: http://forum.xda-developers.com/showthread.php?t=1949687 (you'll have to ODIN)
re: error 7 - odin flash
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
re: jellybeans
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I never said you should be running JB Touchwiz roms, all I was trying to explain is the best and easiest way to get
your phone back up and running whichever way you like it to run.
If you follow the step by step instructions and the phone is working normally then you can re-flash whichever rom
CM10.1 or any others without any issues unless their is something wrong with the rom you are trying to flash.
The main thing is that it's best to start fresh when someone is having issues like you are having with your phone.
Doing anything else besides what I suggested will only prolong all those issues you are having now.
People will be telling you that your cwm or twrp recovery is not the latest one and you need to update it,
other people will tell you that you must have had some error downloading the cm10.1 rom and they will
tell you to re-download it, then others will tell you to check the MD5 checksum of the download and all
kinds of other things which will just prolong the problems you are having.
None of those things I just wrote will help you to fix the error 7 and other issues you are having.
That's why I posted the step by step which works each and every time to fix errors such as yours and
give you or anyone else a clean and fresh start.
Good luck!
*please ignore*
re: you are right
GenericAsianGuy said:
You need to ODIN the latest TouchWiz JB in order to update all the inner-parts of your phone.
I did this yesterday:
ODIN to the latest pre-rooted firmware (DLL1 in my case (SGH-T999V), MD5 for SGH-T999)
Let it boot into TouchWiz
Install Android Terminal Emulator and the latest ClockworkModRecovery
Boot into Recovery
Factory Reset
Install the latest CM 10.1 Nightly
Reboot
Profit (and spend a few hours re-installing and re-configuring everything again).
Click to expand...
Click to collapse
U R so right! I could not have said it better!
---------- Post added 19th May 2013 at 12:00 AM ---------- Previous post was 18th May 2013 at 11:18 PM ----------
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I forgot to mention, since you are kind of new to this you should not even think of or mention anything
about bootloaders if don't want to end up with a shiny brick.
This has happened hundreds of times in these XDA forums when people mess around with bootloaders.
Flashing bootloaders intentionally or by trial and error is the number one way to end up with a bricked phone.
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
re: flash counter
Dantenios said:
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
Click to expand...
Click to collapse
The odin flash to stock rooted will trip the flash counter, but then each time you flash any rom trips the flash counter too.
You can get the "Triangle away" app to reset the flash counter at the play store.
Actually there is no need to reset the flash counter at all unless you need to
exchange a defective phone which is still under warranty.
Good luck!
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Dantenios said:
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Click to expand...
Click to collapse
All of these roms are stock pre-rooted roms, I am not certain which one is for your
T999v phone. Perhaps the "V" stands for videotron so select that one.
Mobililicity_VLDLL1
Updated JB Firmware
Mobililicity_VLALH2
Updated ICS Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware
Videotron_VLDLL1
Updated JB Firmware
Videotron_VLALH2
Updated ICS Firmwar
Misterjunky said:
Mobililicity_VLDLL1
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Videotron_VLDLL1
Updated JB Firmware
Click to expand...
Click to collapse
Great post Misterjunky!
One of these; it depends on what carrier you're with.
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
re Ok
Dantenios said:
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
Click to expand...
Click to collapse
Yes, once odin is done and you flash custom recovery the phone will be ready to be flashed any compatible cwm/twrp custom rom zipfile.
You would be much better off if you go to the playstore and download "Goomanager" which is a free app.
After its installed, open it and press the menu key and select "installopenrecoveryscript".
Doing that will flash the latest TWRP recovery.
When Goomanager is done flashing, reboot the phone into recovery mode and go from there.
TWRP has a built-in file manager and terminal, plus an option for ADB sideloading.
It has all the options which CWM has and more.
Give it a try, you can always flash the cwm back if you like.
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
re: reboot
Dantenios said:
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
Click to expand...
Click to collapse
reboot the phone into recovery and do a "Factory reset" then restart the phone.
Chances are excellent that it will boot normally if you flashed the correct rom.
Don't wipe anything in recovery.
Good luck!
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Dantenios said:
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Click to expand...
Click to collapse
It would probably be best to edit your title with SOLVED in italics or something so other users are aware and can revert to this thread for assistance rather than starting up a whole new one
Sent from my SGH-T999 using xda premium
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Dantenios said:
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Click to expand...
Click to collapse
If you don't see the Gmail app (and other Google apps) installed, you may need to flash the latest Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.
You need to flash any touchwiz rom in order reset your nvram.
Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
My stock rom I made doesn't have that problem, my wife records my kidz all the time, no issues... try wiping if you left your data, I always wipe all data before upgrading to any rom...
check my signature or in the Tmobile development thread.. completely stock...
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.
chetancc said:
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.
Click to expand...
Click to collapse
I have the same issue. Wiped the entire phone including internal sdcard, went back to stock firmware but nothing worked. Taking pictures works but as soon as press the record button it freezes and a few seconds later the phone will reboot.
Just to let you guy know what I am sure is going on, this video recording damage has been caused by none other than aosp! if you all have previously installed liquid smooth like I did in 3 separate devices
1.tmo s4
And 2 note 3's (one is tmo and one is sprint) I think it is any asop although each person having this damage to their device should answer if they previously installed aosp and specifically liquid smooth.
I was going to assume this damage was only going to happen on tmo note 3, so I tested it on 2 other phones and sure enough they must be forced to remain running asop (the s4 has candy 5) the sprint note 3 currently has the ever so bugging liquid smooth. I also have tried every clean Odin delete everything known to us layman's on the planet and now I am looking for a NV restore. I already tried so sort of a NV item restore Using the dialer *#9090# then pressing Q and then pressing 0000 then option 2,1,2,3 then all with no change. I read somewhere in the xda's grapevine lol about a flash able zip called "Brick_Loop_FIX_afterRestoringBackup" that starts an built in feature that restores or rebuilds the modem then upon boot restores the NV items. I am assuming they are the same thing. Although, with no thought it will fix anything I will flash the zip tomorrow and let you know. I got a couple things to back up incase whatever may happen capin, unless one of you guys try it first, let me know
Haven't heard from the grapevine what protocol, ims or a static rebuild even does except if your imei is all zeros and your don't have any network or stuck in a boot loop after a nandroiid restore I erpose this will fix those couple thing I have read. Although I assume the dialer hidden menu NV rebuild does not really NV rebuild all like it says it does or the all its referring to is really just the first 2 options that are just a couple basic stuffs or it would have fixed my aosp camera damage. Well never listen to anyone who says aosp is all the rave and how you should try it out lol its blackmail to get you to stay on a bugged out ROM forever! LOL
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
I had this same exact problem and i fixed it finally after hours of research and trial and error. I noticed that my baseband and bootloader was Nb4 even tho i had flashed lollipop, so i ended up flashing stock lollipop using odin from http://forum.xda-developers.com/note-3-tmobile/general/5-0-n900tuvufob6-extracted-stock-t3047672 then after flashing i downloaded the lollipop bootloader and used odin 3.09 to flash that bootloader in BL, and the modem in ap, video camera works now and youtube has been fixed also.
How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.
revized said:
How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.
Click to expand...
Click to collapse
Try https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
it tells everything including bootloader version
OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!
revized said:
OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!
Click to expand...
Click to collapse
yeah cool let me know please if it helps!! this was the main reason i had flashed back to kitkat so many times.
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Thanks been looking for this
Ahahahahahahaha! I believe roms can be crafted!
jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.
Docmjldds said:
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.
Click to expand...
Click to collapse
Unmodified stock ROMs do not belong in the android development section so general seemed like the better choice. Any mod, please correct me and move this thread if I am wrong.
Always seem to remember them being in general or Q and A.
Word
THANK YOU for upload to MEGA. I'm getting really sick of the rapidgator spam.
Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!
ShermCraig said:
Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!
Click to expand...
Click to collapse
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse
ShermCraig said:
Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
Click to expand...
Click to collapse
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating Cured by flashing the stock ROM Firmware.
SuperSport said:
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating cured by flashing the stock ROM.
Click to expand...
Click to collapse
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!
ShermCraig said:
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!
Click to expand...
Click to collapse
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Okay, that makes sense. I have been having Amazon FC's since rooting. Frustrating but not as bad as it was at its worst. Using Clean Master for the lag issues and Greenify for the battery. Not sure if they counter each other though. Anyway, I will try flashing the Firmware and report back. Thank you again for clarifying.
SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse
SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.
jamcar said:
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.
Click to expand...
Click to collapse
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.
SuperSport said:
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.
Click to expand...
Click to collapse
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!
ShermCraig said:
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!
Click to expand...
Click to collapse
I've now rooted, and flashed the Stock Recovery back to my phone. Deep Sleep is working fine. I'll monitor it over the next few days to see what the battery life is like.
Here is the Stock Recovery for T-Mobile Edge SM-G925T.
https://drive.google.com/file/d/0B3nX3DCjdq6MWS00NHFqRVhOVlk/view?usp=sharing
jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse
This is exactly the the situation that I am in. I am glad OP posted the stock firmware.
Does anybody know why my phone gets stuck in a boot loop when I try to root. I used the S6 version as was suggested in the root tutorial, everything goes smoothly but then it just bootloops.
Where are the roms at guys I'm trying to build one as soon as I finish fixing my pc
hey guys
So I rooted my Exynos S20 Plus after updating it to ATE6 . Since then when I try to open camera I just get "camera error" even after restart.
I tried to use the Samsung service menu and get "unable to connect to camera service" there
Anyone else experienced this and might be able to help?
Thanks!
Did you try resetting your phone once?
If it doesn't work reflash the rom with odin
RohanKalra97 said:
Did you try resetting your phone once?
If it doesn't work reflash the rom with odin
Click to expand...
Click to collapse
Hey,
thanks for your answer.
When reflashing original firmware: Camera works.
When flashing the "vbmeta_disabled.tar" in USERDATA and the modified "KERNEL-G988BXXS2ATD5" (with Mgisk manager) as AP the camera no longer works, even after two full resets via recovery.
mautz001 said:
Hey,
thanks for your answer.
When reflashing original firmware: Camera works.
When flashing the "vbmeta_disabled.tar" in USERDATA and the modified "KERNEL-G988BXXS2ATD5" (with Mgisk manager) as AP the camera no longer works, even after two full resets via recovery.
Click to expand...
Click to collapse
"KERNEL-G988BXXS2ATD5" is for the older firmware. Please wait and it will be updated for the latest firmware.
If you follow the instructions you can make your own boot.img to suite ATE6. That will fix your camera issues
https://forum.xda-developers.com/galaxy-s20/development/howto-root-phone-s20-t4067649
RohanKalra97 said:
"KERNEL-G988BXXS2ATD5" is for the older firmware. Please wait and it will be updated for the latest firmware.
Click to expand...
Click to collapse
Wow. Sometimes I dont know if my brain is actually active and running or if its just melted or sth.
When I flashed the kernel I "checked" the number and was "ah great, the same". But well I somehow still mixed them up.
After manually packing the new boot image it worked
THANKS!!!!!!!!!
heslo.rb26 said:
If you follow the instructions you can make your own boot.img to suite ATE6. That will fix your camera issues
https://forum.xda-developers.com/galaxy-s20/development/howto-root-phone-s20-t4067649
Click to expand...
Click to collapse
Thanks, those worked like a charm!
If the image could be beneficial to someone please tlel me and will attach!