Related
Here is your unofficial TWRP
Please report all issues on my github so I can track them
Download the update!
Merged in TWRP 3.0.0.0
Fixed the time issue Bug in LG's kernel (however daylight savings time does not work when set on/off in recovery)
3.0.0.0
https://www.androidfilehost.com/?fid=24407100847293244
md5: f7c84c5328fb073a1a57fb75dc70191a
2.8.7.1
https://www.androidfilehost.com/?fid=24269982086988199
md5: 736456843ecaa2b65fbbb749008e1ff3
2.8.7.0
https://www.androidfilehost.com/?fid=24052804347853160
md5: f6d38b88b51d8cc39635534b559f719f
This requires you to have an unlocked bootloader which will wipe data if you have not unlocked already.
Recovery does take some time to boot It has taken up to 45 seconds for the TWRP curtain to show for me
To get to bootloader without adb:
Turn device off
Hold Vol Down
Insert USB plug while plugged into your PC
Hold Vol Down until fastboot pops up
Instructions:
If you have issues with adb or fastboot follow this post: HERE
If bootloader is unlocked:
reboot into bootloader
Code:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
If your bootloader is locked:
enabled developer options
in developer options "Enable OEM unlock"
reboot into bootloader
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
Known issues:
You get to see that it's not truly 2 displays
Time is not saved from Android to Recovery
Display does not turn off when it times out
TheJesus said:
I've messaged @KAsp3rd to include it in his OP.
ONLY PERFORM IF YOU HAVE ALREADY FLASHED TWRP AND CREATED AN EXTERNAL BACKUP!!!
1. Hold Volume Down
2. Hold Power button until you see LG screen
3. Release Power button and then rehold Power button
4. Follow on-screen prompts to perform a Factory Reset (If you have TWRP, this should not actually factory reset, but there has been one case of it doing it, that's why I suggest keeping a copy of your backup on your computer), may take a minute to boot into TWRP
5. Enjoy TWRP without fastboot
EDIT: On hold until verified on latest TWRP/more devices.
Click to expand...
Click to collapse
Device tree is here https://github.com/KAsp3rd/android_device_lge_h901
Compiled using omnirom 5.1 with 6.0 bootable/recovery
Get superSU from chainfire http://download.chainfire.eu/supersu
Thanks to @TheJesus @shabbypenguin @Dees_Troy @_that @bigbiff @helicopter88 @savoca @autoprime and anyone I've forgotten.
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
I get the same thing
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
Did you reboot to bootloader and fastboot flash recovery "img"?
re-read the op
adb reboot bootloader
then do the fastboot commands
KAsp3rd said:
Did you reboot to bootloader and fastboot flash recovery "img"?
Click to expand...
Click to collapse
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
I'm currently using Minimal ADB and Fastboot [8-28-15] to push commands.
geeserver said:
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
Click to expand...
Click to collapse
Flashing stock.img myself to make sure
same issues here also
Mine worked first try... I personally change the recovery img file's name to recovery.img, but other than that I use the same commands.
yeah, mine has the android open door with "no command" under it
KAsp3rd said:
Flashing stock.img myself to make sure
Click to expand...
Click to collapse
I can't push stock.img from fastboot. Reading from mickeyinid post in that thread, "Make sure you have the newest fastboot binary or it won't flash the system.img" It has a cap at 53MB but the filesize for system.img is 4.2GB.
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Didn't catch that one shabby thanks for pointing it out. I'll update op
this worked. Thanks!!
and thank you so much @KAsp3rd for this recovery
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Once I put in the fastboot boot twrp-2.8.7.0-h901.img command, I heard the computer disconnect and it took more like a minute or a minute in a half but it worked. Then I flashed SuperSU and now I'm ROOTED!!! Thanks!!!!
All rooted. Thank you @KAsp3rd!!
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
that worked. TWRP installed and rooted. FYI it does take a little time to boot into TWRP with the fastboot command and normal also.
Thanks for the help all
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Xposed
Can you flash xposed in this recovery?
huynh727 said:
Can you flash xposed in this recovery?
Click to expand...
Click to collapse
Yes. I have it. Use the arm64 for Lollipop version. It does however break the second screen occasionally (it FC's when I get/make a phone call, but that's it). BUT it has RootCloak which lets me use Android Pay while rooted
Success! The whole process was very easy and worked the first time! Thanks for posting this!
Hi All,
I've deodexed the systems from 34.0.A.2.292 and 34.0.A.2.301.
How to use:
1. download zip
2. flash with flashfire or custom recovery
3. enjoy
Download links:
F5121_34.0.A.2.292_Deodexed.zip
F5121_34.0.A.2.301_Deodexed.zip
nice work bro
Pandemic said:
nice work bro
Click to expand...
Click to collapse
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.
infected_ said:
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.
Click to expand...
Click to collapse
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.
mstrack said:
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.
Click to expand...
Click to collapse
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.
infected_ said:
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.
Click to expand...
Click to collapse
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...
mstrack said:
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...
Click to expand...
Click to collapse
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?
kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
Click to expand...
Click to collapse
yes, got it, thx.
edit: i used flashtool
kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?
Click to expand...
Click to collapse
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.
infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? ok then.
Click to expand...
Click to collapse
Thanks for the tip will try it out tonight and report back!
kistigun said:
Thanks for the tip will try it out tonight and report back!
Click to expand...
Click to collapse
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img
infected_ said:
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img
Click to expand...
Click to collapse
will do, just wondering: what files/folders of the ramdisk are needed for TWRP? I ask because I use a kernel with allready a modified ramdisk(DM-verity/Sony RIC/DRM-fix/SU?busyBox) so I want to know what files need to be replaced to implements TWRP
infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.
Click to expand...
Click to collapse
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?
kistigun said:
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?
Click to expand...
Click to collapse
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0
infected_ said:
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0
Click to expand...
Click to collapse
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?
kistigun said:
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?
Click to expand...
Click to collapse
delete the symlink and recreate it:
ln -s /sbin/init_sony init
infected_ said:
delete the symlink and recreate it:
ln -s /sbin/init_sony init
Click to expand...
Click to collapse
Sorry it took me a while, had to set-up a new linux enviorment. Repacked kernel, it boots but sony init still doesnt work
Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"
KOALAaufPILLEN said:
Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"
Click to expand...
Click to collapse
No, it only flashes the deodexed files so it does not contain a ´full rom´
Could you make a full rom ? Cause right now i must use aosp rom but there are some features missing like sony themes and others
Ok so.....
Was unlocked with dirtysanta and istalled stocK_ls997 ..
long story short , friend had this phone, got ota and installed (don't ask me why) , so now phone stuck in twrp
seems like bootloader is locked out , can't access adb to unlock it again as i only have access to twrp and fastboot...
Can't boot to OS because of locked booloader...
Had similar situation before and managed to unlock bootloader again , but don;t remember how...
Can you guys help me with that?
++++++++++++++++++++ FIX ++++++++++++++++++++++
jkjambo said:
Finally !!!
Was able to boot to system.
Reinstalled TWRP , but not the one in dirtysanta thread, installed beta twrp for sprint version from this thread and then wipe/format and then installed deoxeded rom from same thread...
http://www.androidinfotech.com/2016/11/root-lg-v20-sprint-ls997-nougat-install-twrp.html
twrp link
http://redirect.viglink.com/?format... Install TWRP - Android Infotech&txt=Download
Click to expand...
Click to collapse
You're in luck
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
The problem is that there is no kdz or tot file for sprint version
wow.. you just need to delete the fota, misc, and caches.
its a common issues with attempting a ota on non oem firmware.
delete the update package from misc and ur good.
Team DevDigitel said:
wow.. you just need to delete the fota, misc, and caches.
its a common issues with attempting a ota on non oem firmware.
delete the update package from misc and ur good.
Click to expand...
Click to collapse
No , seems like update locked bootloader..
I can access twrp and install any rom, but can't boot to the rom , because of locked bootloader....
twrp unmounts system parition itself.....
any more advices?????
If you are able to boot into TWRP you can easily flash the unlocked dirtysanta aboot.img through an adb shell with the dd commands
Hmm, nice catch...
Can you let me know dd command?
i've installed aboot.img with twrp img installer in boot partition, but still same
jkjambo said:
Hmm, nice catch...
Can you let me know dd command?
i've installed aboot.img with twrp img installer in boot partition, but still same
Click to expand...
Click to collapse
Copy the dirtysanta aboot.img into your adb folder & rename it to aboot-dv.img (just to avoid confusion)
Code:
adb push aboot-dv.img /
adb shell
dd if=aboot-dv.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
You might need to repeat step3 of the dirtysanta root method (depending on your variant & if boot needs patching)
Prowler_gr said:
Copy the dirtysanta aboot.img into your adb folder & rename it to aboot-dv.img (just to avoid confusion)
Code:
adb push aboot-dv.img /
adb shell
dd if=aboot-dv.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
You might need to repeat step3 of the dirtysanta root method (depending on your variant & if boot needs patching)
Click to expand...
Click to collapse
Thanks for help, but it's still same.
still locked bootloader and can't boot to os
jkjambo said:
Thanks for help, but it's still same.
still locked bootloader and can't boot to os
Click to expand...
Click to collapse
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Prowler_gr said:
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
I've wiped everything and formated data.
Will add your steps after that and will let you know
Prowler_gr said:
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
still same....
twrp unmounts system partition .....
I've tried bootloader unlock with manual but i'm getting stuck on this step
adb shell chmod 0777 /data/local/tmp/*
it says not a directory
jkjambo said:
still same....
twrp unmounts system partition .....
I've tried bootloader unlock with manual but i'm getting stuck on this step
adb shell chmod 0777 /data/local/tmp/*
it says not a directory
Click to expand...
Click to collapse
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Prowler_gr said:
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Click to expand...
Click to collapse
I'm not running exploit because of recovery, but for bootloader unlock. i think it causes twrp bootloop , as twrp isn't able to mount system partition after restart.
Maybe i'm wrong .. will give few more tries
Prowler_gr said:
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Click to expand...
Click to collapse
No joy ... still same ....
Don't know what to do
isn't there any fastboot flashable system or boot image or anything?
Finally !!!
Was able to boot to system.
Reinstalled TWRP , but not the one in dirtysanta thread, installed beta twrp for sprint version from this thread and then wipe/format and then installed deoxeded rom from same thread...
http://www.androidinfotech.com/2016/11/root-lg-v20-sprint-ls997-nougat-install-twrp.html
twrp link
http://redirect.viglink.com/?format... Install TWRP - Android Infotech&txt=Download
jkjambo said:
No joy ... still same ....
Don't know what to do
isn't there any fastboot flashable system or boot image or anything?
Click to expand...
Click to collapse
But that's what the aboot-dv.img is: an unlocked fastboot enabled bootloader.
Are you absolutely sure that you are using the aboot.img from dirtysanta??? If in any doubt re-download the dirtysanta zip, extract the aboot.img rename it to aboot-dv.img & re-follow my instructions.
[edit:] Happy you were able to resolve your issue!
You just need to do the vol down power button factory reset procedure to break the twrp bootloop.
Search it. The update didn't do anything to your phone but trigger the recovery boot switch. Factory reset will stop this and will not modify anything on your phone as it needs stock recovery and doesn't work with twrp.
Prowler_gr said:
But that's what the aboot-dv.img is: an unlocked fastboot enabled bootloader.
Are you absolutely sure that you are using the aboot.img from dirtysanta??? If in any doubt re-download the dirtysanta zip, extract the aboot.img rename it to aboot-dv.img & re-follow my instructions.
[edit:] Happy you were able to resolve your issue!
Click to expand...
Click to collapse
I downloaded it 2 or 3 times , even when i was 100% sure on first time
fastboot and twrp was working, but bootloader still says it's not unlocked.
Seems like problem was twrp itself.. i knew it had some problems because it wasn't for this specific model, but i was using it before for flashing same zip over and over... not quite sure why it stopped working (i've reflashed it also few times)
@midmadn
I've reflashed roms like 10 times with no luck , so factory reset was not a solution in my case . seems like update messed up someting in recovery .
Anyway solution is in the first post if anyone needs it
I want to root my moto g4 plus(unlocked bootloader and twrp flashed). Anyone knows how to root moto g4 plus. And i also want to know that how to increase battery backup after rooting(is it a myth).
@ADITYA_KUMAR this has been asked and explained many times and once more.
- Take Backup
- get Elemental-X kernel (see development section and download correct one )
- flash with TWRP
- get latest SuperSU : SuperSU
- now you can follow same guide of MM from step 5 : Guide
Don't Forget to Take Backup..
____Mdd said:
@ADITYA_KUMAR this has been asked and explained many times and once more.
- Take Backup
- get Elemental-X kernel (see development section and download correct one )
- flash with TWRP
- get latest SuperSU : SuperSU
- now you can follow same guide of MM from step 5 : Guide
Don't Forget to Take Backup..
Click to expand...
Click to collapse
How to take backup and restore it. I flashed twrp image. Before rebooting twrp works fine. But after rebooting i am not able to open twrp. I think it got removed.
ADITYA_KUMAR said:
How to take backup and restore it. I flashed twrp image. Before rebooting twrp works fine. But after rebooting i am not able to open twrp. I think it got removed.
Click to expand...
Click to collapse
What happens if you select Recovery from Bootloader ? Is it booting in Stock Recovery ?
In TWRP go to Backup and make backup of /system /data /boot.
If anything bad happens while flashing/Rooting then you can restore it.
The first time, you must open TWRP from the bootloader directly or the recovery gets overwritten.
For rooting, you can flash Magisk instead of flashing SuperSu. Other steps remain exactly the same.
____Mdd said:
What happens if you select Recovery from Bootloader ? Is it booting in Stock Recovery ?
In TWRP go to Backup and make backup of /system /data /boot.
If anything bad happens while flashing/Rooting then you can restore it.
Click to expand...
Click to collapse
When i booted into recovery mode. It shows no command.
ADITYA_KUMAR said:
When i booted into recovery mode. It shows no command.
Click to expand...
Click to collapse
That's stock Recovery, you need to flash TWRP again.
____Mdd said:
That's stock Recovery, you need to flash TWRP again.
Click to expand...
Click to collapse
I flashed twrp 2 times. But every time i restarted my phone it removed automatically.
ADITYA_KUMAR said:
I flashed twrp 2 times. But every time i restarted my phone it removed automatically.
Click to expand...
Click to collapse
Did you flashed TWRP and with the next command booted immediately into twrp?
strongst said:
Did you flashed TWRP and with the next command booted immediately into twrp?
Click to expand...
Click to collapse
Commands used:
Fastboot flash recovery name.img
It gives output as image not signed or corrupt.
After that i typed command fastboot reboot bootloader.
I open recovery mode. It opens twrp. But after i restart my phone. It automatically removes the twrp.
ADITYA_KUMAR said:
Commands used:
Fastboot flash recovery name.img
It gives output as image not signed or corrupt.
After that i typed command fastboot reboot bootloader.
I open recovery mode. It opens twrp. But after i restart my phone. It automatically removes the twrp.
Click to expand...
Click to collapse
This is your problem. You must open recovery from the bootloader menu the very first time. Or TWRP is overwritten with stock recovery. I don't know why that is. But that is how it is...
baunthiyal said:
This is your problem. You must open recovery from the bootloader menu the very first time. Or TWRP is overwritten with stock recovery. I don't know why that is. But that is how it is...
Click to expand...
Click to collapse
It means that i don't have to run the fasboot reboot bootloader command and after finishing the flashing i have to open the recovery mode directly?
Yes
ADITYA_KUMAR said:
It means that i don't have to run the fasboot reboot bootloader command and after finishing the flashing i have to open the recovery mode directly?
Click to expand...
Click to collapse
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.
baunthiyal said:
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.
Click to expand...
Click to collapse
I need to root my stock nougat( june version).What should i do after that.
I'll tell you what I did.
1. Flash Elemental Ex kernel. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2. Flash Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
baunthiyal said:
Reboot into bootloader.
Flash recovery - fastboot flash recovery twrp-xxx.img
Open recovery from bootloader menu (by using the volume and power buttons)
From there you can reboot and your recovery will work normally after this, most probably.
Click to expand...
Click to collapse
It didn't work. I flashed twrp. I opened recovery mode by using volume down to scroll to recovery mode and power button to select it. I booted in twrp mode and rebooted system from there. After that i power off my phone and tried to open twrp again, but it is showing no commands only. I didn't boot into twrp again.
ADITYA_KUMAR said:
It didn't work. I flashed twrp. I opened recovery mode by using volume down to scroll to recovery mode and power button to select it. I booted in twrp mode and rebooted system from there. After that i power off my phone and tried to open twrp again, but it is showing no commands only. I didn't boot into twrp again.
Click to expand...
Click to collapse
Try commands,
fastboot oem fb_mode_set
fastboot flash recovery name.img
Fastboot oem fb_mode_clear
Then directly boot into recovery,
Then again boot into recovery through twrp itself (there is option for it in reboot) or try anything.
Thank you guys i successfully rooted my moto g4 plus(xt1643)
Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks
Angelelz said:
Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks
Click to expand...
Click to collapse
Assuming youre rooted... Ive used the reboot app on my phone. I have a 1926-7 Moto G6 Plus. It will boot to fastboot, fast reboot, recovery, reboot system etc. Look around xda and see if someone has a good reboot app or else use GP. I actually had twrp flashed permanently to my phone but it would not back up so I have to redo it. Also the phones data was encrypted and I didnt know how to fix it. I hope that you are able to find something that works for you
You can boot into TWRP via terminal command without using a computer. Use the 'dd' command ( 'dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.backup.img' ) to take a backup of your boot.img. Than use 'dd' to overwrite boot with twrp and reboot to recovery (dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/boot)
Later to boot your phone as normal you only have to install your boot.img backup via TWRP.
now we can install a TWRP 3.3.0 ONLY ON DECRYPTED ROMS (the lastest Havoc, Resurrection Remix, AEX, Decendant, PixyOS are unencripted by default) for flashing magisk modules or mods but it will be overwrite when we flash/update our custom/stock rom:
https://drive.google.com/open?id=1CqzvBiEfk9xucXG8UemNZMhBxDCeSV0i
How to install it:
Put the donwloaded TWRP on your plataform tools folder and in your internal/sd storage.
Boot the same TWRP (fastboot boot TWRP.img)
Go to ADVANCED and select Install Ramdisk Recovery
Check backup boot box( in case something goes wrong just restore your boot partition)
Swipe and wait until finish.
Reboot
If every reboot finishes in twrp booting just flash magisk and youll be able to boot into system.