Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- Sdcard works
Download:
TWRP
To Flash the TWRP:
Code:
fastboot flash recovery twrp-RMX1921-20191018.img
Then reboot in TWRP manually.
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thesprintster/device_realme_RMX1921/commits/android-9.0
Precompiled Stock Kernel in use
Credits:
Thanks to other testers for the tests and the support
Created 2019-10-17
XDA:DevDB Information
[RECOVERY][3.3.x][RMX1921] TWRP, Tool/Utility for the Realme XT
Contributors
thesprintster, mauronofrio
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2019-10-17
Last Updated 2019-10-17
Reserved
Thanks sooo much bro, great work :good::good::good::good::good::good:
Hey thanks for the great work. Can you please provide the method you used for bootloader unlock... I'm trying from past 2 hours but I'm not able to find and drivers for my realme xt.
naushad.016 said:
Hey thanks for the great work. Can you please provide the method you used for bootloader unlock... I'm trying from past 2 hours but I'm not able to find and drivers for my realme xt.
Click to expand...
Click to collapse
Just search in the realme community
They made it official
sandy_9 said:
Just search in the realme community
They made it official
Click to expand...
Click to collapse
Unlock Bootloader Tutorial for realme XT
https://c.realme.com/in/post-details/1184740422732218368
Okay, I got the official method in realme community, but there is no ADB drivers on that post. If anyone have ADB drivers for realme xt please share it here. It will be great help. So far I've tried a few drivers which claimed to work on it.
naushad.016 said:
Okay, I got the official method in realme community, but there is no ADB drivers on that post. If anyone have ADB drivers for realme xt please share it here. It will be great help. So far I've tried a few drivers which claimed to work on it.
Click to expand...
Click to collapse
Use this link for ADB drivers installation.
https://www.xda-developers.com/install-adb-windows-macos-linux/
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
naushad.016 said:
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
Click to expand...
Click to collapse
Hi please have a look on this link. Haven't tried my own but i think this should work.
https://forum.xda-developers.com/showpost.php?p=80447545&postcount=17
ashman8123 said:
Hi please have a look on this link. Haven't tried my own but i think this should work.
https://forum.xda-developers.com/showpost.php?p=80447545&postcount=17
Click to expand...
Click to collapse
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
Click to expand...
Click to collapse
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
Click to expand...
Click to collapse
I think going to a service centre is the only available option.
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
I think going to a service centre is the only available option.
Click to expand...
Click to collapse
Sad to hear. If it serious concern try to go to service center as you think.
But as per my previous experience .. if you did all things carefully, you will not be in such a serious condition. Try to search some more options before you go to service center, if you dare.........otherwise please go on to service center.
naushad.016 said:
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
Click to expand...
Click to collapse
100% will work. Move vbmeta.img to adb directory, boot into fastboot and type the command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
There is no way to give a link to vbmeta.img
Shurx said:
100% will work. Move vbmeta.img to adb directory, boot into fastboot and type the command:
There is no way to give a link to vbmeta.img
Click to expand...
Click to collapse
You have BL relocked ?
naandha114 said:
You have BL relocked ?
Click to expand...
Click to collapse
Bootloader unlocked. Stock firmware showed a breakdown. I flashed vbmeta.img and the phone booted.
Shurx said:
Bootloader unlocked. Stock firmware showed a breakdown. I flashed vbmeta.img and the phone booted.
Click to expand...
Click to collapse
I have unlocked....now I want to relock BL
naandha114 said:
I have unlocked....now I want to relock BL
Click to expand...
Click to collapse
In technical support they answered that a brick is possible.
Shurx said:
In technical support they answered that a brick is possible.
Click to expand...
Click to collapse
Phone will brick for sure.
Thankx for the twrp, but in realme forum they r saying after bootloader unlock we will not be able to use fingerprint scanner and ota updates ?, is there any fix ?
thank you it works!!!
Related
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
Thread Closed
Thread Closed
I don't know what SKU means, but I'm assuming this doesn't work on the XT1763 variant (MediaTek), right?
lucasdeeiroz said:
I don't know what SKU means, but I'm assuming this doesn't work on the XT1763 variant (MediaTek), right?
Click to expand...
Click to collapse
Setting < about phone < hardware info < sku ????
It works on any mediatek variant of e4.
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
yashburshe007 said:
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
Click to expand...
Click to collapse
Did you name the file "twrp.img"?
madbat99 said:
Did you name the file "twrp.img"?
Click to expand...
Click to collapse
No. The name of the file is twrp. Extension in .I'm
I just took the file out of the .zip given by op and flashed. But after flashing if I go into recovery mode, it just gives me "no command" screen. When I directly boot into the file, my device restarts to system
yashburshe007 said:
No. The name of the file is twrp. Extension in .I'm
I just took the file out of the .zip given by op and flashed. But after flashing if I go into recovery mode, it just gives me "no command" screen. When I directly boot into the file, my device restarts to system
Click to expand...
Click to collapse
Make sure the file is named twrp.img because that's what you're typing in your command.
Fastboot flash recovery twrp.img
Or fastboot boot recovery twrp.img
So either rename the file or change your command to match whatever the filename is of the recovery image you're trying to flash.
You're just telling it to flash, you have have to tell it which partition to flash it to. It's not fastboot flash twrp.img (especially if that's not the filename) its fastboot flash recovery twrp.img but the last part (twrp.img) has to match what the actual file is named.
Also make sure fastboot can find it.
madbat99 said:
Make sure the file is named twrp.img because that's what you're typing in your command.
Fastboot flash recovery twrp.img
Or fastboot boot recovery twrp.img
So either rename the file or change your command to match whatever the filename is of the recovery image you're trying to flash.
You're just telling it to flash, you have have to tell it which partition to flash it to. It's not fastboot flash twrp.img (especially if that's not the filename) its fastboot flash recovery twrp.img but the last part (twrp.img) has to match what the actual file is named.
Click to expand...
Click to collapse
Reread my comment. .img is put not because it's in the name of the file but because it's the extension. I've rooted my redmi 2 before using fast boot and I what I'm doing. If I rename the file twrp.img then I would have to type "fastboot flash recovery twrp.img.img"
yashburshe007 said:
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
Click to expand...
Click to collapse
show us the fastboot command window
Francesco Franz said:
show us the fastboot command window
Click to expand...
Click to collapse
nah, i got it to work. But I have a new problem now.... check the questions thread :crying::crying::crying:
who built this recovery? & if you built it please put version and changelog etc
* please credit the maker if it is not your recovery and put link to original source
Help Boot Loop
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
people should stop flashing this recovery using this guide ....* just my opinion ...
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
Max Teodoro said:
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
Click to expand...
Click to collapse
read this thread from the top to fix your device and press the thanks button ..read it ALL
https://forum.xda-developers.com/mo...woods-xt1762-build-nma26-42-75-t3688609/page5
read this too where I explained to another user bricking from this thread
https://forum.xda-developers.com/moto-e4/help/help-boot-stuck-twrp-t3713486
Max Teodoro said:
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
Click to expand...
Click to collapse
disable system verification. So you can boot into system like installing no-verity zip can help you
KevMetal said:
people should stop flashing this recovery using this guide ....* just my opinion ...
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
Click to expand...
Click to collapse
Even i can't figure whats the problem with you . There is nothing bad with installation guide it is same as older ones. The recovery is from RR zip file. Its a working recovery and for daily use. I really don't know if SKU versions matters. Its the variant what we need. Confirm that you have tried everything and the above twrp is not fit into your expectations . I have flashed several roms with this recovery.
Francesco Franz said:
Even i can't figure whats the problem with you . There is nothing bad with installation guide it is same as older ones. The recovery is from RR zip file. Its a working recovery and for daily use. I really don't know if SKU versions matters. Its the variant what we need. Confirm that you have tried everything and the above twrp is not fit into your expectations . I have flashed several roms with this recovery.
Click to expand...
Click to collapse
i don't have any expectations. i just think it is correct to state where you find the files you post. if the people brick using the files in your thread reply and help them ..or put a message in your OP with correct steps . a lot of noobs are coming for help after this thread ( that is not my doing , my expectation or my problem but i try to help them )
i don't know why you mirror other people's work without putting source and credits and without mirroring correct instructions but you go to other threads with full expectations of extra screenshots and changelogs and versions and sources and leave your suggestions
i think we are working around your expectations . keep the files here and help the people i enjoy that , that is cool for xda . but always tell the truth and give credit .
magisk and xposed official is working but you don't change your thread to tell the truth , you put other devs work without credit or thanks .
KevMetal said:
read this thread from the top to fix your device and press the thanks button ..read it ALL
https://forum.xda-developers.com/mo...woods-xt1762-build-nma26-42-75-t3688609/page5
read this too where I explained to another user bricking from this thread
https://forum.xda-developers.com/moto-e4/help/help-boot-stuck-twrp-t3713486
Click to expand...
Click to collapse
boot.zip & recovery.zip are stock file with no change theirs nothing new in it that you have to flash no-verity zip in a half custom and half stock Rom. i already dumped whole firmware through miracle tool. Theirs a guide already available in this forum on *how to dump firmware through miracle tool*. So they can extract their own.
here i help this guy PM from your thread after helping two other guys in last two days if you like i post screenshot here ...why you didn't help them bricking from your post
i don't have expectations ..these guys had expectations from your post but you expect other guys to help them fix or just to leave them hanging ..anyway peace and prosperity and i will stay away from your posts bro :good:
enjoy XDA but maybe you can see one day you request a lot stuff from other guys threads but just give nothing you request from other guys in your posts ..its just a thought ..you don't need to agree or change your ways
KevMetal said:
i don't have any expectations. i just think it is correct to state where you find the files you post. if the people brick using the files in your thread reply and help them ..or put a message in your OP with correct steps . a lot of noobs are coming for help after this thread ( that is not my doing , my expectation or my problem but i try to help them )
i don't know why you mirror other people's work without putting source and credits and without mirroring correct instructions but you go to other threads with full expectations of extra screenshots and changelogs and versions and sources and leave your suggestions
i think we are working around your expectations . keep the files here and help the people i enjoy that , that is cool for xda . but always tell the truth and give credit .
magisk and xposed official is working but you don't change your thread to tell the truth , you put other devs work without credit or thanks .
Click to expand...
Click to collapse
even i am a bit busy these days. i don't have my pc right now so i can update my thread. I already thanked the official thread. Some e4 users randomly throw pm everytime to upload a working recovery. I did. Ok so you want to be a king in this forum. Looks like xposed and twrp threads bother you. i will take these thread down.
After a year of hard work, @steadfasterX has finally unlocked our device! Hopefully we'll get some new roms soon. Full thread is here: https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451
Edit: We are currently able to run any custom rom for H811 on our device! One thing is that we must do the modem flash in TWRP that steadfaster mentions in his FAQ.
Edit 2: Currently only stock Lollipop or stock Marshmallow will run on VS986 with everything working. AOSCP and other custom roms will boot but you will not pull the correct APN for Verizon and therefore will have data but no cell service including MMS or voice calls. You must have the stock MM bootloader stack flashed after you go through the UsU process for everything to work correctly and the stock MM modem.
@fates13,
I know you're trying to get Nougat working on your VS986 and it's not 100% working yet.
I suggest people wait until you get things resolved if they rely on their VS986 as their daily phone.
Please post an update here once you think everything is working. The other thread has a lot of posts since it covers other G4 models too.
Thank you
@fates13,
Were you able to get your VS986 to the point of everything worked after UsU unlock and ROM installation?
divineBliss said:
@fates13,
Were you able to get your VS986 to the point of everything worked after UsU unlock and ROM installation?
Click to expand...
Click to collapse
Yes but only stock MM works properly with data and cell. This can probably be fixed by a proper rom developer for our phone. Advanced calling also doesn't work properly so just waiting until @steadfasterX has time to make a UsU patched kernel for stock MM.
fates13 said:
Yes but only stock MM works properly with data and cell. This can probably be fixed by a proper rom developer for our phone. Advanced calling also doesn't work properly so just waiting until @steadfasterX has time to make a UsU patched kernel for stock MM.
Click to expand...
Click to collapse
has anyone got stock MM rooted yet? tried with twrp but I soft bricked it
Was that with UsU on a VS986? How did you try to root it?
ANDROID2468 said:
has anyone got stock MM rooted yet? tried with twrp but I soft bricked it
Click to expand...
Click to collapse
divineBliss said:
Was that with UsU on a VS986? How did you try to root it?
Click to expand...
Click to collapse
yes and I tried rooting with update-superSU.zip
i got stock MM rooted with magisk!!!!
Attempted to root using @steadfasterX's new tool and I was able to do a partial root? My phone would get stuck try to boot the img, however it was able to achieve an unsecured bootloader
wft300001 said:
Attempted to root using @steadfasterX's new tool and I was able to do a partial root? My phone would get stuck try to boot the img, however it was able to achieve an unsecured bootloader
Click to expand...
Click to collapse
just do magisk it worked for me.
ANDROID2468 said:
just do magisk it worked for me and what tool are you talking about?
Click to expand...
Click to collapse
I used SALT, the tool recently released
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
ANDROID2468 said:
just do magisk it worked for me and what tool are you talking about?
Click to expand...
Click to collapse
I used SALT developed by @steadfasterX
wft300001 said:
I used SALT, the tool recently released
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
I used SALT developed by @steadfasterX
Click to expand...
Click to collapse
i sorry I did not read your question right I thought I saw root tool did you get magisk install?
ANDROID2468 said:
i sorry I did not read your question right I thought I saw root tool did you get magisk install?
Click to expand...
Click to collapse
I wasn't able to
Are you able to boot to twrp.
If your still stuck on boot.img go to your salt back ups is located in the home folder and right click in the folder and click open in terminal put your phone in fastboot mode type in terminal "fastboot flash boot boot.img" and after that "fastboot reboot" and see if your phone boots up if you don't have the salt backup let me know
ANDROID2468 said:
Are you able to boot to twrp.
If your still stuck on boot.img go to your salt back ups is located in the home folder and right click in the folder and click open in terminal put your phone in fastboot mode type in terminal "fastboot flash boot boot.img" and after that "fastboot reboot" and see if your phone boots up if you don't have the salt backup let me know
Click to expand...
Click to collapse
How exactly did you install TWRP? Or if you solely used magisk, how did you flash the patched_boot.img?
I was asking you about TWRP to see if you installed it. You flash all the files in fastboot. You get into fastboot by unplugging the battery wait 4 seconds plug it back in hold volume down and plug your phone in to your computer you should be in fastboot mode. You can download TWRP from the unlock Page. I will upload the pach boot.img and paste the link for TWRP later because I'm not at my computer right now. Be careful NOT to flash the aboot.img you should only flash the boot.img (once I upload it) and the recovery.img right now
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
Tros13 said:
How exactly did you install TWRP? Or if you solely used magisk, how did you flash the patched_boot.img?
Click to expand...
Click to collapse
And if you are still confused I will make a video on how to root later
ANDROID2468 said:
I was asking you about TWRP to see if you installed it. You flash all the files in fastboot. You get into fastboot by unplugging the battery wait 4 seconds plug it back in hold volume down and plug your phone in to your computer you should be in fastboot mode. You can download TWRP from the unlock Page. I will upload the pach boot.img and paste the link for TWRP later because I'm not at my computer right now. Be careful NOT to flash the aboot.img you should only flash the boot.img (once I upload it) and the recovery.img right now
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
And if you are still confused I will make a video on how to root later
Click to expand...
Click to collapse
Ah, different person than you were talking to before. The way I read your post, it sounded like maybe you figured out a way to sideload (if that is the correct term) the patched boot image that magisk makes without the part of the UsU method that causes "Once you go this way - there is no way back! SERIOUSLY. The only way to make the device exactly like before is replacing the mainboard. If you're scared: good." Maybe something like this: ?
https://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Was just looking into my options for if I should wait until a method comes out that doesn't make a permanent alteration or if I should just go ahead and take the plunge with UsU. Your thoughts on whether that change that is made could affect me badly in the long run?
Tros13 said:
Ah, different person than you were talking to before. The way I read your post, it sounded like maybe you figured out a way to sideload (if that is the correct term) the patched boot image that magisk makes without the part of the UsU method that causes "Once you go this way - there is no way back! SERIOUSLY. The only way to make the device exactly like before is replacing the mainboard. If you're scared: good." Maybe something like this: ?
https://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Was just looking into my options for if I should wait until a method comes out that doesn't make a permanent alteration or if I should just go ahead and take the plunge with UsU. Your thoughts on whether that change that is made could affect me badly in the long run?
Click to expand...
Click to collapse
sorry about that the only way to root the latest FW is to unlock the bootloader. as long as you flow the guide and read carefully you shud be fine and if it's too scary just downgraded to LP and root that way (look on xda Verizon G4 general tab)
Has any one got calling and texting working on any costum rom for vs986?
Probably a dumb question, but I'm on 13b rooted. I read through the unlock thread and it mentions MM is required and anti rollback <=2. My ARB value is currently 2. Can I just use LGUP to flash stock MM? Will this preserve my ARB value?
TWRP Recovery 3.2.1-0 for Asus Zenfone 4 Selfie Lite/ Selfie
Instructions :
Update your software firmware to 14.0400.1803.192-20180302 [IMPORTANT]
Then Unlock your bootloader using this tool:
http://dlcdnet.asus.com/pub/ASUS/Ze...47.1956599541.1522883646-782411292.1521405254
After unlocking your bootloader, Flash this twrp via fastboot
type fastboot flash recovery [recoveryname].img
Twrp link (UPDATED AS OF SEPTEMBER 13, 2018 : https://mega.nz/#!Zk4j0SiY!aDzVa43whmy7GNz6Ww8qY-xrbIC1TmRWjGZcliU_l7w
Big Credits to xda user shakalaca for this twrp
and also me for testing and confirming that this twrp is working at its stable!
XDA:DevDB Information
RECOVERY, Tool/Utility for the Asus ZenFone 4 Selfie, Selfie Pro
Contributors
Rempoiiii, shakalaca, Rempoiiii
Version Information
Status: Stable
Created 2018-04-04
Last Updated 2018-04-04
Thanks. Im hoping for u guys give us some rooting procedure for zd553kl ?
Please upload the stock recovery for selfie lite . I want to flash stock firmware.
Jhezbasacaaa said:
Thanks. Im hoping for u guys give us some rooting procedure for zd553kl
Click to expand...
Click to collapse
All you need to do is to get twrp installed in ur device and flash super su zip.
after entering the string "fastboot flash recovery....
gets blocked on waiting for devices.. help me
messicano said:
after entering the string "fastboot flash recovery....
gets blocked on waiting for devices.. help me
Click to expand...
Click to collapse
Make sure you have turned on adb mode in your phone and you have authorized the computer for accessing adb and fast boot.
Or may be you didn't go to fastboot mode of your phone.
You need to press and hold volume up+power button until your phone reboots. Then only you can access fastboot.
I have unlocked the bootloader,then I activated debug mode. i press and hold volume up+power button and i entered in fastboot mode.
. i installed adb driver and program. I opened cmd and I wrote :
cd..
cd adb
adb devices
fastboot flash recovery (name recovery).img
when the writing appears "waiting for devices" does not continue with installation
resolved... my usb don't work good. i used other pc
---------- Post added at 05:33 PM ---------- Previous post was at 05:14 PM ----------
Where i can found the stock recovery?
i found recovery stock.. i flashed it and i flashed firmware UL-ASUS_X00LD-WW-14.0400.1710.168-user. Than i found relock bootloader app so i have ota upgrade
Stock recovery
Where u found stock recovery bro send me also... Stock recovery for zb553kl..
Ho estratto la recovery dal firmware originale ma non so come inviare a te
messicano said:
resolved... my usb don't work good. i used other pc
---------- Post added at 05:33 PM ---------- Previous post was at 05:14 PM ----------
Where i can found the stock recovery?
Click to expand...
Click to collapse
For that you now need to use zenfone flash tool coz you didnt make a back up of your recovery.
For that you needed to first use this cmd.
Code:
fastboot boot recovery.img
This would run twrp temporarily and you could make a backup of your stock recovery. Then to permanently install stock recovery you needed to do the same you did.
Now, except using zenfone flash tool you can only ask a friend if he can give u the stock recovery if he has unlocked bootloader and didnt install twrp..
messicano said:
Ho estratto la recovery dal firmware originale ma non so come inviare a te
Click to expand...
Click to collapse
u can upload here or upload that to Google drive and share the link here or inbox me.... I need it
kanhaiya1.kk said:
u can upload here or upload that to Google drive and share the link here or inbox me.... I need it
Click to expand...
Click to collapse
Actually I am not willing to unlock my phone's bootloader right now. So I cant give it to you. But you can get it by flashing your phone with stock rom...the very first one and flash it using zenfone flash tool.
Devc100 said:
Actually I am not willing to unlock my phone's bootloader right now. So I cant give it to you. But you can get it by flashing your phone with stock rom...the very first one and flash it using zenfone flash tool.
Click to expand...
Click to collapse
how can i flash stock rom?
I hv unlocked bootloader and flashed twrp. I hv no stock recovery
If u know any method then plz help me
kanhaiya1.kk said:
how can i flash stock rom?
Check this link.
Asus Zenfone Flash Tool
Click to expand...
Click to collapse
Devc100 said:
kanhaiya1.kk said:
how can i flash stock rom?
Check this link.
Asus Zenfone Flash Tool
Click to expand...
Click to collapse
it works when u hv stock recovery.. I hv not
Click to expand...
Click to collapse
If you want to flash the stock rom I suggest you do it with adb sideload because I noticed that if you flash with stock recovery with "upgrade from sd card" ,when the phone is rebooted it is very slow.
This is the link with stock recovery:
https://drive.google.com/open?id=1NZ-dsUGB-c-qdLgeZW8JdfTJ1AYlOzbF
kanhaiya1.kk said:
Devc100 said:
it works when u hv stock recovery.. I hv not
Click to expand...
Click to collapse
The flash tool will flash the stock rom and in turn will bring back stock recovery.
Click to expand...
Click to collapse
I flashed before stock recovery with adb and then flashed the rom
1. App unlock bootloader: https://dlcdnets.asus.com/pub/ASUS/...SIGNED_UnlockTool_9.1.0.10_190702_fulldpi.apk
2.Rom: https://drive.google.com/folderview?id=1HxSqpE83FW1U_k8WxCfaTkMUEAbS2QH-
In folder, file boot.img patched to root, no bootloop and wifi working.
3. Minimal ADB: https://androidfilehost.com/?fid=746010030569952951
Step:
S1. Unlock bootloader by app unlock
S2.
a. Install Minimal ADB, copy 21 file .img to C:\Program Files (x86)\Minimal ADB and Fastboot
b. Flash 21 file img in fastboot mode (power + volumeup) using usb type C side of ROG Phone):
Run cmd-here.exe, command:
fastboot flash ***.img (*** same with name 21 file img, do not rename file)
EX: fastboot flash system system.im
fastboot flash vendor vendor.img
Boot in to recovery mode and wipe data/factory reset then reboot system!
Done.
Sorry for my poor English
Mod edit: Deleted!
Whaaaaaaaaaaaaaaaaaaaaat - if this is real, awesome job.
Damnnn good..but i'm afraid to try it
Could u explan more
After this ww rom will be installed? What about upgrade?
I mean can i do future update once in convert to ww rom ?
A Video would be nice (not doubting that this simple guide doesn't work) but to proof that indeed this method works) someone please be kind to post a video.
also, does flashing this WW ROM deletes all personal data? or does it flash like an update retaining data?
wow!!
is it works??
and is it without root??
Will OTA updates work on this? Also, could you rewrite the guide some parts are a bit confusing
It works. No OTA from now on though, without a patched boot.img the phone will always go into a bootloop. Some people have reported dead camera after WWE conversion.
"Some people have reported dead camera after WWE conversion. "
Is there more infomation about this? forum link or screenshot?
Thanks.
inspiron2 said:
It works. No OTA from now on though, without a patched boot.img the phone will always go into a bootloop. Some people have reported dead camera after WWE conversion.
Click to expand...
Click to collapse
In my tele, 2 member rp dead camera, they reflash rom CN then reflash WW, evething ok expect setting theme not working
Can someone state the major differences between the two roms?. I don't see the point of losing OTA and warranty unless you need the stock UI, other than that i don't see any advantages. By the way can someone confirm the call recording option is still there with the WW Rom.
Rashad83 said:
Can someone state the major differences between the two roms?. I don't see the point of losing OTA and warranty unless you need the stock UI, other than that i don't see any advantages. By the way can someone confirm the call recording option is still there with the WW Rom.
Click to expand...
Click to collapse
Yes Please, I Would also like to know the major differences..
Just to evaluate whether losing OTA is worth going to WW Rom.
Hello Guys, I messed up as I did not unlock bootloader first before flashing it from fastboot. Now I have a bootloop. Can anyone help me how to reflash CN. I have a lock bootloader. Thank you very much.
Unlocking BL also voids the Widevine L1 DRM btw, proceed at your own risk.
Can anyone help me how to unlock the bootloader via fastboot since I cannot get in the software as I have a bootloop. I greatly appreciate it as I have been figuring out this for the past 5 hours. Thank you.
tzdu25 said:
Can anyone help me how to unlock the bootloader via fastboot since I cannot get in the software as I have a bootloop. I greatly appreciate it as I have been figuring out this for the past 5 hours. Thank you.
Click to expand...
Click to collapse
You cannot unlock without the app. Hold the power and volume up key when the phone boots up until you enter the bootloader menu then using the volume keys navigate to recovery option from there just do a factory reset.
Hello Rashad83, I went to recovery and did a factory reset,but it still bootloop. I have a tencent ROG phone II model.
---------- Post added at 09:41 AM ---------- Previous post was at 09:40 AM ----------
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
https://photos.app.goo.gl/XVSLyFfQ7VeWKFSM8
tzdu25 said:
Hello Rashad83, I went to recovery and did a factory reset,but it still bootloop. I have a tencent ROG phone II model.
---------- Post added at 09:41 AM ---------- Previous post was at 09:40 AM ----------
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
Click to expand...
Click to collapse
What did you do to get the bootloop in the first place, if you don't mind me asking?
I tried fastboot flash vendor vendor.img then it says parse error due to lock state, then after that I rebooted it then it just bootloop.
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
dungnghien said:
In my tele, 2 member rp dead camera, they reflash rom CN then reflash WW, evething ok expect setting theme not working
Click to expand...
Click to collapse
How did they reflash ROM CN. I am stuck at bootloop with locked bootloader. I can only do fastboot. Any help is greatly appreciated. Thank you.
abunhyan said:
Could u explan more
After this ww rom will be installed? What about upgrade?
I mean can i do future update once in convert to ww rom ?
Click to expand...
Click to collapse
just flash newer version ww firmware. Data will keep. a little bit inconvenience that no OTA. but you will always have root (use magisk manager patch the boot.img).