Develop Bugs

Failed Root; Stuck in Loop "process com.google.process.gapps has stopped"

Hello and thank you for taking time to read this post.
I attempted to root my At&t Samsung Galaxy S3 today then install tha AOKP Rom, and it back fired due to poor instruction, and poor execution. At the moment my phone, whenever it turns on "inititing swager" (with a pink horse and gears) then gives me a pop-up saying "Unfortunatly the process com.google.process.gapps has been stopped." and "Unfortunately, Setup Wizard has stopped". Whenever I hit ok, the other shows up. I have access to the pull down menu, but can't open any of the links on it. I can also shut it off then get back to the root(hat menu) menu. From which I have tried the option "wipe data/Factory Reset" link, but that changes nothing when I reboot. At this point I am just looking for a way to get it back to factory settings or at least working!
How I got here:
1. Rooted the phone through my computer (successfully it seemed)
-Using this tutorial: /watch?v=bIUA1IxiJzo
2.Started puting AOPK on!
(with this: /watch?v=qzcR-G7EKSw
Look, I know none of you have to help me but any feedback will be greatly appreciated.
P.S. I hav looked through other forums about the gapps error, but the difference is mine is not running to the home screen so I can't go to application manager!

Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.

Thank you for responding so quickly! I am attempting the first method, however i am not sure how to transfer a different rom image(im assuming the adb stands for Android Debug Bridge). I was using the internal SD, but I can plug it the phone into my computer, and it says no drivers found for this device, where before it recognized the phone. Once I get that I can clear the other data and restart.
Your help is very appreciated!
smelenchuk said:
Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.
Click to expand...
Click to collapse

Gapps loop
How can I post a doubt in XDA forum?

What custom recovery is on your phone? I suggest installing Philz Touch via Odin if possible and then flash a new rom from an external SD card.

Error «Encryption was interrupted and cannot be complete»

Hi Guys! I have a problem, and i really don't know how can i fix it.
My phone boots normally, but when boot finish this error appear in the screen:
«Encryption was interrupted and can't be completed. Phone data cannot be used anymore.
To continue using your phone, you must restore factory settings. After the restoration, you can restore data backed up in your Google Account to your phone»
There is a "Reset Phone" button but if i push it nothing happen.
I have tried to clear data/cache in recovery but nothing changed, I have tried to install a new ROM (i tried a lot of ROMS) but when it arrive to 50% more or less installation fails.
I have tried this guide oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ but it cannot work (Image Attachment)
Also FASTBOOT can't work. (For exemple: if i try to flash recovery it fails remote: failed to flash recovery / erase userdata / cache)
I really don't know where can i also looking
Help me please!

Anyone?

I'm having the same problem....
Restoring an old backup woth TWRP results in the same error.....

hi guys this happened to me too,
luckily I had twrp 2.8.6.0 flashed for recovery.
think you should still be able to get into fastboot if you do a battery pull
then poweron with the powerbutton and volume up till you see the oppo man icon.
then you should be able to flash your recovery with the latest twrp.
if you seen the penquin then this may not work for you. As i have not done a hard recovery before so i dont know if it would work.
I saw the oppo man so i was able to fix it by:
booting into twrp recovery,
i selected wipe --> advanced and there was an additional option to do a wipe for encrypted volumes and i selected all partitions to be wiped
then i installed i had downloaded on my SD card, it was ColorOS 2.0.8i i believed and it fixed it.
sorry if i am a bit grey about the details i did it a while ago so.
Actually found this in the cm12.1 nighlies thread
http://forum.xda-developers.com/showpost.php?p=58304054&postcount=14
issue is possibly due to unified partitions

Accidently deleted Android OS on HTC One M8

I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc. I can't send ADB commands to it, it won't show up on windows file explorer, I can't even turn it off. As is said this is an old phone so I am not worried about losing data, which is probably just as well at this stage!
Any advice would be appreciated!

Kieran C said:
I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc.
Click to expand...
Click to collapse
The physical buttons will respond, but you need to hold them for a pretty long time in the current "stuck" state. Do this:
1) Hold vol up button and power button, until the phone restarts (may take about a minute in the current stuck state).
2) Once the screen goes dark to reboot (but before the HTC logo screen appears again - I think you have 5 seconds or so), let go of the buttons, and only hold the vol down button. Do not let go of vol down, until you see the bootloader screen.
3) If you fail to get to bootloader, you simply got the timing wrong. Either started pressing vol down too late, or you let go of it too early. Simply repeat steps 1 and 2, until you get to bootloader.
4) Once in bootloader, simply select recovery, which will boot TWRP. And flash Lineage as you originally intended.
A note on wiping system when flashing a ROM: I know some folks will swear by this, and some guides will tell you to do it. But it is not necessary, and as you've seen can cause some complications. Nothing that isn't easily solved, but may give you headache nonetheless (like this case here).
The ROM install script will wipe system before it installs the custom ROM. So doing it yourself is redundant. And in the case of the ROM fails to install (it happens) you are stuck without a working OS. My recommendation is only to wipe cache, Dalvik and data when flashing a custom ROM (the default wipe in TWRP).
Any perceived "benefit" from wiping system is usually a placebo. In the rare event that the custom ROM fails to boot (or some other issue), you can always go back and flash again, wiping system (as a troubleshooting measure, etc.). Of the years of flashing ROMs (dozens and dozens of times) on various Android devices, I can count maybe 2 times where I felt I needed to wipe system when flashing a custom ROM.
Kieran C said:
I can't send ADB commands to it, it won't show up on windows file explorer
Click to expand...
Click to collapse
This can be expected when "stuck" on the logo screen. adb will only work when booted to a working OS, or alternately when booted to TWRP. Same thing with MTP access (File Explorer).

Mi Max 3 stuck in fastboot

Long story short, I tried to flash a global ROM on my Mi phone. However, after a few unsuccessful attempts at doing so, my phone is now stuck in the fast boot screen.
I tried all I know and what I can find online, but the problem still persists, where when holding the power button it would boot to main power screen and then make a buzz and go back to the fastboot screen.
Have tried:
- Resetting through recovery mode (pow + vol up)
- plugging phone into my computer to reflash the ROM (error remote: unknown command) / on my phone it would switch out of fastboot and instead display this message: "press any key/button to shutdown"
- pow + vol down (held for more than 1 minute)
- pow (held for more than 5 minutes, everytime it would boot and then boot back into fastboot mode with the buzz in between)
- ADB console commands:
- fastboot reboot
- fastboot device
- tried using MiPCSuite, plugged my phone in, but application didn't detect my phone
- running all applicable applications as mentioned above as admin
- when resetting phone progress bar would stop at 1.03% then it would say reset completed (I don't think did reset the phone, but whatever...)
- tried different ROM versions, Global and China (Once again it would either switch out of fastboot on screen OR in the flash tool it would display the error "unknown command" which I assume would be something to do with the communication between my PC and the device itself)
At this point I don't know what else to do, watched every tut on youtube, read pretty much all the forums I could find related to this issue.
Any help would be much appreciated!

Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this

Wywern.pl said:
Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this
Click to expand...
Click to collapse
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.

Note - wipe data and format data is not the same
I've stuck with some stupid error ("erase all data" message and reboot to twrp) for hours until I formated data

jayX23 said:
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.
Click to expand...
Click to collapse
did you solve it? i also need to flash rom via mi flash tool but I do exact same error.

Question Can't access recovery mode and have infinite boot loop

I Have a pixel 6 pro that I have rooted. I was going through the process of installing the latest update, (May 2022), via ADB. I have done this several time with success and no real issues. This time, just as I was on the last step of the update, (what's highlighted in yellow),
(This below is from notes that I've created for myself that I follow along with a YouTube channel)
-Execute the below command and directly flash the magisk patched boot.img file to your device
~ fastboot flash boot AND NEW magisk_patched-.img ~
-Restart the phone
my cat walked on my keyboard, and I think might have caused things to go bad.
Now my phone is stuck in a boot loop. I would like to do a factory reset but any time I can get to the Fastboot menu, (by holding down power and volume down), and select the Recovery Mode, it just sends me to the screen that says that I have unlocked my Boot loader and restarts the phone and continues the boot loop.
I have gone back to the CMD in ADB and have done some of the step over again in the updating process to no avail. I've done the googles with all of the results being the same telling me to factory reset the phone, which I would like to do but can't, so I'm reaching out to here, hoping to find an answer.

How about Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)? Make sure and kill ADB in Windows Task Manager first.

Draco3X said:
I Have a pixel 6 pro that I have rooted. I was going through the process of installing the latest update, (May 2022), via ADB. I have done this several time with success and no real issues. This time, just as I was on the last step of the update, (what's highlighted in yellow),
(This below is from notes that I've created for myself that I follow along with a YouTube channel)
-Execute the below command and directly flash the magisk patched boot.img file to your device
~ fastboot flash boot AND NEW magisk_patched-.img ~
-Restart the phone
my cat walked on my keyboard, and I think might have caused things to go bad.
Now my phone is stuck in a boot loop. I would like to do a factory reset but any time I can get to the Fastboot menu, (by holding down power and volume down), and select the Recovery Mode, it just sends me to the screen that says that I have unlocked my Boot loader and restarts the phone and continues the boot loop.
I have gone back to the CMD in ADB and have done some of the step over again in the updating process to no avail. I've done the googles with all of the results being the same telling me to factory reset the phone, which I would like to do but can't, so I'm reaching out to here, hoping to find an answer.
Click to expand...
Click to collapse
In addition to what @roirraW "edor" ehT said (), you may want to try to just flash the stock boot image first to see if it gets you out of the bootloop instead of going into recovery mode to do a factory reset, since it appears you can get into fastboot mode.
Is it also possible that you may have some Magisk mods installed that need updating that may be causing the bootloop?

Did you try disabling Magisk modules? This might work:
As the phone boots, hold down the volume button to get into safe mode. This will trigger Magisk to disable modules when you reboot. Reboot as normal.
For me the culprit was Addon Features for Pixel Devices.
Otherwise, as the posts above say: flash the factory image or boot.img.

Thanks @roirraW "edor" ehT. That was a pain in the butt suggestion, but the advice worked. Now I'm going and doing a full restore.​
@Lughnasadh, I did what you suggested before I even posted, hoping that it would work but it just sent in into bootloops.​​@peabody42, When I was in the Fastboot menu, I could select all of the options but with the exception of the serial number option, all other options would just send me back to the beginning, starting the bootloop.
Thank you all for the suggestions and help.
​

Draco3X said:
Thanks @roirraW "edor" ehT. That was a pain in the butt suggestion, but the advice worked. Now I'm going and doing a full restore.​
@Lughnasadh, I did what you suggested before I even posted, hoping that it would work but it just sent in into bootloops.​​@peabody42, When I was in the Fastboot menu, I could select all of the options but with the exception of the serial number option, all other options would just send me back to the beginning, starting the bootloop.
Thank you all for the suggestions and help.
​
Click to expand...
Click to collapse
Great to hear it helped. Good luck!
FYI, tagging users doesn't work if you copy/paste the username link in a post - that's just a link to their user profile. Tagging users only works if you paste as value (in Google Chrome and some other things, Control-Shift-V). i.e. if the username is already a link, then the "@" symbol before it won't help anything, and we won't get notifications that you tagged us.