So recently I tried completely wiping my cache from the recovery mode, but when I restarted the phone and held the power and volume up buttons, instead of entering recovery mode the phone just vibrated and booted normally. It then showed this message.
[PDP] Back-up : fail setup-wizard [ FINISH ]
Does anyone know what I can do to fix this ? I've already tried several times.
Erskinelink1 said:
So recently I tried completely wiping my cache from the recovery mode, but when I restarted the phone and held the power and volume up buttons, instead of entering recovery mode the phone just vibrated and booted normally. It then showed this message.
[PDP] Back-up : fail setup-wizard [ FINISH ]
Does anyone know what I can do to fix this ? I've already tried several times.
Click to expand...
Click to collapse
did you fix this? i have exactly same proble, i create custom AP from stock with magisk latest i wipe all partitions but when i flash it over odin i get same error
No, i still cant reset it. This is the feedback i get each time i try to hard tweet it
[PDP] Back-up : fail setup-wizard [ FINISH ]
No, i still cant hard reset it. This is the feedback [PDP] Back-up : fail setup-wizard [ FINISH ]
i think if you need a rooted phone just install lineageos is much faster and debloated than stock, i change my stock today to lineage and is amazing
when you change to lineageos install auroraoss store amazing app like google store
you can root lineageos so easy in recovery twrp install magisk zip thats all no problems at all
IF you want more options to play jest follow these post
[Guide] Running Linux on Android with 3D Acceleration / OpenGL (Root Required)
All credits go to: Hentacler for making Sparkle Meefik for making Linux Deploy Now on to the tutorial! Requirements: Sparkle Linux Deploy Termux Now you have all those apps installed lets continue Open Termux then enter: su Once in root...
forum.xda-developers.com
That message what you have i magisk recovery script.
Magisk is installed on recovery partition and when you hold that button when phone power on magisk installing to the phone thats why vibrate
If you wanna go to recovery mode just hold same button combo before phone start logo shows and keep long as possible and you must have connected usb cable to the pc if you press button combo when logo is already on the phone then magisk start installing and thats why its vibrate
When you will hard reset i think you gonna lose magisk and root.
That message what you have should say "backup success" i think magisk is broken and for me is not working too
When you will hard reset i think you gonna lose magisk and root.
That message what you have should say "backup success" i think magisk is broken
Erskinelink1 said:
No, i still cant hard reset it. This is the feedback [PDP] Back-up : fail setup-wizard [ FINISH ]
Click to expand...
Click to collapse
Do you fix this?
I have had that same issue. Unfortunately my partner's phone had a keylock on ii so these are the problems I had to face.
Draw the pattern several times but it never gave me the option to 'use a google account' so it carried on until I had to wait 65 minutes before drawing another pattern. Still no google account option.
I'd swipe down, select the wifi to get it to connect and it wouldn't let me look for my wifi to put a code in.
After a search, it gave me some software that I can download off Tenorshare so I downloaded it and tried which put me to the next problem, I couldn't get into the root menu to factory reset the phone and the phone wouldn't allow me to get into the diagnostic screen when I type on the *#09#*, I think the code is but you can get in via clicking the emergency call option. I'd volume up and power, it buzzed twice and still continued to the main samsung screen. The software from Tenorshare couldn't do much with it ie remove the google account but here's what else I did. I remembered that I used to upgrade firmware on samsung mobile phones via this website so I downloaded the Odin software, found the correct firmware from sammobile.com and that came up with something surprising. As much as I couldn't get into the root menu, I just believe that it's missing or corrupted,
so I connected the phone to the PC using the USB,
fired up Odin, Odin didn't show anything in the log but it after restarting the phone and pressing volume up and power, it buzzed twice and it went into a blue download screen and sat there. I thought, heyyyy this screen is usable.
The download for the firmware was complete and I unzipped it to it's 5 components, USERDATA, BL, AL and two others,
I had put the seperate files into the Odin software and clicked the start button. It uploaded the firmware successfully and restarted the phone so I did the volume up and power (I think I did it or the phone went into the root menu itself).
From there, I factory reset the phone, rebooted and it still asked for the draw pattern but I could set up the wifi, so since I was doing this late, I couldn't be bothered to phone the partner up to get all the email, questions etc.
So I rebooted the phone, went into the root and cleared the cache; this didn't really help at all because the draw pattern came up and when I used my gmail account; the phone wouldn't change the owner.
So I went back to the Tenorshare software and used the google account removal option and that worked;
The is completely clean and I can give it back to her, I did some google updates, galaxy store updates and it works fine. So just need to give it back.
Related
I have Samsung Galaxy S III GT-I9300 with 4.3 stock ROM, rooted with CF-AutoRoot/SuperSU and Recovery replaced by ClockWork Recovery Mod. I used face unlock password together with unlock pattern backup. Now I wanted to encrypt my device. I go trough every step, setting password, charging battery over 80% and plugging in charger. When I finally click Encrypt device, the green Android mascot flashes for second, then screen goes black for minute or two, then phone boots up but no encryption process is performed and the phone is unencrypted.
I tried:
1. Disabling SuperSU
2. Disabling Orbot startup
3. Disabling SIM card PIN request
4. Doing encryption in both portrait and landscape mode
5. Unplugging charger right before clicking Encrypt
I have installed: Flashed Stock ROM with Odin, did a factory reset from stock Recovery, set up my phone, then rooted phone using CF-AutoRoot, Installed SA Manager 2.0, then Xposed Framework and Phone ID changer plugin, then flashed ClockWork Mod Recovery with Odin. At one point I wiped Cache partition from ClockWorkMod Recovery and when exiting choose Repair Root. Then I installed Orbot, Orweb, SecureChat and four other applications to manipulate NFC cards.
What is causing my phone to not encrypt upon reboot? I don't want to reset and reflash everything because my phone already have lot of information that I don't want to lose.
Edit: After trying various methods, I found that disabling SuperSU from paalications menu allowed me to encrypt the phone. This thread delivered http://forum.xda-developers.com/showthread.php?t=2485126&page=4 Tomorrow I will repeat the process again and will tell if Safe Mode is really required for success or only disabling SuperSU
Also the fools saying that Encryption is irreversible process are fools. They are copying each other's wrong blog posts. I clearly see a Decrypt device button and I will try to use it tomorrow!
It all comes down to this: If phone does not encrypt (reboots and then boots few minutes later, but no encryption) then do the following:
To successfully encrypt:
1. Disable SuperSU from applications menu
2. Restart phone in Safe Mode (tap Application key repeatedly while phone restarts)
3. Follow encryption procedure as normal (setting screen lock password, charger, etc.)
4. When encryption is complete, enable SuperSU in Applications menu.
To successfully decrypt:
1. Disable SuperSU
2. Reboot (Safe Mode not required)
3. Decrypt as usual
4. Enable SuperSU again afterwards
This information probably need to be included in some FAQ. This could save other people a lot of time and frustration trying to figure out what is wrong.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
Hi there,
I am a newbie and hoping that someone could help to give me some clear pointers about options that i could take to rescue my phone - I hope its not bricked.
I was attempting to install LineageOS 16 on my Oppo R7s. This is my second attempt at installing a ROM - I did it a couple of weeks ago with Project Spectrum, and it worked, but Project Spectrum didn't impress me, so i wanted to try lineage OS instead).
I entered developer mode and enabled USB debugging
I downloaded the LineageOS zip to my SD card, as well as a Google Apps zip.
I downloaded the TWRP app on my phone just in case it was needed, however I've never used that app and not 100% sure how to use it.
I rebooted in recovery mode, and tried to install from the LineageOS zip file. It didn't start installing, I got some error message which I cannot recall... so I tried wiping the application data first, to see if that would help (maybe that was my mistake??)
I then went back to the install menu, and tried to install the Google Apps package first.... it started downloading, but then crashed and black screened.
Now, when I try to power on the phone, I get the oppo logo, and then it briefly goes back to the install screen for a second, with a message on the screen saying: "updating please wait, do not remove battery, do not co other operations" - but this only lasts for a second, then it crashes.
When I try to reboot into recovery mode (Power key +volume down), it does the same thing. I cannot get back to the white recovery menu.
Is there any way that I can rescue the situation and get back into recovery mode to try again? Or get back to a functioning USB connection so I can load a new ROM zip to try that instead?
When I plug it into the power, I get no indication that the phone is charging.
I'm worried the battery will go flat.
I have ADB installed on my computer, but I dont really know how to use it - the only command I know is "adb push" to load the roms onto the SD Card
Any advice on how to get access again would be greatly appreciated!
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device
Hello,
my friends Samsung Galaxy A51 crashed while using it, opening a google docs link she received via WhatsApp.
Restarting the phone will only show Samsung logo, then Samsung Galaxy A51 logo and then dead again. No boot loop.
In the morning the wake up alarm set in the phone plays its chimes but display remains black.
Rebooting phone with holding volume down doesn't work.
The phone is not rooted or flashed.
I can enter Recovery mode. Tried to restart system. Tried to delete cache. Tried to repair apps. None of this changed anything.
I can connect via adb but only in Sideload mode. Hoped to unsintall Samsung Browser as this might be a damaged app. But I don't have permission because USB debugging is not toggled. I tried adb restart and adb restart recovery. Phone will no restart to Android. Restarting to recovery works but doesn't solve the problem.
I can bring the phone to Download mode. Btw. none of the tutorials helped to do this. At some point I double-tapped the power button and was surprised to get into Download mode. I wanted to flash TWRP recovery to the phone to get more options to backup and recovery. Unfortunatley the OEM protection did not allow me to flash TWRP recovery.
My friend is from Ukraine and has her Ukrainian banking app registered with this phone and currently no other possibility to access her bank account. Also she has a lot of data like contacts, messages, photos and videos only on this phone. So we can not do a factory reset.
Do you have any other ideas for troubleshooting?
Do you have any ideas how to remove OEM protection without access to OS so I can at least flash TWRP and do a backup?
Do you have any other idea how I could backup the phone?
Unfortunately I still have not been successful to get the phone working again or to backup or read any data.
Just to add another information: I drained the battery to 0% so the phone was totally dead. I was not optimistic that this full power off might help any more than the restarts I did so far. But running out of ideas. It didn't help or change anything.
I'm afraid only a factory reset could at least repair the phone :-(
Frisbee7 said:
I'm afraid only a factory reset could at least repair the phone :-(
Click to expand...
Click to collapse
Without OEM-Unlocking and USB-Debugging you will not be able to install TWRP and if so then all data would be gone automatically anyway, as this is equivalent to a factory reset.
The only way would be to download the STOCK-ROM with "Frija" (quick and free) and flash it with "Odin". Of course, the mobile phone is then virgin and has to be set up again from the beginning. A Google login restores a lot of data. Setting up the banking app again (username & password, etc.) shouldn't be a problem either.
Of course you can also try a factory reset first, but setting up a completely new one is not avoided here either.
Much luck!