Hi there, my friend has a Moto G5 Plus they want to wipe entirely before discarding (or selling.) The power button on the phone doesn't work, but I was able to boot the phone up, so we could probably use the factory reset option from the settings menu.
The thing that concerns me is that sometimes certain wipe methods don't get every single file. Can someone point me to a method that will wipe absolutely everything and be unrecoverable?
In my experience typically adb or fastboot commands are the most thorough, whether it be flashing a full wipe factory image or something like that. The phone is recognized by fastboot and I assume I'll be able to get adb to see it also (Windows) so I should be able to run whatever commands are needed.
Can someone point me to the proper commands / method? I'm used to the Pixel 2 at this point, and it's been a long time since I used a Moto.
Well if you get into fastboot somehow then you can use fastboot erase userdata and fastboot erase cache. Get minimal adb it will be enough. Or from the backup and reset settings itself. I guess both of them do the same thing which is erasing the user data. Both of them will wipe the data partition completely so you can try either one of them.
Related
Hello guys, I am facing a major problem:
I have encrypted my N7 in the past, and now I replaced the faulty 3.34 bootloader with the 4.18 version. All went well, but for some reason my encryption password change so I can not go into recovery anymore. ( I have made sure that I did not mistype my old password )
Right now the only thing I have is Fastboot and a encrypted recovery. My question is: How to remove the encryption fully? I have tried:
- Re-locking and unlocking the bootloader (as it wypes all data) NO RESULT
Is there ANY way to remove the encryption from the fastboot menu?
Please and thank you
For anyone who is interested and facing the same problem: Flashing the stock rom via Fastboot worked.
Thread can be closed
SiemHermans said:
Is there ANY way to remove the encryption from the fastboot menu?
Click to expand...
Click to collapse
I would like to see a picture of a fastboot screen displaying any messages about encryption.
Are you sure you don't mean custom recovery or OS boot prompting about encryption passwords?
The OS concludes that the userdata partition is encrypted if it fails to mount it in the early boot - for any reason at all. This *could* be due to the fact that it actually was encrypted (as it apparently was in your case), but it could also be due to other failures such as a corrupted filesystem, hardware problems, etc.
BUT, if the tablet is otherwise working correctly, a "factory reset" (performed by a STOCK recovery, not a custom recovery) is supposed to be able to wipe & format userdata so that the "encryption" disappears. In this (successful) case the tablet would boot as if new; after all, the factory reset does not wipe whatever ROM was in the system partition.
The fact that you went through a lock/unlock step suggests that your bootloader (which version did the lock/unlock step?) should have already taken the correct action(s).
You can try this:
Code:
fastboot erase userdata
fastboot format userdata
to see if it makes any change in the behavior of the (custom?) recovery. (FYI the above procedure also fully wipes the SD card area, but I suppose you already know that)
I won't guarantee it will do anything, but it is worth a shot.
Also remember that if you have fastboot set up correctly you should be able to boot other recoveries without hard-flashing them to the tablet, e.g.
Code:
fastboot boot custom-recovery-image-file.img
You can use this if you suspect there is something wrong with your recovery, want to use a different version, etc.
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged?
Any response would be useful to me, thanks!
boeder9 said:
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged? Any response would be useful to me, thanks!
Click to expand...
Click to collapse
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
v12xke said:
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
Click to expand...
Click to collapse
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
boeder9 said:
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
Click to expand...
Click to collapse
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
v12xke said:
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these commands (espec system and userdata) erase my data and app data/personal files?
Ill try these and get back
boeder9 said:
Do these commands (espec system and userdata) erase my data and app data/personal files? Ill try these and get back
Click to expand...
Click to collapse
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
v12xke said:
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
Click to expand...
Click to collapse
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
boeder9 said:
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
Click to expand...
Click to collapse
System is a read only partition. Formatting it will not cause any data loss of yours, but will temporarily render the phone not bootable... BUT It can easily be restored via fastboot from any factory image. You just extract and flash the system image back to the system partition. Userdata is your personal data. When you format that partition your personal data will be gone. You did mention you had a FF backup so I'm guessing that was on the backup.
Yes on flashing TWRP. If after FLASHING twrp you cannot access Recovery, then try BOOTING recovery- fastboot boot recovery twrp.img
If you get to a point where nothing is working and you decide to format system and userdata and they complete successfully, you can flash a full Google image using flash-all.bat
Not sure about the LED's but just make sure your battery is close to fully charged. You didn't ever mention an battery issue, so there shouldn't be one. If in doubt hook the charger up and let it sit before proceeding.
@v12xke
Thank you for all your help. I left the phone on charge and let it bootloop for a good period of time and went out, came back and it was booted. I disabled the big clusters as suggested by @nicotinic in ElementalX and the device appears to be working fine aside from a little lag. I can live with that
Currently doing a little ADB pull, then will clear some space for a full nandroid backup!
Thanks a bunch to you both.
The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?
Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.
Phylum said:
The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?
Click to expand...
Click to collapse
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.
hawkswind1 said:
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.
Click to expand...
Click to collapse
Lol sounds good to me!
zameer hassan said:
Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.
Click to expand...
Click to collapse
Excellent excellent excellent advice - much appreciated.
You need to have USB debugging enabled btw to unlock your phone and issue those fastboot commands.
Hello guys,
I've got following problem:
For no particular reason my brothers OnePlus 5 get caught in a bootloop, but he has quite a lot of photos and other personal data on it. Unfortunately, he never unlocked the bootloader nor had USB-Debugging enabled. I still can enter the Recovery-Mode and the fastboot mode. Sadly, adb is of no use without the USB-Debugging enabled and fastboot is useless for transferring data, isn't it?
I couldn’t find anything helpful to retrieve the photos on the phone.
I thought about using the sideload function of the stock recovery mode of OnePlus to "repair" the system with a fresh update.
My second guess was to use "fastboot boot" to boot the TWRP-recovery or the stock rom that is currently on the phone, without flashing it. For both ways, however, you would need to have USB-Debugging enabled or the bootloader unlocked....
Do you have any other ideas, how to retrieve the data on the phone? I would really appreciate your help.
try to wipe cache in recovery mode or sideload,even reset system setting(apps with data lost)
do not format data(erase everything...)
billsz said:
try to wipe cache in recovery mode or sideload,even reset system setting(apps with data lost)
do not format data(erase everything...)
Click to expand...
Click to collapse
Thanks for the fast reply. I already tried wiping the cache without success. I would like to do the same with the Dalvik Cache but the stock Recovery seems not to support that.
I was a little scared of the "reset system settings" option, because I couldn't really find what it was doing in comparison to a factory reset. So you recon it will only wipe the system and the data and leaves the rest on the phone (photos, Documents, ...) untoched. That would be totally fine, I only care about the photos.
I tried the system settings reset, however nothing has changed. I guess that means the problem is a malfunctioning bootloader and the system is fine. (I wonder if that could have anything to do with the bend in the phone that is there since it is malfunctioning)
Is there any way to repair that with a locked bootloader or to access the data via the command line and fastboot?
DevilsThumb said:
I tried the system settings reset, however nothing has changed. I guess that means the problem is a malfunctioning bootloader and the system is fine. (I wonder if that could have anything to do with the bend in the phone that is there since it is malfunctioning)
Is there any way to repair that with a locked bootloader or to access the data via the command line and fastboot?
Click to expand...
Click to collapse
in recovery mode,there are three options for clean
1.clean cache(just caches)
2.reset system(clean system settings and apps)
3.erase everything including 1.2 and format user's data(like photos,docs etc.) as factory reset
so u reset the system(2),nothing changed,then u could sideload the system image to fix it and the system image shoud be the same version with ur phone
the sideload procedure is just flashing system part,user data should be safe.
billsz said:
in recovery mode,there are three options for clean
1.clean cache(just caches)
2.reset system(clean system settings and apps)
3.erase everything including 1.2 and format user's data(like photos,docs etc.) as factory reset
so u reset the system(2),nothing changed,then u could sideload the system image to fix it and the system image shoud be the same version with ur phone
the sideload procedure is just flashing system part,user data should be safe.
Click to expand...
Click to collapse
Thanks, I already tried sideload. I used the newest version of the system image, that should be on the phone as well. I thought it would actually work, the phone even said the update was successful. However in the command line the process was interuped at 84%. The phone was still caught in a bootloop. I also tried an older version which was interuped much earlier.
Hi everyone, my case is very simple.
I need to wipe datas my samsung J7 in a recovery mode using adb, a command for that is "adb shell recovery --wipe_data".
The thing is I don't want it to reboot immediately, because I need to change a bit in data files using adb.
As far as I know, other devices have a fastboot mode which you can wipe data there and go back to a recovery mode to change data files.
Since Samsung devices do not support the fastboot mode, I can't achieve that.
So now I am stuck.
Are there any suggestions how to deal with my case?
Or do I need to buy other brand phones which support a fastboot mode?
It may be possible to do this via a custom recovery, but the factory recovery will automatically reboot after a data wipe, and there isn't much that can be done about that.
V0latyle said:
It may be possible to do this via a custom recovery, but the factory recovery will automatically reboot after a data wipe, and there isn't much that can be done about that.
Click to expand...
Click to collapse
Okay, thanks for answering, maybe I will try other devices to look up some workaround methods.