I have a rooted tmobile lg v10, and I just tried to encrypt it using full disk encryption in settings. Right after I started the encryption the white screen with the green android shows up for about 1 second then the tmobile boot picture showed up and stayed there until I removed the battery. All my data is still here and my phone is exactly the same as when I started the encryption process. Any way to fix this?
You have a backup? If so go to your backup and delete your finger prints on it then try it all again
I have a titanium backup of apps. Would it work if I just disabled fingerprints?
No go into settings and delete all of the fingerprints. As a security measure they persist through encryption and a factory reset.
Removed my finger prints. Still doesnt encrypt my phone. Just sits at the same screen.
Are you completely stock? Rooted? Twrp?
You need to kill root first. Run this in terminal emulator:
pkill -KILL daemonsu
Then go through the encryption process.
See if that works.
blubyu87gt said:
You need to kill root first. Run this in terminal emulator:
pkill -KILL daemonsu
Then go through the encryption process.
See if that works.
Click to expand...
Click to collapse
the author did not reply so I guess it did work
shotguns10 said:
I have a rooted tmobile lg v10, and I just tried to encrypt it using full disk encryption in settings. Right after I started the encryption the white screen with the green android shows up for about 1 second then the tmobile boot picture showed up and stayed there until I removed the battery. All my data is still here and my phone is exactly the same as when I started the encryption process. Any way to fix this?
Click to expand...
Click to collapse
a_petrov303 said:
the author did not reply so I guess it did work
Click to expand...
Click to collapse
Haha yeah hopefully so! I haven't tried it on some of the 5.1.1 or 6.0 though.
I also have a rooted LG V10 and yes for encryption you have to do this (done on my phone) :
http://forum.xda-developers.com/g4/general/howto-encrypt-decrypt-phone-rooted-t3200256
I haven't tried it
Related
So I have had this issue with my phone today where I couldn't seem to get passed the Too many pattern attempts screen.
After trying all my combinations of e-mail and passwords, I was unable to access my phone. As a result, I attempted to do a hard reset (the pressing of both volume rockers and then trying to reset it in that recovery mode).
I did so, wiping all my data, but the too many pattern attempts screen remained. So as a result, I booted up Odin and downloaded the stock versions of the Samsung Fascinate's ROM and proceeded to reflash (or what I believe to be reflashing, I simply followed the directions found in the stickies).
That all said and done, my phone still remains in the too many pattern attempts lock.
I've checked the similar posts on a couple of websites, but was unable to find a situation where all of these fixes did not work.
Thank you!
No replies yet, so I am just going to throw this out there on the off chance that it *might* actually work.
The "complete voodoo lagfix removal" uninstall.zip CWM flash seems to be working as a cure-all for just about whatever may ail your phone, whether you actually *have* voodoo or not...
I would check that out in the OP of this thread.
Download the Voodoo Uninstall on your PC. Copy it to your SDcard (if you don't have a computer that you can put the card in after pulling it out of your phone, try using adb to push it to the phone)
Boot into stock recovery, and flash "update.zip" to get into CWM recovery.
Flash that voodoo uninstall zip using CWM.
I really hope this helps. (Just in case it happens to me. )
Let us know!
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
namebrandon said:
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
Click to expand...
Click to collapse
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
martian21 said:
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
Click to expand...
Click to collapse
Good point!
mkdir /dbdata
mount -t rfs -o nosuid,nodev,check=no /dev/block/stl10 /dbdata
else_where said:
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You work for Flextronics ???? Didn't Verizon end their contract with them for all regions already ????
working in an A class store. allot of the philly market and north east stores still have techs. besides or sales people are helpless. like every time with a cellbrite is their first time
Sent from my SCH-I500 using XDA App
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
runeliger said:
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
Click to expand...
Click to collapse
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
mexiken said:
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
Click to expand...
Click to collapse
Yes indeed I did. The first thing I did was the Factory data reset.
Unfortunately, the phone seems to be in a state of perpetual ariplane mode preventing access to any network.
The phone also seems to be suffering from that com.android.phone crashes that I suppose make sense given how the Hardware version and the Baseband version are both unknown.
I'm going to try to flash it again in hopes of resetting my phone. The perpetual airplane mode is of course an issue. (but at least I got the alarm functinoality of my phone back)
Hrm, I'm concerned now. Check your settings / about phone and baseband version. Please tell me it does not say 'unknown'.
Yea, mine wasn't stuck in airplane mode, just didn't connect to google's servers to set up gmail.
If you're still rooted, maybe try the radio update ????
Any update ????
mexiken said:
maybe try the radio update ????
Click to expand...
Click to collapse
DANGER! - Don't go updating your radio unless you really know what you're doing. Yes there has been a radio update with the D01 however flashing the wrong thing to the radio will result in a shiny brick that as of right now can't be recovered!
Yeah I was seeing a bunch of unknowns in a lot of my slots.
I wasn't sure what was wrong, so I did some more research and it seemed as though that the modem aspect of my phone must have corrupted.
So I simply went to a verizon store and swapped out my phones (since I couldn't find a fixed modem).
The other fix of deleting via the privacy wipe definitely worked though.
Thanks everyone!
i500 fascinate too many patterns
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
anngiehdz said:
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
Click to expand...
Click to collapse
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
nitsuj17 said:
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
Click to expand...
Click to collapse
Respectfully I have to disagree. Sharing a new solution to an old problem cannot be a bad thing. maybe 6+ months from now it will save someones bacon without having to start a new thread for it
[Q] is it safe turn off "keep awake" / wakelock for "Android System" ?
in app ops, what happens if i turn this off? thanks,
I wouldn't touch that. It could mess up quite a bit of stuff.
Hi xda-community,
I've been stupid enough to deny android system the wakelock rights. I was a little to quick but the google play service ate 25% of my battery today, and so I just messed around with App-Ops.
I'm running CM10.2 nightly on my sgs2. I've already tried to get into the safe mode with holding Vol+ and - while booting, but it wasn't successfull. The Phone is stuck on the boot logo.
Is there any way besides a reset?
Edit: Just tried reflashing the recent update but it's still stuck...
Edit2: Just did a backup to sd card via CWM. My current plan is to modify this update in a way to let app-ops forget his settings. Is this possible? Any clue where I have to look?
Edit3: Just did rm -R * on /data/data/com.android.providers.settings. THIS DOES NOT CLEAR APP-OPS SETTINGS but my phone booted afterwards and i had enough time to revert my previous changes. Need to reconfigure some of stuff obviously.
Edit4: Deleting everything with the cmd in Edit3 will cause the notificationbar to malfunction. Furthermore you won't recieve any notifications. I just restored the files from my backup i made with CWM (adb push c:\backup /data/data/com.android.providers.settings and everything is working again. Now I'm really done
bye
haxti said:
Hi xda-community,
I've been stupid enough to deny android system the wakelock rights. I was a little to quick but the google play service ate 25% of my battery today, and so I just messed around with App-Ops.
I'm running CM10.2 nightly on my sgs2. I've already tried to get into the safe mode with holding Vol+ and - while booting, but it wasn't successfull. The Phone is stuck on the boot logo.
Is there any way besides a reset?
Edit: Just tried reflashing the recent update but it's still stuck...
Edit2: Just did a backup to sd card via CWM. My current plan is to modify this update in a way to let app-ops forget his settings. Is this possible? Any clue where I have to look?
Edit3: Just did rm -R * on /data/data/com.android.providers.settings. THIS DOES NOT CLEAR APP-OPS SETTINGS but my phone booted afterwards and i had enough time to revert my previous changes. Need to reconfigure some of stuff obviously.
Edit4: Deleting everything with the cmd in Edit3 will cause the notificationbar to malfunction. Furthermore you won't recieve any notifications. I just restored the files from my backup i made with CWM (adb push c:\backup /data/data/com.android.providers.settings and everything is working again. Now I'm really done
bye
Click to expand...
Click to collapse
I denied the keep awake of Android system and I am gone. My touch didn't work. I did forced restart using the power button. It worked for sometime. Again the touch doesn't work. In the allowed time, I set it to Allow but still i face the issue. Is factory reset the only solution?
Long story short i deleted my data/app file(accidentaly). Sony xperia S android 4.2.1 i think... Dont ask how that happened. So right after i deleted it by mistake everything started crashing many apps stopped working. Immediatly after doing that i restored a restore point and rebooted. As you would expect my phone is password protected, but when i klick the password slot id doesnt show the keyboard nor the option to change keyboard because i was using swift key keyboard. Now i cannot enter my phone, so i think that i should do s factory reset but i cant do that. I know that i saw a factory reset option on the sony software updater on my pc because i wanted to update my phone. Also when i tried to root my phone i could not flash it some broken driver issue (was not able to fix) so i finally rooted it with the root tool kit. Well please help me with this. Also i assume that the restore point didnt work. Please help :crying: :crying:
Hmm. So you deleted your /data/app folder and most of the apps are gone? Whoops! lol And you are rooted. Do you have a custom recovery? I'm assuming so since you said you tried to restore a backup, is that correct? It would probably just be easiest to factory reset in recovery as that will remove the password and then when it boots, you can restore the keyboard app. Other option is trying to remove the password in recovery (has to be custom) with adb commands as you won't be able to while booted due to the password.
http://forum.xda-developers.com/showthread.php?t=2620456 - and this does not work for every device, obviously.
es0tericcha0s said:
Hmm. So you deleted your /data/app folder and most of the apps are gone? Whoops! lol And you are rooted. Do you have a custom recovery? I'm assuming so since you said you tried to restore a backup, is that correct? It would probably just be easiest to factory reset in recovery as that will remove the password and then when it boots, you can restore the keyboard app. Other option is trying to remove the password in recovery (has to be custom) with adb commands as you won't be able to while booted due to the password.
http://forum.xda-developers.com/showthread.php?t=2620456 - and this does not work for every device, obviously.
Click to expand...
Click to collapse
Well the thing is that im not near a pc for the next few days, but i have a tablet which has the device input to usb output cable. So i was wondering if theres a app that turns my android tablet into a keyboard for my phone. Ive been looking but only found bluetooth and wireles keyboard wich wont do me any good since my phone is locked. Also is there an app that could hack my phone since its rooted.
Pretty sure you're out of luck without the PC.
Sent from over there...
I rooted and installed custom recovery on my HDX7 using the HDX Toolkit according the the given instructions. After a few days I decided to uninstall recovery and moved the TWRP backup to external storage. I hadn't installed any custom roms or created any rom slots. I had no problems for days until these changes I made last night.
I uninstalled towelroot, reading that it was safe to do so. I installed a flashlight app. I installed Greenify and auto-hibernated some some third-party apps - including ES FileManager and Safestrap, which I considered safe since I had already uninstalled recovery. I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well. I also turned WIFI off before shutting down.
The device is now stuck at the second splash screen with the animated white and gold Kindle Fire logo. The screen is also slightly dimming and brightening repeatedly. I can't get into safe-mode/ recovery mode. I looked up what I was disabling but think I goofed using NoBloat and Greenify and screwed myself by uninstalling recovery.
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Segue2 said:
...
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Click to expand...
Click to collapse
Did you try hard reset? Press power button for more than 20 sec. Your kindle should then restart itself hopefully without bootloop. I was once messing with rooted stock fire OS trying to add one app to system apps (live wallpaper support I think), after restart I get neverending bootloop, but I was able to get out of this by doing hard reset, then Safestrap showed again and I was saved.
If you can manage reverse all your changes on system through adb, good for you, but without installed Safestrap ... well, maybe someone with better skills can manage you through this ...
I have tried but hard resets aren't working.
Can you still access it through ADB?
EncryptedCurse said:
Can you still access it through ADB?
Click to expand...
Click to collapse
No, looks like I am having trouble getting adb access. Command adb devices is returning nothing. Windows is recognizing the Kindle, however, but only as a portable device. Definitely had adb access before (established to use the HDX Toolkit). Now, I am wondering whether I disabled adb support on the kindle at some point beforehand.
On a sidenote, I just unplugged and reconnected the usb cable a few times and was able to hit the lockscreen for a few seconds before falling back into the bootloop. I have been able to repeat this.
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Segue2 said:
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Click to expand...
Click to collapse
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
EncryptedCurse said:
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
Click to expand...
Click to collapse
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
jimyv said:
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
Click to expand...
Click to collapse
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Segue2 said:
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Click to expand...
Click to collapse
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
jimyv said:
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread and that you till the thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
Click to expand...
Click to collapse
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
lol
Segue2 said:
I will try fresh installs on Windows again, then. I did read and interested tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Click to expand...
Click to collapse
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
Segue2 said:
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
Click to expand...
Click to collapse
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
jimyv said:
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
Click to expand...
Click to collapse
Ok, good to know about the power.
Yes, I have used the Minimal Adb and Fastboot utility before and couldn't get access.
I can get into stock recovery for a factory reset.
I can not get into SafeMode. It ends up booting to the lockscreen for a second or two before falling back into bootloop - sometimes flashing the lockscreen again.
okay well I do believe you have run out of options..in a nutshell you are looking at a replacement device anyway so you should be on the go for a factory reset
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
by
Segue2 said:
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
Click to expand...
Click to collapse
nope you are out of options before you got to the factory reset.apparently something was done to the system that nobody knew about. Or there is a hardware problem anyway.you can try to hold the power for over 20 seconds or another factory reset but sounds like you need to give Amazon a call anyway you might have had a bad unit. Because nothing you described in above paragraphs should have gotten you to this point.
Segue2 said:
... I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well.
Click to expand...
Click to collapse
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
jeryll said:
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
Click to expand...
Click to collapse
the loop he was in would not allow him ADB either ,something was done here other than what has been stated whether it was known or not.
correction I also use greenify it on all my devices. And to be able to do anything to system you must have had exposed framework installed....in which case I would have never have recommended a factory wipe. as stated several times already. simply hibernating a few apps even hibernating a few apps ( which is about all you can do without framework) would have not gotten him here. he had to have permanently removed something from system or permanently disabled iteither way without knowing exactlywhat service he appy that too it would be a guessing game even with adb.in short like you said lesson learned for another person that bothers to read this thread not to tamper with your stock system without safestrap at bare minimum and a backup
I wonder if he has had any luck with ADB now that he is no longer in a perpetual boot loop. May be able to come up with a reenable command for system apps? Su should still be in systemat least the binaries will be in case the app wasn't. And I think in this case it would be better if the app was not in system but the binaries remained since he cannot get into the OS he will not be able to grant permission..but without. su command should work still
Thanks for the input. Wiithout a doubt, lessons learned here. At the very least, I never should have uninstalled Safestrap even if I wasn't planning on doing anything else to the system. I have the TWRP backup of my rooted stock, but with no way to use it now - useless.
I must have disabled some critical app or combination of apps that lead to the conflict, despite the care I thought I was taking. As far as Xposed framework goes, I never installed it manually. Maybe it is packaged in with one of those apps? The other thing I wondered about was whether disabling wireless could have led to a conflict. Using the Toolkit has been reported to lead to a bug where the system can crash when trying to enable wifi without first enabling bluetooth.
Either way, all I had to do was leave safestrap alone, just in case. F.
All of your help and feedback has been appreciated!
Wow. Well, I have adb access. After mutliple unsuccessful attempts on Windows and Linux, I was able to fire up an old MacBook and established an adb connection in 10 minutes. Unbelievable! The list of installed packages doesn't show any third party packages. Can I push and install Safestrap through adb to get my backups up and running? Whar is the correct syntax for those commands? I have already got a replacement on the way, but I would like to try to bring this one back and unroot. On second thought, maybe I should just leave it?
I OTA updated my stock unrooted XQ-BC72 to android 13, it boots up to the home screen, fully functional for 10 seconds, then reboots. I can choose power off in that time to prevent rebooting.
I don't want to factory reset if I can avoid it because there's user data I want to get from the device.
I can boot in safe mode: same thing.
The fingerprint sensor had stopped working a while back, and I had changed various configuration settings, which worked fine before. I've reset all app settings. I took out the SIM & microsd. No change.
Any ideas about what i could do?
Re-flash your device using PC Companion or newflasher
nhat.nguyen said:
Re-flash your device using PC Companion or newflasher
Click to expand...
Click to collapse
I will probably have to do that. And first I'll try factory reset. But because I want to recover user data from the device, I was hoping there was some way I could stop it rebooting soon after reaching the home screen, even with reduced functionality. And then fix the OS.
Yep that happened to a lot when i re-wrote the super to removed files from the system.