I recently tried to re-install root on my device. I used the link below to root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Everything worked fine, my phone rebooted normally, said it was rooted and I went on my day. Later that day I rebooted my phone and now it wont start up. It just pauses at the verizon logo and never gets past that. I can get into the default LG recovery, but I don't know how much I can really do there.
I really need to recover some of my files, contacts, etc. If I could just fix the issue without losing data that would be better, but at the very least I need to save some files from my phone. Any ideas?
EDIT: I have done some research and found I can fix my issue if I'm able to get my phone to be recognized by my computer. For some reason the MTP USB Device driver fails the install...
Have you gotten into recovery and tried to wipe the cache?
If you can get into the stock recovery you should be able to choose wipe cache and it will take you to twrp if you have it flashed onto your phone. From there you can restore or wipe the cache and see if that helps.
Exact problem
My s3 is soft bricked and i need all my information back, would pay for help
Majnuel said:
My s3 is soft bricked and i need all my information back, would pay for help
Click to expand...
Click to collapse
Your hit there's no way to recover information from a soft/hard brick requires a factory flash
Related
Hello,
If anyone could help me get my phone back into a functioning state, I would very much appreciate it! I have been playing around with the Cyanogenmod 10 nightlys. All was going well until I decided to try encryption. It encrypted the phone okay, but I decided to format the phone and get it back to an unencrypted state, except it wouldn't allow me to factory reset. The button to start the reset did nothing except reboot the phone a few minutes after pressing it.
No problem, I thought, I made a nandroid backup before I started playing with ROMs, I'll just restore that, except that didn't work because CWM couldn't mount the encrypted volumes. So, I copied the CWM backups to an SD card using root explorer, and tried to restore from there. It gave me an error advising it couldn't mount/format /system. So, I rebooted, only to get stuck on the Samsung boot logo.
I can still get into download mode though. so I tried flashing the stock firmware with Odin. Odin reported the software flashed succesfully, and the phone boots now with the stock animation so presumably it did work, but it still asks for the encryption key. I put in the key I used originally but it rejects it.
I don't know what else to do to restore my phone to a stock state.
This is my first Android phone and I was just playing around out of curiosity, so pleas excuse any noob errors I may have made along the way. I shall be sure to learn from them.
Please tell me I can get my phone back to the original state!
s0mmie said:
*snip*
Click to expand...
Click to collapse
It seems I have managed to get back to a working state by using the Android recovery menu. Phew. I shall not be messing with encryption again. All part of the learning curve though, I suppose!
Hi Guys,
I've been a long time lurker but I have finally registered to ask an important question (well to me anyway)
I fixed one of my friends' LCD and got it working. It turned on and went to the lock screen, all buttons worked but I could not do anything else as there was a password. So today I returned the phone back to him and he about half an hour later he told me he could not get pass the "S" boot logo.
I don't think that I had broken anything while fixing the phone as it booted up successfully multiple times and it is a genuine lcd. So what do you guys think? From previous testing I know that I can get into recovery and download mode so do you think I should factory reset the phone? Will that fix it? From experience I know that some phones are sometimes problematic and require a factory reset after even a general repair. However, he does not have a backup of any of the data and I don't think he would like to lose any data. Is there anyway to get pass this?
I also don't know what firmware it is on nor if it is rooted.
Sounds like a factory reset seems to be the way to go.
Before you reset though, I'd recommend flashing a custom recovery to create a back up of all the data, or just the /data partition. If the factory reset fixes the problem then you can either flash parts of the back up one by one and test for boot loops, or you can search for a back up explorer and just copy out what you need.
amcgavin said:
Sounds like a factory reset seems to be the way to go.
Before you reset though, I'd recommend flashing a custom recovery to create a back up of all the data, or just the /data partition. If the factory reset fixes the problem then you can either flash parts of the back up one by one and test for boot loops, or you can search for a back up explorer and just copy out what you need.
Click to expand...
Click to collapse
Good thinking..
But if the device was not rooted, how would he root (and install a custom recovery) without knowing what firmware it is on?
@OP:
I do not know what caused the issue, but when your phone is stuck at the boot logo, the first thing to try is a factory reset.
immortalneo said:
Good thinking..
But if the device was not rooted, how would he root (and install a custom recovery) without knowing what firmware it is on?
Click to expand...
Click to collapse
Is it necessary to know what the firmware is? When rooting my s2 I installed the custom recovery through odin first, and then installed root through through there. No need to know the firmware!
amcgavin said:
Is it necessary to know what the firmware is? When rooting my s2 I installed the custom recovery through odin first, and then installed root through through there. No need to know the firmware!
Click to expand...
Click to collapse
Then you might wanna try that first.
"To err is human, to forgive is divine."
Sent from my SGS II
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
gbswales said:
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
Click to expand...
Click to collapse
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
As you are going to sell it then follow the guide in general forum, stickies to return to stock. Factory reset before you boot the fresh firmware.
further
VerlyAnanda said:
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
Click to expand...
Click to collapse
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
formatting cache solved the problem!
gbswales said:
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
Click to expand...
Click to collapse
I read someone had the same problem and just cleared the cache - so went into Team Win wiped cache and it restarted - guess I was looking for a complicated solution to something simple!
So my wife broke her phone. (A car ran over it) .
As you can imagine the phone is pretty messed up. Originaly the phone still worked(for a few weeks) and then she bought a new phone and left that one.
Now a few weeks later i try to turn it on to take the pictures off and it boots into the bootloader and thats where i am in need of your help. If there a way for me to get the pictures off of this phone?
You're most likely out of luck. Without booting into the OS, the only alternate way you would have a chance is if had a custom recovery. You don't, unfortunately, as the bootloader is obviously locked. It would have to be unlocked before you could install the recovery, but on HTCs, that process wipes the phone. Only thing you could try would be to boot to the stock recovery and wipe cache. Works in some cases, but if you wipe anything else via factory data reset, it'd wipe everything as well. Sorry. It'd basically take some NSA level stuff to be able to extract anything else in this state, if at all.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.