Phone is painfully slow - Essential Phone Questions & Answers

After I accidently uninstalled twrp and magisk, the phone is terribly slow, i can still use it though, I don't have access to adb right now so i cant flash twrp or magisk. I did a factory reset and after that the phone is slow. Does anyone have any suggestions?

yellk20 said:
After I accidently uninstalled twrp and magisk, the phone is terribly slow, i can still use it though, I don't have access to adb right now so i cant flash twrp or magisk. I did a factory reset and after that the phone is slow. Does anyone have any suggestions?
Click to expand...
Click to collapse
I would suggest flashing the stock image and to return it back to factory. Sounds like something got corrupted that a factory reset doesnt fix. https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

Related

Bootloops when flashing System, Data

It first started this morning when my phone suddenly started rebooting while I was using it. Then I thought it as a ROM issue and flashed a new ROM over it. Everytime I try to flash something on system. TWRP Hangs and the phone restarts itself.
Tried repairing data, system partitions from TWRP, same thing happens. Bootloops when I try to repair data partition
Tried restoring nandroid backup. When it says flashing data, TWRP freezes and the phone starts bootlooping.
Can anyone help?
I have tried doing the EFS flash via adb from PC.
I'm stuck with the exact same problem since months.
CallMeAldy said:
I'm stuck with the exact same problem since months.
Click to expand...
Click to collapse
No luck?
Have you tried Claiming Warranty?
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
StarRavier said:
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
Click to expand...
Click to collapse
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
TJ_bab said:
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
Click to expand...
Click to collapse
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
StarRavier said:
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
Click to expand...
Click to collapse
Doesn't crash during backup but crashes during restore.
TJ_bab said:
Doesn't crash during backup but crashes during restore.
Click to expand...
Click to collapse
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
StarRavier said:
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
Click to expand...
Click to collapse
it doesn't boot at all.
It bootloops
I have the exact same problem. Last week upgraded to 7.0, root, stock room, viper4arise audio and EX kernel and that's it. while taking pictures it froze then that boot loop, somehow I managed through a combination of flashing factory image through fastboot, locking, unlocking, reflahsing, to get it to boot normally, then yesterday I was taking pictures again and it refroze then bootloops. Now I am able to fastboot factory images but it doesn't get me out of the bootloops, and in TRWP same as you, I cannot flash anything on data or system. Repairing the file system doesn'T change anything, I did like on other threads also and flashed factury, restored nandroid then flash factory but the restore on TRWP always hangs up.
I was wondering if there is someone knowing the adb dd commands to impose the raw copying back of the restore ? Maybe that would work.
Did you try wiping system under wipe > advanced in TWRP?
In twrp, can you open a terminal and check the results of this (basically, doing a full read-only test of your flash)
Code:
dd if=/dev/block/mmcblk0 of=/dev/null

Need Help; My LG G6 (H870) keeps booting in TWRP and I can't install stock ROM

Hi,
I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.
I decided to look for a stock ROM and flash that ROM.
I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.
Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.
I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?
After this I took these steps solve this issue:
1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)
2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.
Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.
My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.
3. Installed LG Bridge for more drivers; did not work either
4. Downloaded Uppercut, but it doenst work without LGUP.
4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing
5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.
7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.
I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.
Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.
Really hoping for a kind person to help me out and provide me solution for this issue.
Thanks in advance
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
autoprime said:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
Click to expand...
Click to collapse
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
RoyalD said:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
Click to expand...
Click to collapse
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.
Had the same issue, fixed it, thanks.
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.
RoyalD said:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
Click to expand...
Click to collapse
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...
Well, I finally solved it with lgup and uppercut... what a nightmare.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash stocl .kdz with uppercut and lg up
Saved my G6!
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Great tip @Swizzle82! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!
Hi, all
If I understand, and to sum up :
I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/
Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?
Thx

How to root on stock 7.1.1 using Magisk

So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.

I'm not sure how to fix...

So I was trying to wipe dalvik/cache via Twrp, I accidentally did a factory reset instead. After going through the prompt process of resetting up the phone, I rebooted into twrp and restored my most recent backup. No, no matter what I try the phone wont go past the circular boot screen. How can I get past this
Bildo41383 said:
So I was trying to wipe dalvik/cache via Twrp, I accidentally did a factory reset instead. After going through the prompt process of resetting up the phone, I rebooted into twrp and restored my most recent backup. No, no matter what I try the phone wont go past the circular boot screen. How can I get past this
Click to expand...
Click to collapse
Did you try reflashing TWRP and then Magisk?
schmeggy929 said:
Did you try reflashing TWRP and then Magisk?
Click to expand...
Click to collapse
No, I did not! I didnt have my laptop with me and I was so flustered i hadn't considered it this morning. I'll get back to you after I try it ?
Ok, gave that a try and still didnt work. I'm downloading the latest software update to see if that'll make a difference.
schmeggy929 said:
Did you try reflashing TWRP and then Magisk?
Click to expand...
Click to collapse
So I flashed the latest 9.0.12 software, and the phone booted. It seems all I need to do is reflash twrp and Magisk and I should be good. Thanks for your input, I appreciate the input.

My device is stuck at fastboot after rooting it and updating Magisk

I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.
Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.

Categories

Resources