Hi All,
I'm am absolutely stumped and have tried what feels like everything I can to resolve my issue to no avail. So, I'm hoping to find success from the wisdom of the seasoned XDA community.
I have an SGH-T999 with baseband UVDMD5. In early September, my camera stopped working. When I open the camera app, I'm greeted with the infamous "Can't connect to camera" message. The front camera works fine (via Skype), but the rear camera does not. I've tried all of the following but the camera still won't work:
1) Unrooted and re-flashed the stock root66;
2) Finding the correct "SLIM_ISP.bin" file, placing them in the /data folder, and set the permissions to 777;
3) Re-flashed the stock UVDMD5 bootloader, firmware, and modem;
4) Took the phone to a shop to have a new camera installed and they couldn't get the new hardware to work either (so, it's definitely software related);
5) Cleared the app cache and fixing permissions in recovery;
6) Restored a Nandroid from a previous state of the device when the camera was fully operational;
I don't know what else to do. PLEASE help me folks. I really want my camera back. Thank you in advance for your time and insight.
I've attached a Catlog I recorded while attempting to open the camera, if that helps at all.
just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness
Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Have you considered replacing the camera hw? It's very easy to do and the part usually costs less than $10.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi Doc, I tried that. Sorry. Should have listed it. I took it to a shop to have a new camera installed and they couldn't get the new hardware to work either. So, it's definitely software related.
Thanks for the suggestion though. Please let me know if you have any other ideas.
mrrocketdog said:
just a thought , but if you have a nandroid backup could you uninstall current camera and then grab camera from nandroid and install it ?
or if have titanium backup hit the install button on camera apk (even though its already there). these methods have worked for me with browser issues.
just an idea.
good luck.
err on the side of kindness
Click to expand...
Click to collapse
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.
At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
halebopper said:
mrrocketdog,
Would that work if the camera doesn't work even when the Nandroid is restored (despite that fact that the camera was functional when the Nandroid was created)? Thank you.
Click to expand...
Click to collapse
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness
mrrocketdog said:
i think that would be the point. the camera was functioal when the nand was created.
dont know exact function , but what about going into recovery and fixing permissions.
and going into settings>apps>camera and clearing cache ? wouldnt take but a minute and it already doesnt work so....
err on the side of kindness
Click to expand...
Click to collapse
Thank you for your response and the suggestions.
That point makes complete sense. However, what I'm saying is that I've restored s Nandroid from a state when the camera was functional. However, the camera still doesn't work despite restoring a Nandroid from a previously operational state. So, please correct me if I'm wrong, but, considering that, what good would extracting the apk from the Nandroid do if restoring the entire Nandroid doesn't make the camera work?
Regarding your second suggestion, I have tried clearing the app cache and fixing permissions, but it didn't work. I'll add this to my list of attempted fixes in my original post.
Thank you very much mrrocketdog. I sincerely appreciate your continued interest and support. I hope we can figure this out.
well dang it ! hopefully someone else will chime in with some ideas. sorry i didnt have anything new. will keep thinking.
err on the side of kindness
DocHoliday77 said:
At this point I think that would be worth a shot. If it doesn't work though I'd have to say it sounds like it could be hardware related, even though you replaced the module. Might be a problem on the motherboard or something like that.
The only other thing I can think to try though is to flash a 4.1.1 rom. Then using the hidden code to write the camera firmware to the device. If the firmware got corrupted somehow, this could fix it. The problem though, is if you've updated to 4.3 firmware, it probably won't work. They patched against our ability to write the cameras firmware ourselves. If this was done in the controlling app, it may just work. However, if it was patched in the base firmware, there won't be any way I know of to do this.
I'll post the code in a min. Gotta hunt it down again...
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:07 AM ----------
Ok here are the codes:
*#34971539#
*#7412365#
Enter in the stock dialer.
I'm pretty sure the first one is the one you need, but both are camera codes which is why I gave both.
If it works, it will open a menu called Camera Firmware Std
You can check the firmware versions first if you like. If the phone fw is older than the cam fw, and you do this, it is possible you could loose some features. But if so, I imagine flashing the device firmware again will update back to where it should be.
To write the camera firmware, just choose Phone to Cam FW Write.
Good luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi DocHoliday77,
Thank you very much for the reply and the suggestion. Your advice seems sound.
I'm not sure what you mean by "controlling app." I'm afraid my knowledge is too limited to tell you if I've flashed the 4.3 firmware.
Not sure if this helps, but I have intentionally not upgraded beyond the stock baseband UVDMD5 version. I understand the baseband versions following UVDMD5 are bad due to the addition of KNOX and the inability to flash back to previous baseband versions.
Currently, I have flashed Carbon rom, which states the Android version is 4.4.4. However, I don't know if the Android version number is reflective of the firmware.
Regarding flashing a 4.1.1 rom, is there a rom you suggest that would be better for this than others? Should I just grab an older version of Carbon or would it be best to use Odin to flash back to a stock root66 version of 4.1.1 ?
Btw, not sure if you saw, but I uploaded a Catlog I recorded while trying to launch the camera app. I don't know if that will reveal anything or not. I can't make two cents of Catlogs other than to identify that errors are occurring. I really hope this isn't a faulty motherboard.
Thank you again for your continued interest and support. I really appreciate your advice. It means a lot. I hope we are able to resolve this.
If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If you never updated beyond 4.1.2, you can fully downgrade to 4.1.1 and try that method I posted. The app is just the one that controls the cameras dialer code. You don't really need to worry about it. Don't remember which it is right now anyway...
If you like though, first just flash stock 4.1.2. The code might work there. I just can't remember if it was patched there or in 4.3. You'll know you need 4.1 1 if you open it and the firmware write choice is greyed out.
I suggest just flashing the root66 firmware rather than a rom. This way everything you need is included. If it does solve the problem you can flash back to whatever you like.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok Doc. I flashed root66 T999 UVDLJC (Official JB Firmware - Latest JB 4.1.1 Firmware). After rebooting the phone, I entered the first code you provided - *#34971539# - into the phone dialer. This pulls up an all black screen with a gray colored placeholder/header at the top that reads, "CameraFirmware Standard." Again, other than the gray header and title, the rest of the screen is all black with no text or anything, except for the notification bar at the very top. Then, after sitting on that screen for a few seconds, it closes and the message, "Unfortunately, Factory Test has stopped," displays in a pop-up message.
I can make my assumptions about what that means, but I'd prefer your opinion. What do you think?
Thank you again for your time, insight, and assistance. I respectfully look forward to your response.
p.s. Just to clarify my experience for potential future readers, the second code you provided - *#7412365# - didn't work. It displayed, "Unable to process request" in a pop-up message.
That tells me that the system is most likely having problems communicating with the camera.
I'd open it up and make sure it's properly connected. It's very easy to do. You can find disassembly videos on YouTube if you want to see what to look for first.
If the shop couldn't get a new one to work, I'm honestly not sure what else you can try. It does sound like a hardware issue though. My best guess is its got something to do with the motherboard.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Related
Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel
FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.
I'm getting ready to download it
When I go to flash the radio, Odin says it's an invalid image type
circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?
XD Now I feel like a ruh-tard. I forgot about that part
Wait, it's still saying invalid image type
I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?
No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..
If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind
^ lolololol
Sent from my SCH-I400 using XDA Premium App
FROYO
i think i love you (no homo)
I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.
Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App
It all started here:
http://support.t-mobile.com/thread/44716
I griped on the T-Mobile forums about the struggle I've had in finding a smooth ROM for my T999. And I made an off-handed comment in another thread that got me pointed in the right direction hopefully. I'm looking for other T999 owners that have this problem.
The problem on DMD5 is all related to (apparently) intensive tasks. Playing games, mostly. Temple Run 2 and Fruit Ninja, neither of which are all that intensive, were nigh-on unplayable. Other games like Scramble with Friends would lag and stutter a bit, too. So after a lot of searching, I reverted to a pre-rooted T999UVDLJC with the matching baseband, so that way my phone doesn't try to update itself OTA. And performance is pretty good. But I'd like to think that I'm not alone, and I found I'm not alone in this thread:
http://forum.xda-developers.com/showthread.php?t=2326763&page=33
At the bottom of this page and the top of the next one, I found at least one kindred spirit that has a rev0 phone and has the same issue with DMD5.
NO other ROM has this issue. I've tried all of the official Samsung ROMs and I have tried official CM10.1 nightlies and the official 10.1 stable release and performance is very good on all of them. But it took a huge serious nosedive on T999UVDMD5.
So I'm curious about two things:
Does DMD5 run well on your phone? Particularly with games - that's where it was most notable, but even TWLauncher is laggy for me.
How old is your phone? According to the box for my phone it was built 6/30/2012.
If you are affected, could you help us all out on the T-Mobile support forum, and post a message in my thread at the top of the page? If we can get T-Mo and/or Samsung to look into it maybe we won't get left behind. I plan on using this phone for another year or more and I'd rather get the official updates in the future, too.
Update July 6, 2013: I found out thanks to help from people in this thread that I can run mismatched modem firmware/ROM and with the JLC modem on MD5 ROM, my phone runs fantastic. Or at least it has for about 2 hours - usually issues have shown themselves by now, and since they haven't cropped up I'm calling this resolved.
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Please do not check "yes this is a question" if it is "info gathering" as all Q's are moved to Q&A. I will edit the title for you.
FNM
DocHoliday77 said:
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've tried all of the above. I even let Kies install it once. I've used TriangleAway and Odin to install 4.0.4 and let it do all the OTAs. Iv'e done factory resets and I've told setup not to restore my data to the phone and started from scratch. I used a flashable ZIP with the pre-rooted ROM, and when I did that I also got the DMD5 modem flashable ZIP to go along with it. I've tried not rooted. I've tried custom kernels, and I've tried stock. Odin completely stock and flashable zip totally customized. I've played with custom DMD5-based ROMs with the v6 script and I've tried not. I'm way out of ideas right now.
Sorry, @kennyglass123, I didn't realize I'd checked that box.
Starting to think all of them have "rev 0" for the CPU identifier, so that may not be the way to tell who has what.
Just to be clear, did you ever Factory Reset, then Odin flash MD5 (not mobile odin btw), and factory reset again to ensure internal sd was cleaned out too? If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Don't get me wrong. I'm not trying to argue against your point, just to make sure not only that you've covered all angles, but that anyone who wants to back up your claim has also done the same.
As for the revision number, it may still be relevant as mine would have been among the first built too. We would need to find at least several others with the same, and different, to know for sure if it matters here.
Its always possible too that you got the unlucky pick of the hardware. (Just as possible though that I got a lucky pick)
Anyway, if you really are having that bad of problems with it, you may want to check if its still under warranty. I don't believe its the norm though.
Sent from my SGH-T999 using xda premium
Yeah I'm pretty sure, but I'm willing to do anything at this point. I'll do it again. I've stashed the Odin tar.md5 file on my backup hard drive, so I'll back up my working config and flash it again. Worst case scenario is that I re-root it, re-install recovery, and then restore my backup. Should take an hour max.
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
DocHoliday said:
If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Click to expand...
Click to collapse
There is no possible way it could be necessary. Proof or it's placebo.
DeerSteak said:
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Click to expand...
Click to collapse
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
DeerSteak said:
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Click to expand...
Click to collapse
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Aerowinder said:
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
There is no possible way it could be necessary. Proof or it's placebo.
Click to expand...
Click to collapse
I don't reboot unless the battery dies, or I was rebooting a lot when I was on MD5 trying to get stuff to work well. Generally I try not to mess with a good thing.
DeerSteak said:
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Click to expand...
Click to collapse
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK, I won't mess with it too much then. I've backed up my internal storage already and I've backed up my SMS using SMS Backup and Restore. That thing has been very handy keeping copies of my texts while I screw with this.
Cool, sounds like you're good to go! Good luck! And let us know how things seem to be acting after flashing.
Don't forget to factory reset after flashing md5.
:thumbup:
Sent from my SGH-T999 using xda premium
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
DeerSteak said:
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
Click to expand...
Click to collapse
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Aerowinder said:
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Click to expand...
Click to collapse
OK i'll give it a go. Thanks.
Should I re-flash the MD5 modem?
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Aerowinder said:
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Click to expand...
Click to collapse
OK I see it there. So I should use the LJC modem/firmware with the DMD5 debloat ROM you're going to PM the link for to me? Will they work if they're mismatched? I assumed (not that I'd bothered asking before) that they'd all have to be the same.
After rooting, launching the camera app resulted in some errors. I cleared the cache and data, and everything looked fine. I went ahead and flashed a custom ROM. Then I realized the FFC was not working. I'd get camera error. Someone said that I should go back to stock to see if it worked, and I flashed stock, and it still didn't work.
Not sure what to do next. The FFC was working fine before the root operation. Any tips on how to restore the FFC functionality?
You need to supply more info as far as what os, rom, what else isn't working before you get any input. If all is well and just the camera is borked you can always flash a camera apk. Reflashing the rom may also help.
Pp.
Sent from my bluetooth equipped toaster using mind control.
PanchoPlanet said:
You need to supply more info as far as what os, rom, what else isn't working before you get any input. If all is well and just the camera is borked you can always flash a camera apk. Reflashing the rom may also help.
Click to expand...
Click to collapse
I flashed Virgin ROM (http://forum.xda-developers.com/showthread.php?t=2343513). I tried to flash over the camera.apk from OP. It didn't help. I have since then clean flashed the same ROM and a couple of its updates, and clean flashed KOT49H(http://forum.xda-developers.com/showthread.php?t=2539361). At all times the FFC did not work. Someone suggested that I flash a different kernel. I tried that but ended up in a bootloop and reverted to the KOT49H. I also did try to ODIN flash the stock ROM, but found the camera to be not working there too. I am now running the KOT49H ROM. Everything, except the FFC, works.
Not trying to be rude but this why backups are made before you flash something
Sent from an A.I. frequency
Kriptik210 said:
Not trying to be rude but this why backups are made before you flash something
Sent from an A.I. frequency
Click to expand...
Click to collapse
I believe something went wrong right after I rooted the phone. Backing up would not have achieved anything.
Maybe it's hardware failure what you're dealing with. Not sure but there may be a dialer code you can enter using your dialer that can check to see if it works or not. You may need to be stock firmware /Rom in order to do this. Google it.
****** Edit ******
Try this https://www.google.com/url?sa=t&sou...1ce0hlHnyNRhUDpxw&sig2=sLCXBjxinKSz0GeZWCkM_w
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
Maybe it's hardware failure what you're dealing with. Not sure but there may be a dialer code you can enter using your dialer that can check to see if it works or not. You may need to be stock firmware /Rom in order to do this. Google it.
****** Edit ******
Try this https://www.google.com/url?sa=t&sou...1ce0hlHnyNRhUDpxw&sig2=sLCXBjxinKSz0GeZWCkM_w
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
Click to expand...
Click to collapse
Thanks. None of those codes for the camera worked. It's annoying to go to stock. I'll just live with it for now!
Maybe it's a warranty issue.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
Ok let me be really specific i have flashed stock firmware through odin, i have done clean wipes, i have done every possible thing in my power but still experience horrible tablet preformance i get app stops and restarts everytime even after i have flashed on odin no one here has been able to help me they tell me to do the same thing over and over download stock firmware and flash, do a clean wipe iv'e done it all please help i know someone can i think its a file in the screenshots i enclosed that is corrupted but i have no idea which one is it. its not the system or the kernel it is something deeper please help i am begging you developers
k,
no offense, but your post is wildly disrespectful. [frowny face]
you are basically putting the proper ownership of your error off on others.
to be fair, in your ignorance you flashed a firmware without first doing some research on the topic.
a noobish mistake, it happens, i've done it.
there were plenty of threads created prior to your experience warning of new samsung releases
overwriting bootloaders and how to navigate the issue.
from my interaction with you, i think i am accurate in saying you did not do the aforementioned research.
i for one took time to describe a way to "fix" your issue. You chose not to attempt it, which is fair. It is risky.
Cool.
However, lots of the users you've interacted with on xda have a fair to expert handle on how to get things done.
they do what they can to help, they cannot be expected to compensate for another's impatience, lack of attention
to detail and/or incompetence/ineptitude.
m
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
kgalv419 said:
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
Click to expand...
Click to collapse
hmm,
okay, different approach.
http://m.youtube.com/watch?v=JmvCpR45LKA
just a refresher.
now,
screenshots of directories are next to useless.
what's needed is , at the very least a logcat.
to get that or anything else moving you need,
custom recovery installed.
root.
busybox.
adb setup properly on pc.
the ability to describe you problem in words other than my thing doesn't work.
the sense not to keep creating thread after thread concerning the same issue.
if you are that insistent on undoing what you have done, my previous suggestion to you is probably the best bet.
if you want "Professional" help then seek a repair service.
Savvy?
m
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
kgalv419 said:
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
Click to expand...
Click to collapse
k,
okay, cool. sorry for being so rough on you.
i am downloading a copy of 4.4.2 firmware though linking me to the firmware
you initially flashed would be good.
what would be better is if you still have the firmware file crack it open with 7zip and get me a list
of the files [.img, .bin] inside.
run logcat after you boot up. attach to post as text file
then run your routine to where you get your issue, fc's etc and run logcat again and post as text [2]
m
okay it looks like i am not going to be downloading the 4.4.2 firmware.
downloads break from the one source i found
and i have no interest in joining the other site. that's bull****.
so if you can get me the list of files contained in the realease that would be helpful.
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
kgalv419 said:
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
Click to expand...
Click to collapse
k,
dude, where's my car ? [log ?] :silly:
m
Here bro
kgalv419 said:
Here bro
Click to expand...
Click to collapse
k,
i am going to guess you are trying to run a battery/governor tweaker ?
i am going to guess when you type getenforce in terminal
your output will be enforcing.
i am guessing when you resend your logcat you will do so after
typing su
and then
logcat -d > /sdcard/logcat.txt
if my guesses as to the app and selinux are correct you;
a- need to let the app go into the dustbin of history
b- need to look for a tutorial on dumping/unpacking/customizing/repacking/reflashing your boot.img
in order to disable selinux and make it stick.
if my guesses are wrong it is because;
the log you posted is super-lame [sorry] use your terminal, not a catlog app.
you have yet to tell me what app are giving you your headache. in which event is an issue between you
and the app's developer.
lastly you should be question the developer of the rom.
m
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
kgalv419 said:
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
Click to expand...
Click to collapse
k,
okay, this ---> android.permission.INTERACT_ACROSS_USERS_FULL is the ballbuster.
it's connected to , from what i've read so far , a maybe faulty root and multiuser.
what version supersu are you using ? unroot and then reroot trying from version 1.97 maybe to 1.99.
kill multiuser and clear out any suspect accounts in settings. will post back if i find something more conclusive.
you can jump in as well by searching the error i mentioned.
android.permission.INTERACT_ACROSS_USERS_FULL
m
@kgalv419
edit after rooting set actions to auto grant permission and trust system
EDIT - disable xposed modules - xprivacy if you're running it.
QUESTION - THIS IS A JELLYBEAN ROM ? seems to be a jellybean issue...
EDIT-EDIT i found this... http://forum.xda-developers.com/gal...card-app-data-to-extsdcard-tw-t2178863/page16
read that page looking specifically at the portion concerning /system/etc/permissions/platform.xml
you may need to add/edit the line for
android.permission.INTERACT_ACROSS_USERS_FULL
with the proper uid [user identification] meaning the right number/symbol for root,shell,ewok, etc.
the entry looks something like this;
<assign-permission name="android.permission.INTERACT_ACROSS_USERS_FULL" uid="shell" />
and remember to reset the file's permissions correctly - 644
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
kgalv419 said:
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
Click to expand...
Click to collapse
In a situation like this thinking is guessing = no good.
re-read previous post. search, test, verify. Don't guess [think].
m
Yes bro trust me I'm trying
Are you able to flash CWM and root your device ?
I will advise what is next to be done....
Sent from my SM-T211 using XDA Free mobile app
Yes I already have it rooted with philz touch recovery
Wipe format every single partition that you see remove 1st your ext sd card this will empty all folders then redo tne Odin part
Sent from my SM-T211 using XDA Free mobile app
By every single partition you mean including those folders like acc, and others in the device?
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.