Well I'm trying follow the steps of the thread of battery life to try get an 0.1% of drain per hour but when I try to uninstall the apps ( velvet apk, play services and other apps) the apps appear uninstalled then reboot and it's again the apks on system folder any ideas? Or am I doing something wrong? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk
Do you have system write protection off? You have be able to write to system for changes to stick
gunnyman said:
Do you have system write protection off? You have be able to write to system for changes to stick
Click to expand...
Click to collapse
Maybe that's the problem, where can I change the system write protection, that is the answer to many questions, like I can't use xposed an sole others, so we're can I turn it off? Thanks for the answer
Enviado desde mi XT1058 mediante Tapatalk
hermeshhn said:
Maybe that's the problem, where can I change the system write protection, that is the answer to many questions, like I can't use xposed an some others, so where can I turn it off? Thanks for the answer
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Enviado desde mi XT1058 mediante Tapatalk
Is it the dev edition? If not and you rooted using jcase method, his method replaces stock recovery with a version of Android with write protection off. So just boot into "recovery" and you'll be good
Sent from my Nexus 7 using xda app-developers app
davidtb12 said:
Is it the dev edition? If not and you rooted using jcase method, his method replaces stock recovery with a version of Android with write protection off. So just boot into "recovery" and you'll be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Isn't the dev edition, that method is on Android development? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk
hermeshhn said:
Isn't the dev edition, that method is on Android development? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Yes. If you've rooted with Jcase's method, you need to reboot into "recovery" mode to have system writable.
you can either use adb reboot recovery command or install something like quickboot app and choose reboot recovery.
gunnyman said:
Yes. If you've rooted with Jcase's method, you need to reboot into "recovery" mode to have system writable.
you can either use adb reboot recovery command or install something like quickboot app and choose reboot recovery.
Click to expand...
Click to collapse
well I´ve tried what you told me but when I reboot into recovery only appear a green android with a red triangle on him, then reboot but I check the protection with adb shell getprop ro.boot.write_protect and gives me 1, when should be 0, any ideas? I´m rooted with RockMyMoto
hermeshhn said:
well I´ve tried what you told me but when I reboot into recovery only appear a green android with a red triangle on him, then reboot but I check the protection with adb shell getprop ro.boot.write_protect and gives me 1, when should be 0, any ideas? I´m rooted with RockMyMoto
Click to expand...
Click to collapse
if you rooted with jcase's method and you see a recovery like you've described either you've put the stock recovery back on the phone, or you haven't rooted properly.
Putting back stock recovery breaks the system write capability of the root method.
Just 'Freeze' the applications. It should have the same effect on your battery life and it survives without system write protection. It also has the added benefit of being easily reversed if you accidentally disable anything important.
If you rooted using jcase's method, the recovery was hijacked. This means that instead of rebooting into a recovery when you "reboot recovery," it'll reboot the phone normally, but write protection will be off. This allows you to do what you want to do (i.e. remove apps/bloatware). Once that's done, you'd reboot and everything would be normal and write protection would be turned on again.
Related
Hi, I have a lg l90 d405n with lolipop version v20a. I've rooted and changed rom last month but then restored it back to default rom. I' trying to root it again now but i cant. I followed different guides but none of them worked. I've tried the one click root, fails because send command crash. Update.zip in sd card, it fails because it cannot verify the file signature. Is there a specific method to use in this version?
If you have custom recovery instaled just download flashable supersu.zip and flash it..(search for it in xda forum to avoid scams).
Enviado do meu LG-D405n através de Tapatalk
Root LGs
It's easy
If you have restore your to the original ROM, just follow this guide:
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
This is only the command that you have too use, read the post in the link I already gave you.
1 -
adb.exe devices
2 -
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
3 -
Send_Command.exe \\.\COM4
4 -
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
Warimation said:
If you have custom recovery instaled just download flashable supersu.zip and flash it..(search for it in xda forum to avoid scams).
Enviado do meu LG-D405n através de Tapatalk
Click to expand...
Click to collapse
No, i dont have. It's lg recovery, i put it back in original form, no root no unlocked bootload nothing. Just like new, but i can't root it again
XiCO FiR3 said:
It's easy
If you have restore your to the original ROM, just follow this guide:
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
This is only the command that you have too use, read the post in the link I already gave you.
Click to expand...
Click to collapse
I already used that one, it fails in the sens comand
Tonize said:
No, i dont have. It's lg recovery, i put it back in original form, no root no unlocked bootload nothing. Just like new, but i can't root it again
I already used that one, it fails in the sens comand
Click to expand...
Click to collapse
You can always try Kingroot.
It never failed me in any device, but there are always a first time:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
I always used the pc version.
But try first with the APK.
Good Luck!!!
Tonize said:
I already used that one, it fails in the sens comand
Click to expand...
Click to collapse
Reinstall LG drivers, and try again. If still not working and if your windows is 10 try rebooting it and try again.. I needed to do that sometimes for "1click root" to work..
If fails try kingo root although Its a bit difficult to replace it with supersu..
Enviado do meu LG-D405n através de Tapatalk
Kingroot worked, i've instaled aboot for the v20a software that's in the other thread, flashed clockworkmod and cyanogen. Working good thanks
Hi
Im having an strange trouble flashing firms or roms, from adb rsd or fastboot.
I can flash radio, cdrom and everything except for /system.
Another thing: I tried compressing /system (in pc) uploading with adb push and extract the zip, that method work but for sure dont boot.
I have already Motorola unlocked. And i cant pass the recovery or bootloader.
If usefull when i try to adb push each folder of system from system pc folder in any point it stucks forever and i cant mounting again unless erase it.
Btw: sorry for bad english. :silly:
When you flash from fastboot does it show an error?
Sent from my XT1095 using Tapatalk
AGISCI said:
When you flash from fastboot does it show an error?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Any error Just stucks forever. In fastboot or rsd.
Enviado desde mi GT-S5301 mediante Tapatalk
U said u have a unlocked bootloader and can't pass the recovery. What do u mean by that? Can't flash it or can't boot it from the bootloader menu
Hazou said:
U said u have a unlocked bootloader and can't pass the recovery. What do u mean by that? Can't flash it or can't boot it from the bootloader menu
Click to expand...
Click to collapse
Sorry is my bad english.
What i want to say is i only can see bootloader, the fastboot menú and cwm recovery. But i cant boot the OS
Enviado desde mi GT-S5301 mediante Tapatalk
militellodante said:
Sorry is my bad english.
What i want to say is i only can see bootloader, the fastboot menú and cwm recovery. But i cant boot the OS
Enviado desde mi GT-S5301 mediante Tapatalk
Click to expand...
Click to collapse
Format system through the CWM recovery and try to install one of the ROM zips.
Hazou said:
Format system through the CWM recovery and try to install one of the ROM zips.
Click to expand...
Click to collapse
Stucks on /system too.
militellodante said:
Stucks on /system too.
Click to expand...
Click to collapse
Ok, and "fastboot erase system" also didn't work? Or did it give an error?
Hazou said:
Ok, and "fastboot erase system" also didn't work? Or did it give an error?
Click to expand...
Click to collapse
I get no errors, i can erase from mfastboot or fastboot, and format it from cwm.
But I THINK, is an I/O error... there is a way to do something like "chkdsk" but in android?
Hi Guys,
Am facing this problem, and that is my Moto X-Ghost device can boot directly into system OS when I press power key to switch on the device but rather goes to Recovery/TWRP . And also when I I'm in TWRP recovery or any other recovery, I can't reboot to System and it rather boot back to TWRP again.
Please what fix do I need and how to solve this.
Please any help and guide is welcome.
Sent from my Moto X using Tapatalk
Sounds like there is no system on the phone or maybe corrupted partition.
First try formatting,restoring /system partition (a trick to have a clean partition would be to format it to f2fs and then back to ext4), once done flash a ROM on top with TWRP. Backup your /data partition , then make a factory reset and reboot .
If that doest work use RSD lite or Fastboot tools to flash stock ROM including stock recovery so you'll have to start from scratch.
Enviado desde mi Moto X mediante Tapatalk
lavero.burgos said:
Sounds like there is no system on the phone or maybe corrupted partition.
First try formatting,restoring /system partition (a trick to have a clean partition would be to format it to f2fs and then back to ext4), once done flash a ROM on top with TWRP. Backup your /data partition , then make a factory reset and reboot .
If that doest work use RSD lite or Fastboot tools to flash stock ROM including stock recovery so you'll have to start from scratch.
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
Am on ext4, but am able to use the device if only am able to boot to fastboot and select "Normal Reboot" then its able to boot to system.
Sent from my Moto X using Tapatalk
iykeDROID™ said:
Am on ext4, but am able to use the device if only am able to boot to fastboot and select "Normal Reboot" then its able to boot to system.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Then reflash recovery, probably that's what is causing it. Use fastboot to flash it.
Enviado desde mi Moto X mediante Tapatalk
lavero.burgos said:
Then reflash recovery, probably that's what is causing it. Use fastboot to flash it.
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
okay bro...
thanks and I will do that
Sent from my Moto X using Tapatalk
Does your pb fixed?
iykeDROID™ said:
okay bro...
thanks and I will do that
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks Very Much bro, it worked as you said I should should do......now I can boot, reboot, and do any sort of boot/reboot-related actions.....
Thanks, Nice.
Sent from my XT1053 using Tapatalk
iykeDROID™ said:
Thanks Very Much bro, it worked as you said I should should do......now I can boot, reboot, and do any sort of boot/reboot-related actions.....
Thanks, Nice.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I have the exact same issue..but flashing the recovery again doesn't work :/ (already tried with Win, Ubuntu, Arch...)
Rahh1112 said:
I have the exact same issue..but flashing the recovery again doesn't work :/ (already tried with Win, Ubuntu, Arch...)
Click to expand...
Click to collapse
Flash official TWRP 2.8.7.0 , after you download the image check md5sum to make sure its not corrupted.
If that doesn't work reflash full stock ROM with RSD lite or via fastboot and start from scratch.
Enviado desde mi Moto X mediante Tapatalk
Hello everyone!
A month ago I rooted my device (Huawei P8 Lite 2017 [PRA-LX1]) using the XDA tutorial here. Now I am trying to recover my device using this XDA tutorial here.
My device is fully working but I have a few problems and bugs now and then so I want to fully recover it. My bootloader is unlocked and USB Debugging is on but every time I try to recover my phone or flash anything, I am getting the same error over and over and over again: FAILED (remote: Command not allowed).
Any ideas on how to fix that and recover my device?
is the frp locked?
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
is the frp locked?
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
Yes it is and I tried to unlock it using the Fastboot and ADB but I am getting the same error.
meymigrou said:
Yes it is and I tried to unlock it using the Fastboot and ADB but I am getting the same error.
Click to expand...
Click to collapse
do you have stock recovery or TWRP?
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
do you have stock recovery or TWRP?
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I don't have the stock recovery and I don't know where to find it and download it. But I have all the TWRP files on my PC.
meymigrou said:
I don't have the stock recovery and I don't know where to find it and download it. But I have all the TWRP files on my PC.
Click to expand...
Click to collapse
first of all...take a backup using twrp...and then...you must flash the stock recovery...if you have root...you can use flashify...and then you must do a factory reset using the stock recovery...
after all the steps above...
you must relock your bootloader using thia command:
fastboot oem relock xxxxxxxxxxxxxx
xxxx.... are your bootloader unlock code...
after locking the bootloader you can re enable your oem unlocking in developing options
Sent from my PRA-LA1 using Tapatalk
---------- Post added at 06:11 PM ---------- Previous post was at 06:05 PM ----------
hamzio7 said:
first of all...take a backup using twrp...and then...you must flash the stock recovery...if you have root...you can use flashify...and then you must do a factory reset using the stock recovery...
after all the steps above...
you must relock your bootloader using thia command:
fastboot oem relock xxxxxxxxxxxxxx
xxxx.... are your bootloader unlock code...
after locking the bootloader you can re enable your oem unlocking in developing options
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
reasons why you need the stock recovery:
after relocking the bootloader your phone asks to delete everything and encrypt the phone again.
without stock recovery you can't
why you need to do a factory reset using the stock recovery first?
your phone will detect your phone as rooted and will give you this error when you try to relock the bootloader
root risk or something...i don't remember it
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
first of all...take a backup using twrp...and then...you must flash the stock recovery...if you have root...you can use flashify...and then you must do a factory reset using the stock recovery...
after all the steps above...
you must relock your bootloader using thia command:
fastboot oem relock xxxxxxxxxxxxxx
xxxx.... are your bootloader unlock code...
after locking the bootloader you can re enable your oem unlocking in developing options
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
First things first, thank you so much for taking the time to help me with a solution. Here's the problem: I can't do anything with TWRP because it's stuck at booting.
use flashify to flash twrp on your phone...or you can use dd commands via terminal and super su
meymigrou said:
First things first, thank you so much for taking the time to help me with a solution. Here's the problem: I can't do anything with TWRP because it's stuck at booting.
Click to expand...
Click to collapse
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
use flashify to flash twrp on your phone...or you can use dd commands via terminal and super su
Click to expand...
Click to collapse
I can't use Flashify because my device isn't rooted. I want to root it but I don't know how because TWRP doesn't work. Is there any other way I could root my device?
meymigrou said:
I can't use Flashify because my device isn't rooted. I want to root it but I don't know how because TWRP doesn't work. Is there any other way I could root my device?
Click to expand...
Click to collapse
have you rooted your device before?
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
have you rooted your device before?
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
Yes I did! I rooted it using TWRP and Super Su (both downloaded from XDA).
meymigrou said:
Yes I did! I rooted it using TWRP and Super Su (both downloaded from XDA).
Click to expand...
Click to collapse
su it's rooted...you just have to install the super su apk...
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
su it's rooted...you just have to install the super su apk...
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I just installed SuperSu from Play Store and it says that 'Root Undetected'.
meymigrou said:
I just installed SuperSu from Play Store and it says that 'Root Undetected'.
Click to expand...
Click to collapse
use the one that you downloaded from xda
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
use the one that you downloaded from xda
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
Same again, I downloaded the same SuperSu apk from XDA and it says that root undetected.
that's bad...i don't know what to do...can you try terminal emulator...type su and press enter key...if there wasn't any errors then you can use terminal to flash files
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
that's bad...i don't know what to do...can you try terminal emulator...type su and press enter key...if there wasn't any errors then you can use terminal to flash files
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I did and it says "not found". That's really weird, how can I fix a device that doesn't let you flash anything and it's firmware doesn't even work? When I try to open TWRP it stuck at boot and doesn't do anything. I can't even reset my device because it stays at boot.
meymigrou said:
I did and it says "not found". That's really weird, how can I fix a device that doesn't let you flash anything and it's firmware doesn't even work? When I try to open TWRP it stuck at boot and doesn't do anything. I can't even reset my device because it stays at boot.
Click to expand...
Click to collapse
use adb command to boot into recovery and see if the device boots to TWRP...
adb reboot recovery
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
use adb command to boot into recovery and see if the device boots to TWRP...
adb reboot recovery
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I just did it and it stuck at boot again.
meymigrou said:
I just did it and it stuck at boot again.
Click to expand...
Click to collapse
the only thing that you can do to flash files at the moment is with DC Phoenix box ... it's a paid app...15 euro for 72 hours of using...i used it to fix mine
Sent from my PRA-LA1 using Tapatalk
Is it possible to boot into custom recovery without actually flashing it? Used to do it on other devices but it was a long time ago? I need to edit build.prop to enable multi user but don't want to do any other changes to my phone. Like unlocking bootloader etc. Many thanks.
Sent from my SM-G973F using Tapatalk
If I remember correctly, twrp image must be in ADB folder and then:
fastboot boot recovery [name_of_twrp].img
or
fastboot boot [name_of_twrp].img
Tell me please back which one was right
Doesn't seem to work for me, stuck on waiting on device and nothing happens. Do you need unlocked bootloader to do this?
Sent from my SM-G973F using Tapatalk
lepszy said:
Doesn't seem to work for me, stuck on waiting on device and nothing happens. Do you need unlocked bootloader to do this?
Click to expand...
Click to collapse
omg, yes
rmn.br said:
omg, yes
Click to expand...
Click to collapse
Lol, ok cheers.
Sent from my SM-G973F using Tapatalk