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.
Related
Somehow I have managed a binary count of 4, and I need to reset it to 0. For some reason my phone gets to the screen where it says "4G lte" with all of the rings expanding and stops, it doesn't boot any further, it just sits at that screen forever in a loop (I feel like this could be due to the binary count?). But anyways, since I don't have access to my phone I cannot use Triangle Away, so I was wondering if someone could please tell me how to reset it from the computer or in download mode. Thanks!
VerizonS3 said:
Somehow I have managed a binary count of 4, and I need to reset it to 0. For some reason my phone gets to the screen where it says "4G lte" with all of the rings expanding and stops, it doesn't boot any further, it just sits at that screen forever in a loop (I feel like this could be due to the binary count?). But anyways, since I don't have access to my phone I cannot use Triangle Away, so I was wondering if someone could please tell me how to reset it from the computer or in download mode. Thanks!
Click to expand...
Click to collapse
While I can't answer your specific questions in regard to the count..
It might be worth it to hook up to a PC with the USB cable and check out the logcat. Typically in a boot loop it'll be trying to do the same steps (and failing..) over and over again. Might be some very useful information there and the problem could be totally unrelated to what you suspect it is.
Another super ez option would be to simply restore your last known working nandroid backup..
CrustyMcLovin said:
While I can't answer your specific questions in regard to the count..
It might be worth it to hook up to a PC with the USB cable and check out the logcat. Typically in a boot loop it'll be trying to do the same steps (and failing..) over and over again. Might be some very useful information there and the problem could be totally unrelated to what you suspect it is.
Another super ez option would be to simply restore your last known working nandroid backup..
Click to expand...
Click to collapse
Unfortunately I do not know how to use the logcat what-so-ever, so I wouldn't know what to look for, the loop only begins when it gets to the verizon rings, it's not restart the whole bootup, it just gets stuck at the last boot animation and never displays the homescreen, if I am making sense
As for restoring the most recent nandroid, my phone for some reason will also not boot into recovery mode, I can hold Volume Up+Power+Home to attempt it and it will show the Samsung Screen and the "Recovery Booting..." in the top corner, but the recovery mode never actually comes up, I just have to let go and then it restarts itself normally and gets up to the Verizon animation and loops there
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.
Hi all
My missus dropped her old s7+ edge years ago now and while the screen isnt cracked or anything whatever she did it just caught it at the wrong angle or something. The screen kinda works but its all messed up with very faint boot logos and stuff - I cant really see the android recovery comming up so cant select wipe/factory reset for example
Anyway its never been able to boot since. I was going to throw it out as not worth repairing. But Ive just connected to windows and the device is showing up in Device Manager
Just wondering if there was some kind of windows app to wipe the phone or something
Or am I best putting a hammer to it?
Thanks
kiteboy said:
Hi all
My missus dropped her old s7+ edge years ago now and while the screen isnt cracked or anything whatever she did it just caught it at the wrong angle or something. The screen kinda works but its all messed up with very faint boot logos and stuff - I cant really see the android recovery comming up so cant select wipe/factory reset for example
Anyway its never been able to boot since. I was going to throw it out as not worth repairing. But Ive just connected to windows and the device is showing up in Device Manager
Just wondering if there was some kind of windows app to wipe the phone or something
Or am I best putting a hammer to it?
Thanks
Click to expand...
Click to collapse
If USB debugging wasn't enabled in the device's system settings and if you can't unlock the lock screen, you won't be able to use a PC to wipe the device.
If you can find a screenshot of what the stock recovery screen looks like on your specific model number of S7+ edge, you can use the screenshot to see the order of the options in your stock recovery and count how far down the list the factory reset option is. Boot into your stock recovery, you may not see it but it is probably still booting into it, then you can use the volume up/down button to go up or down the list. If factory reset is the second option, in your screenshot, press volume down once to select it then press the power button to initiate the wipe, if factory reset is the 3rd option, press volume down twice then press power, if it is 4th on the list, press volume down three times then press power, and so on. If you find the correct screenshot to guide you and if you use the buttons to correctly select the factory reset option this should wipe your device whether you can see what is going on or not.
Or
If you can boot into download mode, you can flash the newest version of your stock firmware for your specific model number of S7+ Edge, there should be two CSC files in your firmware, when you flash the firmware files, use the CSC file that does not have Home in its name, it will wipe the device when you flash it, if you use the Home CSC, it will not wipe the device.
So first of all I have a S5 neo which I have rooted. I wanted to achieve that there is no way to access the data on the phone without physical access to it.
So I have everything with Wifi, Bluetooth, GPS, LTE, UMTS or GSM unsoldered from the motherboard. It worked except for the problem that the phone only started in safe mode so I could not use my own apps.
First I updated Lineageos from the official 17.1 to the unofficial version 18.1 with this ROM https://forum.xda-developers.com/t/...1-0-0_r49-lineageos-18-1-28-nov-2021.4292703/ .
Which in itself worked but it still starts in safe mode even when setting up.
Then I had the idea to uninstall system apps via TWRP. Since probably because of the missing components a system app throws errors why it goes into safe mode. So in TWRP via advanced -> file manage in system gone and have thought in my infinite wisdom, since I do not know if it repairt I remove all apps, if it solves my problem I can narrow it down later which app exactly. So first priv app and app folder completely solved.
Now to my current point of view. It does not boot into Lineageos (who could have imagined that XD). So it comes as far as in the boot animation (green curved line where always a circle moves from right to left).
When I try to boot in TWRP it just loops the Samsung logo and then when I release the buttons it tries to boot back into Lineageos.
When I try to boot into download mode it works up to the point where it says warning and I have to press volume up to advance or volume down to cancel. Whereas in here all at once the volume dasten do nothing more. and no the keys are not broken because otherwise I would not have come into the menu.
USB debugging and the like is of course not aktieviert, because I just installed a new ROM.
I don't intend to do anything illegal with the phone, as you might think, it's just a backup idea that I'm implementing for fun.
Does anyone have any idea what I can do?
My only idea right now would be to solder the EMMC memory from another mainboard to my current mainboard.
Chigoma333 said:
So first of all I have a S5 neo which I have rooted. I wanted to achieve that there is no way to access the data on the phone without physical access to it.
So I have everything with Wifi, Bluetooth, GPS, LTE, UMTS or GSM unsoldered from the motherboard. It worked except for the problem that the phone only started in safe mode so I could not use my own apps.
First I updated Lineageos from the official 17.1 to the unofficial version 18.1 with this ROM https://forum.xda-developers.com/t/...1-0-0_r49-lineageos-18-1-28-nov-2021.4292703/ .
Which in itself worked but it still starts in safe mode even when setting up.
Then I had the idea to uninstall system apps via TWRP. Since probably because of the missing components a system app throws errors why it goes into safe mode. So in TWRP via advanced -> file manage in system gone and have thought in my infinite wisdom, since I do not know if it repairt I remove all apps, if it solves my problem I can narrow it down later which app exactly. So first priv app and app folder completely solved.
Now to my current point of view. It does not boot into Lineageos (who could have imagined that XD). So it comes as far as in the boot animation (green curved line where always a circle moves from right to left).
When I try to boot in TWRP it just loops the Samsung logo and then when I release the buttons it tries to boot back into Lineageos.
When I try to boot into download mode it works up to the point where it says warning and I have to press volume up to advance or volume down to cancel. Whereas in here all at once the volume dasten do nothing more. and no the keys are not broken because otherwise I would not have come into the menu.
USB debugging and the like is of course not aktieviert, because I just installed a new ROM.
I don't intend to do anything illegal with the phone, as you might think, it's just a backup idea that I'm implementing for fun.
Does anyone have any idea what I can do?
My only idea right now would be to solder the EMMC memory from another mainboard to my current mainboard.
Click to expand...
Click to collapse
I would throw it away at this point, it isn't worth the money, the time or the effort.
Find something else to tinker with, just don't destroy it the way you did this device.
Why take the approach on unsoldering?
Etherway.... , yes just throwing it away at this point is the best thing
FKX1997 said:
Why take the approach on unsoldering?
Etherway.... , yes just throwing it away at this point is the best thing
Click to expand...
Click to collapse
also if the data is confidential, try drilling through the EMMC
I got it working again with the help of a Samsung USB jig.
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.