Database Info

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.

Have you tried booting into recovery?

(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

SM-G930F Maintenance Boot?

Hi all,
Just wondering if you Android pro's can tell me whether the G930F (Australian) can boot into maintenance mode?
My girlfriend bought one new on the way to the airport for her dream holiday in the USA mainly for the camera, then promptly forgot the swipe pass for the secure startup when she arrived home. USB debug is off, so I'm looking to get it back on. Got no problems with the FRP, she knows all the details for that, but it's just that the phone won't power on and connect to the network so we can do an account recovery. Or, at least get to a point where we can pull the photos off and then just do a hard reset.
If it's a no go on maintenance boot, would flashing the stock ROM back on get us past the swipe and at least to a point where we can actually recover the account from Google?
Just to be clear - the phone boots past the Samsung logo and then stays in "To start up your device, draw your pattern." and the option to go to an emergency call. We cant call the phone at this point, it just goes straight to voicemail.
Thanks heaps!

The 930F is the international model, Australia has no specific firmware or hardware differences so shouldn't have any reason not to be able to.
It sounds like you have the set to have the pattern required to start the device as opposed to just unlock it, and I'm not sure how early it kicks in preventing boot modes.
If I recall correct boot to recovery is vol up + home + power, boot to maintenance is vol up + power, and boot to download is vol down + home + power
Couldn't tell you if recovery or maintenance will let you pull data.
A factory reset within recovery might get past the pattern lock, but will wipe your photos.
A stock firmware flash in Odin should do it if recovery doesn't work, but also will wipe your photos.

Ah, I see. I appear to be able to get into Recovery and Download boots, but not maintenance. I'd seen that once you get into maintenance, you can turn on USB debugging from there, and I'd be all sorted. Hmmm.
That's a pity about the stock ROM flash, I thought that might be my best bet after maintenance boot.

Maintenance might be a snapdragon thing, googling it I can only see people doing it on the US model.

Oh right. Could I do anything like in this article -
Google "Physical Imaging Of A Samsung Galaxy S7 Smartphone Running Android 7.0" (sorry, I can't post outside links yet!)
- down to step 4? Is there an appropriate boot image available for the G930F?
Thanks heaps for the help so far!

Should be, every ROM zip I've seen has one in them. Not sure where you could get a stand alone stock one.

Ok, cool. Would the one found in this thread -
"ENGBOOT for S7 and S7 Edge (Qualcomm/Exynos) (Untested) (Still Seems Legit)"
- on these forums be ok? There's a file in the download labelled G930F_XXE1APBG_ENGROOT.tar (after extracting the .7z) that appears to be standalone. Is that what I'm after?
For reference, in Recovery boot, it tells me that the current PDA is G930FXXS1DQF6, and from that I can find that the CSC is G930FXSA1DQEF.

So she can't remember the pattern to unlock it? Or does it not boot properly despite entering the correct pattern? The S7 comes encrypted by default and the pattern is the key. No data is actually usable at the point it displays the pattern screen with the black background(because it can't actually access the wallpaper yet). If you can't get the pattern right all data currently on the device apart from the external SD(unless it's encrypted too) is lost It's a security feature, the only other way is a factory reset.

Yeah, black background is where we're at, and yeah, can't remember the pattern. So there's no way to get past that at all? Not even flashing the boot image?
Hmmm. Is there any way to reset the amount of attempts? We can at least keep trying different patterns that way.

JamesMudd said:
Yeah, black background is where we're at, and yeah, can't remember the pattern. So there's no way to get past that at all? Not even flashing the boot image?
Hmmm. Is there any way to reset the amount of attempts? We can at least keep trying different patterns that way.
Click to expand...
Click to collapse
NOTE: This is based on what I know. If anybody else has any ideas please don't hesitate to share!
Does it let you enter a backup password? She might have some ideas there?
Your best bet would maybe be a firmware reflash, but that's a very slim chance. So try that first(Remember to use HOME_CSC!). You can try flashing the boot image but beware, if the phone is full stock then the encryption system has some self-defence mechanisms that can permanently lock the data if unauthorized firmware is detected(or anything else suspicious like resetting the attempts). It technically *shouldn't* disable secure startup though; Remember, the whole point of encryption is to make it physically impossible to access data without the key, so it wouldn't be doing its job if you could just disable it at will. Samsung is also pretty anal about security these days.
Edit: Does she have a Samsung account? It might have backed the photos up already.

Boot options on bootloader screen

I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!

Dead_Dude said:
I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!
Click to expand...
Click to collapse
This is NOT the Q&A thread

fubugang said:
This is NOT the Q&A thread
Click to expand...
Click to collapse
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.

Dead_Dude said:
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.
Click to expand...
Click to collapse
As per the thread title: This thread is for development purposes only. All questions should should be asked in the Q&A thread

I dunno but I can tell you the SUPRA from cricket does not support bootloader unlock or root right now, and probably never will, I bought one but i will probably sell it off or gift it and buy the Power or G7 Plus with the money typically with moto you just go to the motorola bootloader unlock page enter your fastboot and type oem get_unlock_code or whatever it gives you a string you put it together and paste that in the moto bootloader page and they provide an unlocked bootloader boot.img you do get the code however when you put it in it gives you message that the phone cannot be unlocked thanks alot cricket, and Att I dont mind your service here but I want to be able to flash custom roms so I will just order a moto from swappa or straight from moto so i can do what I want with the phone, considering these are prepaid and you buy them out right it should not even be legal to keep the locked really, wish some attorney that had this stuff as a hobby would help us out it is flat out wrong to tell me I cannot unlock my bootloader its not like I owe anything on the phone thru cricket in the first place its paid for in full.

Question Z flip 3 bootloop

The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer

Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.

I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.

Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left

twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer

There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.

I see, alright, thanks a lot, I'll consider resetting it

It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.

Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )

ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.

Samsung J7 Prime (2017) SM-G610Y Boot Looping Problem

Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.

You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.

Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!

A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.

Try restarting by pressing home, power and volume up all at once.

Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.