Related
This is my journey from Eclair to Froyo - read only if you have ample time. You have been warned !
I had never tried even rooting my Galaxy I5801 so I was a bit hesitant to upgrade my DDJG6 Eclair to DDJP2 FROYO even via Kies. After some days of the official release I finally plugged my phone to update. But alas, Kies constantly showed "operation timed out" (poor connectivity ?) and I was left with no other choice but Odin
DAY 1:
Downloaded the flashing package and the relevant firmware, connected and fired up Odin as per the tutorial. Loaded the packages and started the process with a prayer on my lips. The first boot nearly gave me a panic attack but the tutorial did calm me down and voila ! I had successfully flashed Froyo. Thereafter I also loaded my backed up contacts & memo data through Kies sync.
DAY 2:
I was happy with my effort and started explorin the possibilities of FROYO including app2sd. All fine until I decided to install a flashlite plugin later that day. The system starting freezin so I rebooted. The problem recurred and I again rebooted. This my boot screen got stuck on the "GTI5801 - Samsung" screen. I knew I was screwed but since I could access download / recovery mode (even though wipe data or cache didnt work) I knew it was only a "soft brick"
Day 3:
Geared up to reflash my phone through Odin. This time I took some unusual steps - removed bootloader & sbl and extracted dats.rfs from DDJG6 & added it to DDJP2 tar package. Flashing was succesful and I had started to sort of like the entire process.
Day 4:
Was disappointed with the improper implementation of swype so I decided to install swype beta. Root, delete, register and install - simple ? That's what everybody says.... Downloaded superoneclick, enabled USB debugging and rooted (Z4root didnt work). Now the delete process was tricky. Couldnt make sense of titanium backup so tried another method. Since root explored is paid app and terminal emulator is beyond my scope, installed super manager from market. Gave superuser permission and started deleting relevant swype files - I think it was 2 from /system/app, 1 from /system/lib and 1 from /data/data. Registered for swype beta and downloaded it as advised on the website. I write this post with swype beta.
Everything is working fine now - almost !
PROS - learnt flashing, knew the benefits of rooting, now can manage my apps and memory a bit better
CONS - My music player is screwed. For that matter, any music player I have downloaded and tried is having the same problem. The player doesnt play some music files, skips it or even if forced to play remains mute although the music play status bar moves. I checked the file properties and played them on PC. They are either Mp3 or M4a. Do I need to reinstall the music player coz it sounds like its become corrupted ? But then it plays some tracks flawlessly
I am in debt to XDA Galaxy 3 forum members and rudolf in particular for helping me out at crucial junctures. Now if only I could solve this problem !
jg6 is an eclair rom right? That could be causing problems, mizing eclair and froyo.
Did you do a factory reset after flashing (I suspect you did if you followed a tutorial).
Also, removing boot and spl is not unusal, it is HIGHLY RECOMMENDED, always do it! (this is mostly for other people reading this thread)
Nice story... Waiting for day 5+
@stubborn - yup, i did a reset but the music player problem persists. I included the data.rfs file from eclair to froyo coz I was somehow convinced that its absence in the DDJP2 had causes my system to freeze the first time
@kyrillos - Day 5+ testing isnt exactly detailed. The only thing I noticed is that the battery drain was more than DDJG6 eclair or maybe its the battery bug acting whimsically (as it usually does). Havn't modified or tested the GPS so no comments. Installed Gingerbread keyboard but not exactly to my taste. Still using a combo of swype and regular tap.
BTW - ur ROMS are damn good judging by the features, performance feedbacks and screenshots. However, It will take me another leap of faith to flash one of those since the complexity involved is beyond my current level of expertise (or rather the lack of it !)
Any ideas / tutorials on deleting the stock music player app and reinstalling it (with apk files, if possible) ?
I've flashed new JVP into my SGS using ramad's deodexed firmware with CF-root kernel and JKay skin. Then I restored my backup and used it for some time. After one reboot I noticed that it suddenly got much slower than it was - before I got quadrant score of 1900-2200, after it dropped to ~1300. After some investigation I found that there must be some problem with my settings - if I use some "clean" database (com.android.providers.settings) it works like it should but with my backed'up data it works fine only if I boot it with bluetooth turned off.
Can someone suggest what could have I done wrong?
Try to re-flash and use the stock Kernel, then see if you get the same problem. If not then only restore /data applications (Never restore /system applications) and see again if you get a problem, and so on..
You need to find out at which stage you get the problem, this could help isolating the problem so you can help finding a solution by finding out what cause it... in the way you are asking every member will give you a theory, try to find out by your self, devices are all different and so are the applications/settings/Kernels are all different on members devices.
Sorry for beeing so vague on the first post.
I did tried to isolate the problem - reflashed everything at least 10 times with different configurations. The result is I can show the exact moment when after restoring the backup phone starts to act weird.
Unfortunately the problem probably lies somewhere in my old settings as restoring only this one piece into the clean firmware (or - as my steps were - after flashing cf-root and installing theme) doesn't activate the slowdown. Unfortunately I also did a mostly clean restore - restoring only things I really need (contacts, bookmarks etc.) and only a few applications with data and for the rest of backup only applications. It didn't help.
Today I'll try another way - I'll reflash it and then restore only applications without any data and see what would happen.
Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now
matofesi said:
Ok. So I did another round and for now I'm satisfied with the result.
What I did was:
1. reflash deodexed JVP
2. restored my user apps with data from backup
3. restored pieces of system data and configured missing settings
it worked fine up until this point
4. reflashed to CF-Root kernel - it seems this broke my setup. I'm certain that there must be something in my config/installation that when added to CF-Root and bluetooth introduces slowdowns.
5. as I needed my theme I just flashed it using CF-Root's CWM and after that I reflashed back to the stock kernel - everything returned to normal - quadrant score was back up at ~1300 (from around 700 with CF)
6. as I also wanted to convert to ext4 I flashed a Speedode kernel and I test the speed - it showed stable 1300
7. converted to ext4 using SpeedMod's CWM then rebooted and retested with quadrant - it holds fine at around 2200.
This closes the case for me for now
Click to expand...
Click to collapse
Good work, and you did it all on your own
Now you know what was the cause for your trouble and how to deal with such problem next time.
For others that find themselves in a similar predicament, but want an alternative method (or workaround), then keep reading.
I too am using Ramad's deodexed Rom's with CF-Root & have similar problems.
Ramad, I know it's not your Roms.
There is definitely something flaky after flashing CF-Root (no disrespect to Chainfire) , as I can replicate the faults again & again & again, with only the deodexed Rom & CF-Root, APN & WiFi setup. No user apps or anything else on the phone at this stage.
Certain problems then arise (lag is often noticed first) after the phone is restarted while ever WiFi & BT are both turned on prior to restarting the phone.
See my posts in the CF-Root thread here (Posts #2151 & #2152) which lists a few other problems which arise after flashing CF-Root, along with my workaround in post #2152.
It'd be great if Chainfire was able to get this issue fixed, as a workaround is never as good as a permanent fix.
If anyone found my workaround worked for them, feedback is definitely welcome.
Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Greetings,
The camera on my Note 3 is not working for video recording (taking pics works fine). I have switched a lot of roms and kernels on it, but I noticed the camera app would not record and, instead, show me a "Warning: Recording Error" followed by a force close and, usually, a reboot.
I decided to switch back to stock Lollipop to see if this would revert it, but it didn't work.
The phone specs and other info:
SM-9005
Currently on official Lollipop from Brazil (N9005VJUGBOD5_N9005ZTOGBOD4_ZTO from sammobile)
Stock kernel
These are the things I did to try and fix this, not in order:
1- Changed kernels
2- Changed roms (always wiping everything but internals on recovery before doing so)
3- Cleaned cache
4- Cleaned camera cache
5- Tried google camera app instead of the official camera app (it did not FC, but while it said it was recording, it would never save a video file of it)
6- Did a factory reset on the stock rom
7- Updated modem and bootloader with the files on the Aryamod thread
8- Tried removing the SD card completely
9- Tried reseating the SD card
10- Tried changing to internal card in the camera app
11- Changing recording resolution options
Last custom rom I had was the Omega Rom. First Lollipop rom I installed was the official (non leaked) Poland rom, and I did not use a pit file back then (as, according to the thread this was featured it, that file was meant only for users coming from the leaked lollipop rom).
This is the log from the camera bugging out in the Omega Rom:
http://pastebin.com/TkCA2KbT
I took a second one for precaution:
http://pastebin.com/1exMLTk3
This is not a hardware problem as it worked on KK. The problem persists on the official rom I just installed. Also, the SD card has a lot of space available, as does the internal memory.
Also, not sure if this is relevant, but most kernels give me a bootloop, exception being the Omega kernel and the Darkqueen. I also *may* have flashed by accident a rom based on Cyanogen at some point, but my memory is very fuzzy on this. I think that this wouldn't matter as I wipe everything before putting a new rom in, anyway (and if I did that, the new and now correct rom I put after that wouldn't leave any traces of this accident).
I have no idea what else to do to fix this.
I have exactly the same problem. I have a ZTO Note 3 with the same problem as well, sometimes the whole android crashes after I try to record it.
The whole problem began after I installed the Omega Rom, I used CM12.1 for quite some time and the camera record correctly. I am not sure if you managed to wipe the whole thing by using the TWRP, but once I did, I found out that it was a MTO problem, which I searched about and it was nothing major.
Did you manage to fix the problem?
Maybe install latest bootloader?
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Journyman16 said:
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Click to expand...
Click to collapse
white7561 said:
Maybe install latest bootloader?
Click to expand...
Click to collapse
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Leminur said:
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Click to expand...
Click to collapse
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Video not recording
Do you have a link to the kernel and has anyone else tried this? I'm also having the same problem with the video recording not working and I'm not sure what to do about it.
chickenlittlesound said:
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Click to expand...
Click to collapse
I'm having exact same problem
I'm also having this exact same problem with my N9005 Note 3. Its running Lollipop but i don't really much about roms as i bought it used from some shop. Everything works fine both cameras take pictures but video recording doesn't work at all. Also i downloaded a screen roader app and its videos are also not recorded. When i finish recording them and go to gallery it says File Corrupted. Please anyone got fix of this problem yet?
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Hi everybody,
@hayder78,
I tried to do the same to fix the issue: flash with the last firmware available for my region code (XEF - N9005XXUGBOK6) using Odin 3.11.1 and the same options (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update) but I still have the issue.
@Fenrir007
Did you manage to fix the issue using the same method?
I had the same issue with a 6.0.1 ROM (MagMa-NX UX8.5) on my Note 3 N9005. Any attempt to record video merely resulted in a "recording failed" message after about a second.
I thought I had installed a recent bootloader and modem using Odin 3.11.1, but although I did it twice I had used a "Reboot to Download" restart and for some reason that does not seem to have taken properly - although I have no idea why, all the display messages said it had worked.
So I have just done a full (remove battery and then three-finger power-up) boot into Download as advised in this thread, and then sent the same BL_N9005XXSGBQA1 and CP_N9005XXUGBOJ2 files to the phone via Odin, and now video recording works fine.
So when people say clean boot into Download, they do actually mean it. Thanks folks!
Oh, and I did NOT need to tick the "clear EFS" option, which seemed a rather risky thing to try so I was avoiding it as long as I could.
Andre