A few months ago while I was visiting family my cousin decided to lock me out of my phone by putting in the wrong pattern 30 times. I was then asked to provide my Gmail account and password to unlock it. However, when I input my Gmail account and password it says "Invalid username or password". I wasn't able to do much searching there since their internet was very unstable and rarely worked, so now that I'm back I checked and the Gmail account and password that I entered are correct, it just happens to not work on my phone. My WiFi and data off too, so that could be the reason why it's not verifying it.
When I turn off my phone and turn it back on while pressing the volume up button it does say that it's on fastboot mode and that it's unlocked. Not sure if there's any other information that I can provide that will be helpful. I really want to access my phone again without having to factory reset it since I've a lot of pictures that I haven't saved and I don't want to lose all my contacts again (not sure when I last backed up my phone or if I have ever backed it up).
Try this.
http://forum.xda-developers.com/showthread.php?t=1800799
Thank you for the link. I tried both methods posted on there but it didn't work. when I typed adb shell it would say device not found. I believe my USB debugging is turned off.
If you have a custom recovery then you can try the same commands.
If you have an unlocked bootloader, then flash a custom recovery and give it a go.
Sent from my Nexus S using Tapatalk
I went into bootloader mode and selected recovery.. but that didn't do much. it just showed an android with a red triangle and an exclamation mark inside of it. Then it went back to asking for a gmail account and password.
I'm trying to flash a custom recovery but its still not working. I was using this site for guidance http://forum.xda-developers.com/nexus-s/general/nexus-s-guide-unlock-bootloader-root-t2034264 but in the "early necessary requirements" it says that USB debugging should be enabled.. which it isn't for me.
I tried using all 3 commands but all I get is "waiting for device" and nothing happens after that.
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
- When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.
Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data
same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Currently I am not able to switch on my phone !!!
AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!
Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.
The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.
So, I have a really really odd situation. I have an MDM on my phone, MASS360. I typed in the phone's password wrong too many times, and it locked me out of the phone. The phone says to reach out to the IT Department to fix it. I reached out to the IT Department, but they weren't able to fix it. So I have a bit of a conundrum. OEM Unlock is off, and so is USB debugging. I cant unlock the phone to turn them on. I also can't factory reset (even from the recovery menu) because of the MDM's policy. Is there a way to Sideload a file or something to factory reset the phone? Any other ways that I can factory reset the phone? I'd also be fine with installing another ROM on the phone if its possible.
Phone info: Samsung Galaxy J327U
jordanbw1 said:
So, I have a really really odd situation. I have an MDM on my phone, MASS360. I typed in the phone's password wrong too many times, and it locked me out of the phone. The phone says to reach out to the IT Department to fix it. I reached out to the IT Department, but they weren't able to fix it. So I have a bit of a conundrum. OEM Unlock is off, and so is USB debugging. I cant unlock the phone to turn them on. I also can't factory reset (even from the recovery menu) because of the MDM's policy. Is there a way to Sideload a file or something to factory reset the phone? Any other ways that I can factory reset the phone? I'd also be fine with installing another ROM on the phone if its possible.
Phone info: Samsung Galaxy J327U
Click to expand...
Click to collapse
flash factory firmware in Odin
Youdoofus said:
flash factory firmware in Odin
Click to expand...
Click to collapse
Thanks so much! I didn't realize you could flash stock firmware without OEM unlock.
jordanbw1 said:
Thanks so much! I didn't realize you could flash stock firmware without OEM unlock.
Click to expand...
Click to collapse
you bet! Welcome to XDA btw!
I have almost exactly the same issue. I was tinkering with MDM 'force PIN' and then stupidly removed the device (Samsung SM -T505) from MDM (Scalefusion) before disabling the PIN lock. Now the PIN is not recognised, I can't get into the the home screen at all because of the PIN, the recovery menu is missing wipe data/factory reset and (of course) USB debugging is NOT enabled. If I try to flash a stock ROM, ODIN reports 'SetupConnection..' but eventually times out without sending anything. ADB devices list is empty. However, I can get into ADB sideload from the recovery menu and ADB devices (on the PC) then shows a device in sideload mode. I tried loading the Samsung stock ZIP, but the tablet reported signing errors and quit.
Is it possible to sideload a stock rom? Or a 'force factory reset' zip file of some sort? Or perhaps from SD card?Choosing the bootloader menu shows 'Fasboot Mode' in red with device state - locked (also in red.
I m not trying to crack an ebay cheepy or anything else (I have the receipt to prove purchase), but I REALLY need to get back into this darned thing! I suppose at least one can say that the Knox system works well!.
Any offerings, please?!!
/AJC
Mk...yesterday I started a factory reset cuz I'm trading my phone back to google.
After starting the reset from inside the os, I set the phone and when I came back it was on the recovery screen where it's in red font
saying it's unable to load may need to factory reset. ok, well I go ahead with the reset and it goes to the white google screen
then reboots, and after the bootloader warning screen it ends up back in recovery asking to do a factory wipe again.
Tried connecting to pc but 'adb devices' fails to find the phone. If I can't connect how do I flash/fix it??
The phone is rooted with magisk 25.5 on stock A12.1 rom.
Just want to flash it to current and the re-lock the bootloader
so I can send it to google for my $300 trade-in towards my 6a.
Atm, I can't even power down. Holding pwr button doesn't work
and when I get to the bootloader (pwr+vol.dn) and select
'power off'...it just keep tryin' to boot and ends up back at the recovery
screen prompt.
I've d/led a fresh factory image to flash but I dunno how to establish
a connection with the pc. I know I should know how... very noobish of me...lol
Got to fasboot, when I connect to pc I hear the windows connect sound but when I try 'adb devices' I get nothing. Back to google I go.
Mk...I got it.
During the flash-all.bat it kept dropping the ball losing 'userspace' after a couple of reboots. So I figured I give the online android flash tool a shot...worked great and re-locked the bootloader too!
Problem solved...can a mod delete this thread...it's embarrassing.