Database Users

[Q] Camera Error "Cannot connect to camera " in STOCK 4.2.2

So i have a Nexus 10 running 4.2.2.
-Stock
-Non rooted
-Non unlocked
Since about a day i have been getting the error
Camera Error
" Cannot connect to the camera"
I have tried to
-Clear the cache
-Multiple reboots
-Services cache clear
None of them worked and im getting the same error and none of the onscreen camera controls work.
Help is appreciated.

??
poikilo said:
So i have a Nexus 10 running 4.2.2.
-Stock
-Non rooted
-Non unlocked
Since about a day i have been getting the error
Camera Error
" Cannot connect to the camera"
I have tried to
-Clear the cache
-Multiple reboots
-Services cache clear
None of them worked and im getting the same error and none of the onscreen camera controls work.
Help is appreciated.
Click to expand...
Click to collapse
Any advice ?

Best advice is to contact Samsung and start harassing for an RMA, sadly. It looks like hardware issue.

poikilo said:
Any advice ?
Click to expand...
Click to collapse
Factory reset? Reflash stock image?
Sent from my Nexus 4 using Tapatalk 2

Some background service is probably using your camera. It will probably show up under battery stats near the top of the list.
You can do a factory reset to verify if you are willing to lose your settings.

Update
zivan56 said:
Some background service is probably using your camera. It will probably show up under battery stats near the top of the list.
You can do a factory reset to verify if you are willing to lose your settings.
Click to expand...
Click to collapse
I havent done a factory reset yet. I will update this as soon as i do so.
I just wanted to know if there are any known fixes for this.

I used to have this problem on ICS on my Droid4. No one at the stores or online could ever seem to figure out a fix... but I did! (Yay me! Uh-huh!) Sadly, its not a silver bullet for you, because this was the fix:
-Remove the SD card, reboot the phone, access the camera (which will then work), then shut down, re-insert SD card, turn back on
You should play around with:
-USB settings, such as MTP mode and developer settings USB debug = try turning them on and off, rebooting and camera attempts in between
-File Explorer utilities that could allow you to wipe or reformat the emulated SD portion
Best of luck,
bm

I've had the camera connect error on a custom ROM/Kernel with Google Goggles. First time I've had the issue actually. Upon reboot, all was well, so it seems it was only a one-time thing.

If everything else fails you could try to open the tablet and see if the camera became disconnected from the rest of the hardware. The camera plugs into the mainboard via a tiny ribbon cable.
front camera:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rear camera:

Replies
EniGmA1987 said:
If everything else fails you could try to open the tablet and see if the camera became disconnected from the rest of the hardware. The camera plugs into the mainboard via a tiny ribbon cable.
front camera:
rear camera:
Click to expand...
Click to collapse
Im too scared to dismantle my tab. But if all else fails, i will try this and contact you. Thanks.
bigmatty said:
I used to have this problem on ICS on my Droid4. No one at the stores or online could ever seem to figure out a fix... but I did! (Yay me! Uh-huh!) Sadly, its not a silver bullet for you, because this was the fix:
-Remove the SD card, reboot the phone, access the camera (which will then work), then shut down, re-insert SD card, turn back on
You should play around with:
-USB settings, such as MTP mode and developer settings USB debug = try turning them on and off, rebooting and camera attempts in between
-File Explorer utilities that could allow you to wipe or reformat the emulated SD portion
Best of luck,
bm
Click to expand...
Click to collapse
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.

poikilo said:
Im too scared to dismantle my tab. But if all else fails, i will try this and contact you. Thanks.
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.
Click to expand...
Click to collapse
You may have to be in the recovery to formati t.

poikilo said:
Problem is N10 doesnt have an SD card so i get that the fix wont work for me
I do not know which File Explorer allows me to reformat the emulated SD portion WITHOUT ROOT. If you happen to know anything please let me know. Thanks.
Click to expand...
Click to collapse
Yeah, that's the catch 22. When I had the problem on my Droid4 even 'factory reset' wouldn't fix it, but the SD card pull did.
You could root your phone, then use a root utility to do some formatting, then reinstall factory everything. It would be a lot of work, but it could all be done w/out physically opening the device. But - no guarantees it will fix it. Still, if its been a few days now and the camera STILL isn't back, a lot of work in reformatting etc would be worth it.
As for what root utility/explorer would be best, I am not the best guy to answer - but I suspect TWRP can accomplish this. Vets, care to chime in?

A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.

EniGmA1987 said:
A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.
Click to expand...
Click to collapse
It will only do a factory wipe and then that must be done from the recovery, upon unlocking it. I imagine locking up the bootloader may do the same as you would no longer be able to flash an operating system with it locked.
Sent from my Nexus 10 using XDA Premium HD app

EniGmA1987 said:
A simple unlocking and then relocking the bootloader will also do a complete wipe of the entire tablet. Just make sure you know how to reflash the factory image through fastboot otherwise you wont have an OS.
Click to expand...
Click to collapse
dibblebill said:
It will only do a factory wipe and then that must be done from the recovery, upon unlocking it. I imagine locking up the bootloader may do the same as you would no longer be able to flash an operating system with it locked.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think either of these are totally correct? I thought unlocking the boot loader warns you that you will lose your stuff but doesn't actually format userdata or cache on the N10.
All data on the phone is erased, i.e. both the applications' private data and the shared data that is accessible over USB, including photos and movies. Be sure to make a backup of any precious files you have before unlocking the bootloader.
On Nexus 10, after unlocking the bootloader, the internal storage is left unformatted and must be formatted with
$ fastboot format cache
$ fastboot format userdata
http://source.android.com/source/building-devices.html
Sent from my Nexus 4 using Tapatalk 4 Beta

Major update
Major Update
I downloaded this app called " All-In-One Toolbox" and did a maintenance update by deleting all my cache, history, app files, unused data and etc. After that i did a restart and voila, the camera app started working perfectly. ( Both the front and rear cameras ).
Im so happy, now i need not reset my tab and moreover that it is not a hardware issue.
Ill keep this thread open for a while for people with similar problem to comment.

Thanks
Thanks to all over hear for their suggestions.
Hope this thread helps all those who need it.

OS command delay

Hi,
I recently bought a refurbished Nexus 7 and after creating 4 users and installing some apps on them the tablet started to act strange... e.g. when I open settings and tap any of the category it doesn't open... I need to press back and wait 30 sec or more. The same happens with Google Play when I tap install. Also with all other apps (EXCEPT games). Note: The tablet isn't laggy. I don't know what to do Please help
Sent from my Nexus 7 using xda app-developers app

Up.
Please help !!!!! :crying: This thing is getting worse

Try wiping cache. In recovery preferably.

Okay. And that will erase the temporary files and cache files NOT user data, correct? :fingers-crossed:

You've tried rebooting?
Sent from my Nexus 7 using Tapatalk HD

Yes. The same thing happens. I tried to enter recovery mode to erase the cache but i got the message "no command" and the green Android laying on its back with a red triangle over it. Any opinions?
BTW, on boot a white open padlock appears. That means is rooted? I also installed Root Checker and said that i don't have root acces. If it's rooted then can I unroot? (bcz i'm thinking of a warranty replacement)

The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Sent from my Nexus 7 using Tapatalk 4 Beta

It probably means recovery wasn't installed at all.

SlowCobra96 said:
The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)

If you want it completely stock like factory new there is a thread sticky on how to do that as well.
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using Tapatalk 4 Beta

Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions

bv31top said:
Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions
Click to expand...
Click to collapse
The problem is that it appears there is no recovery installed thus the no command error. So you need to start with using the knowledge from the first thread I posted to get a recovery installed. From there you can try to wipe cache and dalvik cache then fix permissions. Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
EDIT: here is a guide for using adb and fast boot. http://forum.xda-developers.com/showthread.php?t=2225405
Sent from my Nexus 7 using Tapatalk 4 Beta

bv31top said:
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)
Click to expand...
Click to collapse
Gonna lag for sure then.
Rooting's best side effect is being able to tweak and streamline your device to make it as zippy as possible. Never will be as smooth running unrooted stock with no tweaks.
Sent from my SGH-T989D using xda app-developers app

I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
Click to expand...
Click to collapse
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?

bv31top said:
I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?
Click to expand...
Click to collapse
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Username invalid said:
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
Click to expand...
Click to collapse
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.

bv31top said:
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.
Click to expand...
Click to collapse
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".

Username invalid said:
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".
Click to expand...
Click to collapse
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?

bv31top said:
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?
Click to expand...
Click to collapse
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta

SlowCobra96 said:
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok... I think I will give it a try with the 2nd link.
And the cache problem?

[Q] Odin Flash Failure - Advice Please

I've tried to flash my GT-I9505 using Odin and it's failed (please see screen grab below).
I used "I9505XXUBMH1-PRE-ROOTED-ODEX-FULL" from post 5 of this thread
Code:
http://forum.xda-developers.com/showthread.php?t=2250824
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A few weeks ago, I tried "I9505XXUBMGA-PRE-ROOTED-ODEX-FULL" from the same thread and that failed and locked up my phone.
Which I had to pay to get the phone re-flashed properly.
(I've used the above successfully in the past).
Now, I'm in the same position again with a failed flash and probably paying to have it fixed again.
On the phone itself, the progress bar is only 2mm long. So if I switch it off, it will probably mess everything up.
What should I do now, while it's still connected to the PC and how can I successfully flash it in the future ?
Thank you.

What firmware's currently on the phone ?

MistahBungle said:
What firmware's currently on the phone ?
Click to expand...
Click to collapse
It's 4.2.2.
I've managed to get the phone "working" again, by using "I9505XXUAME2-PRE-ROOTED-KNOX".
Which is on the same thread.
But, since I got the phone working again, I can't get WiFi to switch on. Factory reseting via Settings doesn't fix it.
All the ROMs I downloading in the past (MF8, MGA and MH1) with "ODEX" in the title from the same thread don't work.
Odin (any version), says "Not Responding" when I try them and fails to update (using Win 8.1).

0-0-0 said:
It's 4.2.2.
I've managed to get the phone "working" again, by using "I9505XXUAME2-PRE-ROOTED-KNOX".
Which is on the same thread.
But, since I got the phone working again, I can't get WiFi to switch on. Factory reseting via Settings doesn't fix it.
All the ROMs I downloading in the past (MF8, MGA and MH1) with "ODEX" in the title from the same thread don't work.
Odin (any version), says "Not Responding" when I try them and fails to update (using Win 8.1).
Click to expand...
Click to collapse
Try clearing data , cache and dalvik cache from cwm and do a factory reset in cwm
sent from my GT-I9082 using xda app-developers app

asifcheer said:
Try clearing data , cache and dalvik cache from cwm and do a factory reset in cwm
sent from my GT-I9082 using xda app-developers app
Click to expand...
Click to collapse
Sorry, but I've no idea what you're talking about.
Simple instructions, please.
If it's for post 3: If it's the same as powering off the phone and starting it with Vol. up, Home and Power keys and resetting it that way.
That didn't for resetting the phone and the WiFi problem.
If it's for post 1, please ignore.

0-0-0 said:
Sorry, but I've no idea what you're talking about.
Simple instructions, please.
If it's for post 3: If it's the same as powering off the phone and starting it with Vol. up, Home and Power keys and resetting it that way.
That didn't for resetting the phone and the WiFi problem.
If it's for post 1, please ignore.
Click to expand...
Click to collapse
Edit:
Just to update.
I've lost all sound and I can't play any music or videos, even the Samsung material.

have u flashed a custom-recovery like cwm, Philz or TWRP?
If "clearing data , cache and dalvik cache" are new for you, plz read more about this all.

btmz said:
have u flashed a custom-recovery like cwm, Philz or TWRP?
If "clearing data , cache and dalvik cache" are new for you, plz read more about this all.
Click to expand...
Click to collapse
Thanks for the reply.
CWM
I've deleted the cache partition and wipe data/factory rest.
I can't find the "dalvik cache", I've seen a YT video about it, but it's in "advanced settings", which I don't have.
I'm rooted , SuperSU is installed.

delvik cache is under advance option of philz recovery
AND DO INSTALL THE LATEST PHILZ RECOVERY V 6.0.0.1

Clearing cache/Dalvik ain't going to fix your problem. Your sound/WiFi is busted due to that bootloader issue. You need to flash a 'WiFi fix' (non-HLOS modem) to match your current firmware/bootloader. Go to the modem thread (search; easily found) & find a non-HLOS modem to match your current firmware (and I don't mean 4.2.2 or whatever, I mean XXUA, etc, etc)

Thank you for the replies and help.
This is the WiFi Fix page http://d-h.st/users/DjeMBeY/?fld_id=16262#files
But, my current FW isn't listed (ME2), I've tried ME3 and MEA, I think those are the ones before and after ME2 (maybe wrong).
But, they don't work. I've tried them multiple times.
I'm not sure which others to try.
I'm going to pay and hopefully get it fixed today.
But, I'd still like to know how to fix it, for future use.
It will mess up again, when I root it. That is unless I just stick with "I9505XXUAME2-PRE-ROOTED-KNOX" and not try later updated ROMs which have worked in the past).

0-0-0 said:
0-0-0 said:
I've tried to flash my GT-I9505 using Odin and it's failed (please see screen grab below).
I used "I9505XXUBMH1-PRE-ROOTED-ODEX-FULL" from post 5 of this thread
Code:
http://forum.xda-developers.com/showthread.php?t=2250824
A few weeks ago, I tried "I9505XXUBMGA-PRE-ROOTED-ODEX-FULL" from the same thread and that failed and locked up my phone.
Which I had to pay to get the phone re-flashed properly.
(I've used the above successfully in the past).
Now, I'm in the same position again with a failed flash and probably paying to have it fixed again.
On the phone itself, the progress bar is only 2mm long. So if I switch it off, it will probably mess everything up.
What should I do now, while it's still connected to the PC and how can I successfully flash it in the future ?
Thank you.
Click to expand...
Click to collapse
Maybe this helps ya: HERE
Click to expand...
Click to collapse

Joku1981 said:
0-0-0 said:
Maybe this helps ya: HERE
Click to expand...
Click to collapse
Thank you.
My phone is currently at the shop, waiting to be fixed.
But, I'll try those.
Click to expand...
Click to collapse

0-0-0 said:
Joku1981 said:
Thank you.
My phone is currently at the shop, waiting to be fixed.
But, I'll try those.
Click to expand...
Click to collapse
pla report whats happend.
Click to expand...
Click to collapse

btmz said:
0-0-0 said:
pla report whats happend.
Click to expand...
Click to collapse
I'm due to collect the phone tomorrow, I received info from them today (Geek Squad at Carphone Warehouse, a company based in the UK), saying that it had been fixed.
I'm guessing they reflashed it. But no info was given on what they did.
After I get it back, I think I'll get rid of it and get a HTC One instead.
Using a custom pre rooted ROM, just seems to mess the phone up.
Hopefully there's another way for the HTC. Plus, I shouldn't need to worry about Knox.
Click to expand...
Click to collapse

http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
Download and flash modem for old bootloader and everything will be back to normal
Sent from my GT-I9505 using XDA Premium 4 mobile app

lazybeard said:
http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
Download and flash modem for old bootloader and everything will be back to normal
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you.

FlashFire for locked bootloader G4's

Hey guys, I just want to start a general discussion about using FlashFire on G4's with locked bootloaders. We have confirmation that we can install the latest Xposed with it. I've also created a standard backup using it (I have not tried restoring yet). I don't see what would prevent us from installing stock based roms with it.
Here's a screen shot of the backup it created. System, data, and boot all appear to the the correct sizes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS986 using Tapatalk

joshw0000 said:
Hey guys, I just want to start a general discussion about using FlashFire on G4's with locked bootloaders. We have confirmation that we can install the latest Xposed with it. I've also created a standard backup using it (I have not tried restoring yet). I don't see what would prevent us from installing stock based roms with it.
Here's a screen shot of the backup it created. System, data, and boot all appear to the the correct sizes.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Well I think the problem will be this, the app needs to be ran while android is running. If you are restoring the image and it is trying to replace system files it will probably crash at some point resulting in a boot loop. I haven't looked to see how this app works and maybe they have a way but I remember an app a few devs were working on to do the same and he was never able to get it working properly, it would just end up crashing and bootlooping/bricking. If they found a way around that this would be an incredible app!
You can try it out if you want but understand that you will probably softbrick. I highly recommend backing up your current system.img using the guide in the root method we have. That way you can put it in download mode and restore.

Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.

Flashfire boot in a minimalistic os to work there.
You can also use partition flasher to flash system.img, boot.img and so on. To flash system img is no problem with locked boot loader at all. But the device can not boot with twrp installed with an locked Bootloader. The signature is not correct, so softbrick.

player911 said:
Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.
Click to expand...
Click to collapse
You're a dev. lol. Anyways, we can flash stock roms with this. As long as it's running a stock kernel, it shouldn't be a problem. A modified kernel would most likely trigger secure boot error.

player911 said:
Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.
Click to expand...
Click to collapse
On the contrary. Coming from Samsung, this is how roms are installed on those devices with locked bootloaders. It flashes the system images perfectly working around the Locked boot loader. Just don't try to flash a bootloaders.

I was wondering how the s6 was running Roms. Was it an easy process? And why aren't they doing this on the G4?
Sent from my iPhone using Tapatalk

dlscott1111 said:
I was wondering how the s6 was running Roms. Was it an easy process? And why aren't they doing this on the G4?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You probably need a dev to build a package accordingly. Remove kernel and stuff like that. No one wants to be the tester lol. It would be nice to have a tot file just in case instead of that PR that is breaking cameras. (talking aT&T version of course)
I would LOVE to try out an international rom if they can get it to work with our devices but I have a feeling we will only be able to run rom on the same update we have? Maybe not as long as it works with the kernel

Just as an update...I used FlashFire to successfully restore my stock kernel. Granted, there were no modifications, but it worked.
Sent from my LGLS991 using XDA Free mobile app

The more I hear about flashfire the more I like.
Sent from my iPhone using Tapatalk

anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today

diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
I would totally do it but I don't want to have to factory wipe my device :-/ Just a pain to set it up again lol, I'm sure someone with more time on their hands can do it. Exciting, hope you can get the 815 working, there may be some changes needed to get everything to work
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
looks like you need to try to get this 10f update that fixes touch issues, if we could get that going we will be in paradise unless the fix was in the kernel

diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
Wait, would this image file work? http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427 worth a shot. I'm not sure if that is the full system or not

joshuadjohnson22 said:
I would totally do it but I don't want to have to factory wipe my device :-/ Just a pain to set it up again lol, I'm sure someone with more time on their hands can do it. Exciting, hope you can get the 815 working, there may be some changes needed to get everything to work
Click to expand...
Click to collapse
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.

CAG-man said:
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.
Click to expand...
Click to collapse
ok... I'll trust you. I have xposed installed so you will have to live with it if it made changes to system and the system.prop edit. I will want to send it directly to you first before I post it in case something stays lol PM me (it is backing up now btw)
---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------
CAG-man said:
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.
Click to expand...
Click to collapse
also I backed up my system.img file before I rooted it using the adb commands maybe this will be useful too? Let me know.
EDIT: if you do not have the data partition exact won't it just have force closes and boot loops? I just have horrible memories on my G3 where I accidentally wiped data and even after flashing new roms i had force closes.
EDIT AGAIN: Currently uploading, I will PM you and the other requester @diedemus the file here in a minute. keep me posted
EDIT LAST: PM Sent

grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2

diedemus said:
grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2
Click to expand...
Click to collapse
Hmm interesting, Fingers crossed, what can you do differently the second time?
Sent from my LG-H810 using XDA Forums Pro.

just an update to flashfire... i was able to do a full backup for now. the black screen is a bit scary at first, u dont know if it hangs or not u just have to be patient. now i want to try if xposed will really work. *crossfingers*
edit.. xposed framework works!! finally!
Sent from my LG-H815 using Tapatalk 2

diedemus said:
grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2
Click to expand...
Click to collapse
You're restoring this with FlashFire?
Sent from my VS986 using Tapatalk

joshw0000 said:
You're restoring this with FlashFire?
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
yeah, it seems to work but we don't know if we can manage flashing a different version of stock yet. He is testing that out. Would love to get someone with 10F to install the app and back up system, data (with a factory wipe) and boot using FlashFire and see if we can get the touchscreen fix.

Backup Apps?

So, I have the S5(Obviously) and I like to play around with which of the ROMS I like best, but my only problem is having to redownload all my Apps. I can backup my contacts and messages easily and restore them, but when I try to backup/restoring my apps, i'm at a loss.
I've tried titanium backup but when I do I move the backups to my External SD Card so they don't get wiped when I flash it with a new ROM, but when I move them back or anything, it just shows nothing. So basically is there something i'm missing or is there another way to backup my apps+appdata so i'm not spending forever trying to redownload some of my apps?
Veru much appreciated and thanks in advance.

Why are you moving your backups? Why not just back them up to your external card?

You are half way there by using titanium backup........
TiBu can make a zip of your backup that can be restored through CWM.......
Done it myself many times.....
http://i.imgur.com/rVnFwJM.jpg

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BUT.......If you choose to include app data in the backup zip, make sure the version of Android you are restoring it to, is the same as the version that was on your device when you made the backup.....
App data is *usually* OS version SPECIFIC......so it could be the case that the restored data won't 'play nice' with your new ROM if it's based on a different OS version......
Sent from my SM-G900F using Tapatalk

keithross39 said:
BUT.......If you choose to include app data in the backup zip, make sure the version of Android you are restoring it to, is the same as the version that was on your device when you made the backup.....
App data is *usually* OS version SPECIFIC......so it could be the case that the restored data won't 'play nice' with your new ROM if it's based on a different OS version......
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
This could work for me, but I don't have the donate version at the moment unfortunately. So is there another way to achieve this?
I didn't know this about android version but that's nice to know. i plan on sticking with Lolipop but i'll be sure to keep this in mind.

Sorry fella......
TiBu is the only app like this I've ever used....it's all I know.....
It was the first root level access app I purchased after rooting my first ever smartphone somewhere way back in the frozen past.....lol
For what it costs it is *the* single most useful app you'll ever buy......
http://i.imgur.com/rVnFwJM.jpg

Agreed, I bought it like 6 years ago, invaluable.

Check this Web page. .....
http://m.alternativeto.net/software/titanium-backup/
Might be something worth trying......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Sorry fella......
TiBu is the only app like this I've ever used....it's all I know.....
It was the first root level access app I purchased after rooting my first ever smartphone somewhere way back in the frozen past.....lol
For what it costs it is *the* single most useful app you'll ever buy......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
I don't doubt that, and I can probably buy it here next week or so after I gain some funds. SInce it the holidays I kinda went a little overboard on getting gifts. Haha
Ill probably do that though. Thanks for the help.
Just to make sure I got this right, so basically just open TiBu, backup al my aps and such, then run the "Create "update.zip", move it to me external SD card, flash the ROM, and afterwards just re-dl TiBu, and recover it usng the update.zip, correct?
EDIT: Thanks, i'll check out the site.

You don't use TiBu to 'flash' the zip......you use a custom recovery....
I've always used one version or another of CWM, I should think that you can use TWRP instead, but having not used that recovery, I can't say for certain.
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
You don't use TiBu to 'flash' the zip......you use a custom recovery....
I've always used one version or another of CWM, I should think that you can use TWRP instead, but having not used that recovery, I can't say for certain.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Oh no, sorry I knew that you didn't use TiBu to flash the zip. xD Sorry, I use FlashFire for that. Shoulda used more detail or explain better last time.
1. Create the Backup
2. Create the Update.zip
3. Backup whatever else I feel I need to on my phone
4. Move it all to my external SD Card
5. Flash the ROM with FlashFire
6. After new ROM is installed and etc, re-download TiBu
7. Then under one of the recovery options, get all the apps from the Update.zip
8. Restore whatever else I backedup onto my External SD card.
9. ??
10. Profit
(9 and 10, couldn't help myself. xD)

Lol.....
In essence, correct......
Point 7 though......
You don't touch the zip.....no extracting or anything like that necessary.....
Simply boot into (custom CWM or TWRP) recovery (this won't work with stock recovery.....or even CM recovery), locate the update zip and flash like you would a ROM zip......nothing else needed......
Edit.....TiBu will be included in the update zip....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Lol.....
In essence, correct......
Point 7 though......
You don't touch the zip.....no extracting or anything like that necessary.....
Simply boot into (custom CWM or TWRP) recovery (this won't work with stock recovery.....or even CM recovery), locate the update zip and flash like you would a ROM zip......nothing else needed......
Edit.....TiBu will be included in the update zip....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ooh ok, perfect, makes sense then. Thank you so much for the help.
Sent from my SM-G900V using Tapatalk

Exmix said:
Ooh ok, perfect, makes sense then. Thank you so much for the help.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
In my experience the update.zip hasn't worked for me in flashfire, might be better to just back up your apps to external, and then when you reflash it'll all still be there eon your external so long as you don't wipe it, then you boot and restore them in TiBu, that's what I do on my G900A since there's no recovery...
Sent from my SAMSUNG-SM-G900A using Tapatalk

Rakuu said:
In my experience the update.zip hasn't worked for me in flashfire, might be better to just back up your apps to external, and then when you reflash it'll all still be there eon your external so long as you don't wipe it, then you boot and restore them in TiBu, that's what I do on my G900A since there's no recovery...
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
At the moment FlashFire is my only option since I don't have a recovery either(Atleast I don't think so? If someone could tell me how to check to see if I do or not would be great)
But i'm gonna try on FlashFire at somepoint when I can get the Pro version of TiBu

Exmix said:
At the moment FlashFire is my only option since I don't have a recovery either(Atleast I don't think so? If someone could tell me how to check to see if I do or not would be great)
But i'm gonna try on FlashFire at somepoint when I can get the Pro version of TiBu
Click to expand...
Click to collapse
If you are currently running a custom ROM, then at the very least you have CM custom recovery....it is relatively easy to flash CWM or TWRP over the top of this, then you can use the newly installed recovery to flash the update zip......no need for Flashfire at all......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 03:21 AM ---------- Previous post was at 03:12 AM ----------
To check which recovery you have, simply power the device off, then press and hold power, volume up and home buttons simultaneously until the phone begins to boot. Release all the keys and you'll be in recovery......
The text at the top of the screen will tell you which recovery you have.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
If you are currently running a custom ROM, then at the very least you have CM custom recovery....it is relatively easy to flash CWM or TWRP over the top of this, then you can use the newly installed recovery to flash the update zip......no need for Flashfire at all......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 03:21 AM ---------- Previous post was at 03:12 AM ----------
To check which recovery you have, simply power the device off, then press and hold power, volume up and home buttons simultaneously until the phone begins to boot. Release all the keys and you'll be in recovery......
The text at the top of the screen will tell you which recovery you have.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ah ok. I only ever had to do this on my Nexus 7 tablet and that was Power+Vol Down and when I tried it on this it didn't work and I never really had to need to check, so when I do this I get this:
Code:
Android system recovery <3e>
LRX2IT.G900VVRU2BOG5
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADP
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CDC-code : VZW
Successfully applied multi-CSC.
So I should be able to apply the update.zip from this menu from what im understanding, but which option would I choose? :X I assume the "Apply update from external storage".
Also, thank you again so much for the help, you've made this a tremendous learning experience.

Exmix said:
Ah ok. I only ever had to do this on my Nexus 7 tablet and that was Power+Vol Down and when I tried it on this it didn't work and I never really had to need to check, so when I do this I get this:
Code:
Android system recovery <3e>
LRX2IT.G900VVRU2BOG5
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADP
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CDC-code : VZW
Successfully applied multi-CSC.
So I should be able to apply the update.zip from this menu from what im understanding, but which option would I choose? :X I assume the "Apply update from external storage".
Also, thank you again so much for the help, you've made this a tremendous learning experience.
Click to expand...
Click to collapse
Hey no problem fella......
The text at the top says 3e which means stock recovery.....i'm guessing you are currently running a Samsung firmware....
Unfortunately you cannot flash the update zip from stock recovery.....
It *has* to be a custom recovery which would normally come as part of a custom rom......
Although, a standalone custom recovery can also be flashed on top of a stock firmware......just got to make sure the recovery you flash is compatible with the firmware.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Hey no problem fella......
The text at the top says 3e which means stock recovery.....i'm guessing you are currently running a Samsung firmware....
Unfortunately you cannot flash the update zip from stock recovery.....
It *has* to be a custom recovery which would normally come as part of a custom rom......
Although, a standalone custom recovery can also be flashed on top of a stock firmware......just got to make sure the recovery you flash is compatible with the firmware.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Well i'm running the Phoenix ROM. So do you have any links or Tips on how to get a custom recovery onto mine so I can make this possible?
Like I had mentioned I really enjoy trying out new ROMs and wanna try more I just hate having to re-install all my APPs and such. =\
EDIT: I found this link here and it this seems liek it may work since i'm on the G900V version, but I just want a little confirmation on if this can work before I just jump right in. =P

I have a variant of the device that doesn't have a locked bootloader.....so (fortunately for me) I don't have to jump through the same loops as you do in order to modify my device.....
as a result, I'm not familiar with the processes needed for locked bootloader devices, I also cannot state what will or will not work with any certainty......
Having said that, I've been a member on here for some time, and whenever I've seen mention of Safe strap, it's generally been a positive comment.....speaking as someone who hasn't had to work around a locked bootloader, it would seem to be a good option, but if it were me, I'd be looking for some informed confirmation before I used it.......
Sorry I can't be any more help than that, but I really don't want to hand out advice that bricks somebody else's device.......
http://i.imgur.com/rVnFwJM.jpg