Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
This works with the new bootloader setup for the M9?
Captain_Throwback said:
This works with the new bootloader setup for the M9?
Click to expand...
Click to collapse
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.
The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.
How
niekie73 said:
The program stops on my windows7 x64 laptop
It install the drivers and show online but if i choose Get tooken ID my phoon reboots and after that the program stops.
sorry for my bad english
now i tried to push a file and that works, i got allready my token and unlocked different way.
Click to expand...
Click to collapse
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...
kaw900r said:
SO how did you get token and unlock? Get my phone Tuesday so trying to find out how to get this done before it gets here...
Click to expand...
Click to collapse
I used this one
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?
DroidShift79 said:
Any chance you can add some sort of extracting files from twrp backup and an deodex function to the tollkit?
Click to expand...
Click to collapse
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.
WindyCityRockr said:
I can look into it, but any features I add to the toolkit would have to be compatible with all of the devices I support, which is over 90 now. It may not work with every device correctly.
Click to expand...
Click to collapse
doesn't work. won't flash twrp. and my phone is unlocked.
stargaterules said:
doesn't work. won't flash twrp. and my phone is unlocked.
Click to expand...
Click to collapse
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.
NaitsirkC said:
Can confirm, unlocked using htcdev.com and flashed TWRP the old fashioned way (fastboot flash recovery twrp.img) and received this message:
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 0.945s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.968s
So it looks like we might need s-off first? That would suck.
Click to expand...
Click to collapse
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.
stargaterules said:
Yup, that's exactly what I get and yes, need s off first. So we gotta wait.
Click to expand...
Click to collapse
Actually I misspoke. In bootloader mode it says that, but in download mode, the one with the black background instead of the white background, it works like a charm! That's a relief.
What works like a charm? It's not letting me install recovery because s is on. How did you get past that?
stargaterules said:
What works like a charm? It's not letting me install recovery because s is on. How did you get past that?
Click to expand...
Click to collapse
It's supposed to be in download mode, it works just fine then. Manually choose download mode not bootloader and it works
WindyCityRockr said:
The toolkit uses the official HTC Dev bootloader unlock, official TWRP, and latest SuperSU, so I assume it does, unless extra steps are needed.
Click to expand...
Click to collapse
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
awesome. it works. maybe add the info about device needing to be in download mode so people don't get confused. the program reboots the device into bootloader.
Will the program be updated?
Captain_Throwback said:
Recovery must be flashed while in download mode on the M9, not in bootloader. Flashing in bootloader is only possible if the device is S-OFF.
Click to expand...
Click to collapse
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!
emptyPD said:
Hi guys, so the steps are the next:
1.- Unlock Bootloader Normally with the program.
2.- using this program Flash recovery but get into download mode manually(the program take to bootloader mode)
3.- ROOT.
Correct?
Thanks!
Click to expand...
Click to collapse
2b Make a stock backup
For 3 you need to make sure you install the latest Beta SuperSU, which I don't think is linked in this app.
Related
This tool will allow you remove the Tampered flag from your bootloader. It will also allow you to easily Lock and Unlock your Bootloader directly from recovery.
No root required since it is run in recovery, however you still must be S-OFF.
Before using this tool you need to be sure you are using the latest version of recovery as the M7 U/UL TWRP requires at least version 2.6.3.3 for this package to work. The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE.
The latest M7 U/UL CWM can be downloaded HERE.
***[UPDATE] - It seems that the latest TWRP 2.6.3.3 has been pulled due to some minor issues. If your TWRP version doesn't work please use CWM for now until a updated TWRP release is made.
This will work for Verizon and Sprint as well, however they have different versions of these recoveries, so please make sure you are using the correct recovery for your device.
Saying this again in case you missed it: YOU MUST BE S-OFF!
To use the tool simply copy the zip file to your phone and then boot to your custom recovery and choose install. Then browse to where you copied the file and select it. The aroma installer will begin. Follow the steps outlined in the pictures below and choose the options you want to run.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can just keep this file on your phone and Lock and Unlock at anytime without a PC and without losing data.
***Credits***
S-trace for originally discovering the location of the lock status flag. See this thread.
scotty1223 for his ADB shell commands. Threads HERE and HERE. Scotty was also very helpful to me in understanding some of the default values.
Just to be clear I did not just copy and paste scotty1223's commands into a aroma installer. The echo command can be problematic in aroma, so I developed original code for all four commands. The end result is the same in that the data in the partitions is changed as needed.
***Download***
Guru Bootloader Reset Tool
md5: fdb8264a8f4741bae22939cd7734f7c2
Enjoy!
If this helped you out please consider a small donation or just a thanks would be great.
Demo and Troubleshooting
Demo Video:
***Troubleshooting***
If the installer stays on this screen fore more than a few seconds, then it means you need to delete/format cache. This can be done within both recoveries. You may need to reboot recovery after clearing cache and begin the installer again. This seems to happen more on CWM than TWRP.
If the installer runs but your bootloader doesn't change, it is proably one of these things:
You are not S-Off
You do not have the latest version of recovery (I recommend TWRP)
+ 1
+1
Worked on int. m7 with hboot version 1.55.
Now have removed my tampered flag :victory:
thx
pOpY
Oh yeah..thanks..a handy tool..
Sent from my HTC One using XDA Premium 4 mobile app
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
nkk71 said:
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Click to expand...
Click to collapse
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Evil-Dragon said:
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It will work on any firmware. Hboot is not touched. This only modifies partitions mmcblk0p3 and mmcblk0p7.
crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Noted. Thanks
Sent from my HTC One using Tapatalk
Awesome!
I was looking for this... it worked great! Thanks man!
crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
. Warranty purposes. Or for example in my case if I decided to upgrade my phone with jump, I can make everything look like never even happened. It's quite useful.
Sent from my HTC One using XDA Premium 4 mobile app
nkk71 said:
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Click to expand...
Click to collapse
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
Also sometimes a locked bootloader is needed for promotions like the 25 GB of Google Drive space.
There can be a variety of reasons one might need to toggle it.
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
crushalot said:
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
Click to expand...
Click to collapse
I'm still on CWM 6.....2 (the old one, but with updated ts drivers) gonna test ur tool on friday.
Will let u know.
Btw, thanks for all your guru site, I refer to it a lot; PayPal doesn't work in my country so can't contribute. But thanks !!
Love ur work.
Sent from my HTC One using Tapatalk
joho5 said:
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, my tool doesn't wipe data during a lock or unlock.
It directly modifies the partitions that conatin the bootloader status, without touching /data or /system
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
AndroPlus said:
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8YWJsVGZTc0ZhZUE
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
Click to expand...
Click to collapse
this is only for unlocked bootloader?
x10isrooted said:
this is only for unlocked bootloader?
Click to expand...
Click to collapse
yes.
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
To root, just install SuperSu zip in TWRP (search it)
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
fl3xx said:
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
Click to expand...
Click to collapse
You don't need to backup TA (at least when you are using) since DRM patch solves camera functionality problem.
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
charliebigpot said:
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
Click to expand...
Click to collapse
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
mesajoejoe said:
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
Click to expand...
Click to collapse
Good luck and keep us posted!
charliebigpot said:
Good luck and keep us posted!
Click to expand...
Click to collapse
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mesajoejoe said:
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
Click to expand...
Click to collapse
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
AndroPlus said:
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
Click to expand...
Click to collapse
Here ya go.
mesajoejoe said:
Here ya go.
Click to expand...
Click to collapse
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
AndroPlus said:
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
Click to expand...
Click to collapse
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
mesajoejoe said:
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
Click to expand...
Click to collapse
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
AndroPlus said:
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
Click to expand...
Click to collapse
Let me know if there's anything I can assist with.
mesajoejoe said:
Let me know if there's anything I can assist with.
Click to expand...
Click to collapse
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
AndroPlus said:
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
Click to expand...
Click to collapse
Appears to be working. I have mounting access in TWRP, flashed superuser.zip without issue. Thanks!
Well it was kind of working. On US firmware root was functioning but when switching over to UK it stopped. Since then I have not been able to regain root access on US or UK. After flashing the superuser.zip it just hangs on the Sony logo. I've gone back and forth between US and UK, but no luck. TWRP is having issues unmounting /system... not sure if that gives anyone any insight. I'm probably just going to leave it without root access for now. Appreciate your help!
Does it work on CE version
Hey everyone
Can anyone confirm that it works on CE software Version.
Unlock BL is allowed.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through
You can find the source code for TWRP at https://github.com/omnirom/android_bootable_recovery
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Install as image using Flashify or TWRP
Downloads: TWRP-3.1.1-0_v521-recovery.img
Version Information
Status: Stable
TWRP Version: 3.1.1-0
Kernel: 3.10.84-lineage
Created 2017-05-18
Last Updated 2017-05-19
reserved
Thank you!
Sent from my LG-V521 using XDA-Developers Legacy app
king3opobn said:
Thank you!
Sent from my LG-V521 using XDA-Developers Legacy app
Click to expand...
Click to collapse
TWRP-3.1.1-0 is here --> TWRP-3.1.1-0_v521-recovery.img
For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.
mad212 said:
For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.
Click to expand...
Click to collapse
i downloaded the 3.1.1-0 version and reinstalled but no issue here. did you edit anything or install on the wrong device? mount points are defined in the /etc/recovery.fstab file in recovery. maybe try re-downloading and installing
mad212 said:
For some reason im not able to make a nandroid backup of my stock rooted rom. TWRP is failing to mount data. Am I doing something wrong? I've used TWRP countless times on other devices to backup and have never had a problem.
Click to expand...
Click to collapse
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable
HighRidas said:
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable
Click to expand...
Click to collapse
That did it. Thanks!
Hi.
Using your recovery, I get this:
"b3" devices; this is a "v521". Installer Error (Status 7)
Flashed to an older version of TWRP for the v521 and that worked. Thoughts?
bmac6996 said:
Hi.
Using your recovery, I get this:
"b3" devices; this is a "v521". Installer Error (Status 7)
Flashed to an older version of TWRP for the v521 and that worked. Thoughts?
Click to expand...
Click to collapse
What zip were you trying to flash? im guessing the first half of your error said "this package is meant for b3 devices..." or something along those lines. Im pretty sure the shabbypenguin 3.0.2.0 is b3 based, so it was generic or compatible with v521, v525 etc. . this is v521 only. I assume whatever zip you were trying to install only had the b3 assert. Most have "b3, v521" asserts in the update-script.
That error usually comes up when the recovery checks the assert in the zip you're installing, against the recovery default.prop and the v521 assert wasn't found in the zip package. So it failed because the recovery read the zip as being for another device.
Could also be your bootloader is outdated.
HighRidas said:
What zip were you trying to flash? im guessing the first half of your error said "this package is meant for b3 devices..." or something along those lines. Im pretty sure the shabbypenguin 3.0.2.0 is b3 based, so it was generic or compatible with v521, v525 etc. . this is v521 only. I assume whatever zip you were trying to install only had the b3 assert. Most have "b3, v521" asserts in the update-script.
That error usually comes up when the recovery checks the assert in the zip you're installing, against the recovery default.prop and the v521 assert wasn't found in the zip package. So it failed because the recovery read the zip as being for another device.
Could also be your bootloader is outdated.
Click to expand...
Click to collapse
This started with my LTE is being slow like snail on LineageOS. Baseband wasn't showing up on status (showing unknown) so I was going to try to flash/upgrade the modem to see if that does anything. Would drop into TWRP and flash but would get that error saying this was made for a "B3" not a "V521".
So I decided to go back to stock and flash with this :
https://forum.xda-developers.com/lg-g-pad-83/development/rom-lg-stock-nougat-t3561088
But even that came up with the same errors So I downgrade to shabbypenguin's TWRP and then I was able to flash those packages. Went back to LG STOCK and tried the modem zips but to my original issue, still getting SLOW LTE speeds. Maybe my radios are kaput? APN looks correct comparatively to other US Tmobile APN settings.
You said it could be the bootloader. Wouldn't going back to stock (link above) or even flashing latest LineageOS or RR update it to the latest bootloader?
HighRidas said:
if you just rooted the device you're going to have to wipe data in twrp before it will be mountable
Click to expand...
Click to collapse
I'm in the same boat like the other guy was, every time time I try to wipe data through twrp it fails.. How am I supposed to wipe it?
@HighRidas twrp 3.2 is released, fyi
Does this support encryption if I encrypt with Lineage? I'm hearing some issues with TWRP in general with encrypted Nougat devices.
Has anyone flashed this successfully? I'm having "remote: unknown command" errors.
to prove that I already successfully unlocked the bootloader:
fastboot getvar unlocked
Code:
unlocked: yes
finished. total time: 0.002s
fastboot flash recovery TWRP-3.1.1-0_v521-recovery.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (16170 KB)...
OKAY [ 0.510s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.511s
Any ideas? I'd appreciate any assistance.
mattlach said:
Has anyone flashed this successfully? I'm having "remote: unknown command" errors.
to prove that I already successfully unlocked the bootloader:
fastboot getvar unlocked
Code:
unlocked: yes
finished. total time: 0.002s
fastboot flash recovery TWRP-3.1.1-0_v521-recovery.img
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (16170 KB)...
OKAY [ 0.510s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.511s
Any ideas? I'd appreciate any assistance.
Click to expand...
Click to collapse
Must be done on 20f with dirty cow. https://forum.xda-developers.com/g-pad-x-80/how-to/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
Airtioteclint said:
Must be done on 20f with dirty cow. https://forum.xda-developers.com/g-pad-x-80/how-to/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
Click to expand...
Click to collapse
Ah. Thank you.
Someone really ought to fix the LineageOS guide page for the v521
Now I just have to figure out how to downgrade to 20f without a Windows machine to run LGUP on. I tried in a VM with USB forwarding, but no dice. The USB debugging authorization gets confused when it connects to the host and then the VM...
Encryption does NOT work but I think this is Lineage problem or the device doesn't support it.
When a LineageOS update comes out, and it reboots to recovery, the recovery doesn't install anything. Is this the recovery's fault or LineageOS' fault?
I also have to run this every upgrade (TWRP loop): dd if=/dev/zero of=/dev/block/platform/soc.0/7824900.sdhci/by-name/misc count=1 bs=32
c0080900v said:
I'm in the same boat like the other guy was, every time time I try to wipe data through twrp it fails.. How am I supposed to wipe it?
Click to expand...
Click to collapse
Same here, I go to "Wipe" and swipe and I get various "failed to mount" errors.
cookiemonster79 said:
Same here, I go to "Wipe" and swipe and I get various "failed to mount" errors.
Click to expand...
Click to collapse
You will need to format data on the wipe tab which will remove encryption and delete anything installed but will allow storage to mount.
Sent from my LG-V521 using Tapatalk
Hi guys,
My phone is bricked now and there is no solution yet, I think but it won't hurt me to ask
With the latest news, I could unlock the bootloader of my Verizon pixel 2 successfully (fastboot flashing lock_critical) then I flashed a custom kernel to it. Somehow it won't boot. I stupidly relocked the bootloader while the custom kernel was still on it.
I tried to unlock the bootloader again using the command fastboot flashing lock_critical but it never worked again.
Now my phone is stucked on the bootloader screen, when I select recovery mode, it would take me back to the bootloader screen.
I can't use flash-all because the bootloader is locked. adb sideload won't work for me because I can't get into recovery mode.
Please let me know if you have any suggestion. I really appreciate it.
Otherwise, I will keep it for a while and pray there will be a solution to unlock the bootloader again.
Thanks everyone and happy new year.
what happens when you try the lock_critical again
Lightn1ng said:
what happens when you try the lock_critical again
Click to expand...
Click to collapse
It said failed not allowed
tdiep said:
It said failed not allowed
Click to expand...
Click to collapse
Send a picture of the device in fastboot. Cover the serial number.
Lightn1ng said:
Send a picture of the device in fastboot. Cover the serial number.
Click to expand...
Click to collapse
Here it is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hate to say, but it looks like you're done for. Not under warranty?
Lightn1ng said:
Hate to say, but it looks like you're done for. Not under warranty?
Click to expand...
Click to collapse
I contacted Google asking for a warranty. They asked me to provide the receipt of purchase which I don't have. I bought the phone on Craigslist. So no warranty. Google sucks. Apple never asks for a receipt
tdiep said:
I contacted Google asking for a warranty. They asked me to provide the receipt of purchase which I don't have. I bought the phone on Craigslist. So no warranty. Google sucks. Apple never asks for a receipt
Click to expand...
Click to collapse
Ask the guy who sold you the phone.
@tdiep
Update adb & fastboot.
Lightn1ng said:
@tdiep
Update adb & fastboot.
Click to expand...
Click to collapse
I did but still no luck bro
tdiep said:
I did but still no luck bro
Click to expand...
Click to collapse
Can you fastboot flash the factory images?
Lightn1ng said:
Can you fastboot flash the factory images?
Click to expand...
Click to collapse
Can't do anything but sideload with a locked bootloader. But he can't get to recovery so no sideload for him either.
bobby janow said:
Can't do anything but sideload with a locked bootloader. But he can't get to recovery so no sideload for him either.
Click to expand...
Click to collapse
You might be wrong. People in the Nexus 5X forums seem to say otherwise.
Lightn1ng said:
You might be wrong. People in the Nexus 5X forums seem to say otherwise.
Click to expand...
Click to collapse
@bobby janow is right. I can't fastboot flash with a locked bootloader.
tdiep said:
@bobby janow is right. I can't fastboot flash with a locked bootloader.
Click to expand...
Click to collapse
Not even an official boot.img to the boot partition?
Lightn1ng said:
Not even an official boot.img to the boot partition?
Click to expand...
Click to collapse
C:\Users\lordg\Downloads\platform-tools-latest-windows (3)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (32768 KB)...
OKAY [ 0.085s]
writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.090s
tdiep said:
I contacted Google asking for a warranty. They asked me to provide the receipt of purchase which I don't have. I bought the phone on Craigslist. So no warranty. Google sucks. Apple never asks for a receipt
Click to expand...
Click to collapse
Tell them that it was a gift and ask for warranty again (be polite) !
How come your stock recovery is not working ? You said you flashed kernel only. Not even TWRP .... You need to hold power and then press volume up and immediately release both of them ...
rohanhole said:
Tell them that it was a gift and ask for warranty again (be polite) !
How come your stock recovery is not working ? You said you flashed kernel only. Not even TWRP .... You need to hold power and then press volume up and immediately release both of them ...
Click to expand...
Click to collapse
On the new Pixels, boot and recovery is now combined in one partition.
tdiep said:
Hi guys,
My phone is bricked now and there is no solution yet, I think but it won't hurt me to ask
With the latest news, I could unlock the bootloader of my Verizon pixel 2 successfully (fastboot flashing lock_critical) then I flashed a custom kernel to it. Somehow it won't boot. I stupidly relocked the bootloader while the custom kernel was still on it.
I tried to unlock the bootloader again using the command fastboot flashing lock_critical but it never worked again.
Now my phone is stucked on the bootloader screen, when I select recovery mode, it would take me back to the bootloader screen.
I can't use flash-all because the bootloader is locked. adb sideload won't work for me because I can't get into recovery mode.
Please let me know if you have any suggestion. I really appreciate it.
Otherwise, I will keep it for a while and pray there will be a solution to unlock the bootloader again.
Thanks everyone and happy new year.
Click to expand...
Click to collapse
You said you typed flashing unlock critical. You should not even using that. You should have used flashing unlock. It says on Google page specifically do not use that command unless you have the pixel 2 xl. My guess you did not fully unlock the bootloader. For the pixel 2 XL you have to type into commands flashing unlock critical in flashing unlock for the regular pixel 2 it's only flashing unlock.
Try typing flashing unlock only and see what happens if not you may have bricked your phone
mikeprius said:
You said you typed flashing unlock critical. You should not even using that. You should have used flashing unlock. It says on Google page specifically do not use that command unless you have the pixel 2 xl. My guess you did not fully unlock the bootloader. For the pixel 2 XL you have to type into commands flashing unlock critical in flashing unlock for the regular pixel 2 it's only flashing unlock.
Try typing flashing unlock only and see what happens if not you may have bricked your phone
Click to expand...
Click to collapse
You are correct that Google says specifically not to do that, which is why I did it. Previously on It's Always Sunny, that brought up a menu asking if you want to unlock. It seems OP messed up Kernel somehow.
This is the Xiaomi Mi A2 Lite's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Yay ^_^ Thanks for the efforts Respected devs. Hope it makes life way easier for people here at the community ^_^
unlock bootloader and root still delete all of my files right?
machine1104 said:
unlock bootloader and root still delete all of my files right?
Click to expand...
Click to collapse
Yes
Xiaomi Mi A2 Lite got messed up
Hi there!
I have just received my new Xiaomi Mi A2 Lite phone and wanted to pass all of my data from my old phone to it in a way that it was required to be rooted.
KingRoot didn't work on this new phone, so I unlocked bootloader and tried to install TWRP recovery on my phone.
Installing to the recovery partition did not work. I searched the error it gave me and found a thread saying that flashing it to the boot partition worked for them. So I did. Next thing that happened is that my phone did not boot into the OS (operating system) ever again. It only booted TWRP.
I have since been able to remove TWRP (though I made a back up of it) but the phone still stays on just the loading part before going to the OS.
I have since been able to get back the fastboot and stock recovery, but the phone will not start into the OS anymore.
How can I fix this?
I have been searching for ways to restore my android to the 8.1 Oreo version that it was.
Can I do it with this Tool All In One? Please help! Thank you in advance!! Much appreciated!!
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
chillout23 said:
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
Click to expand...
Click to collapse
If you need to flash twrp and root.no, you will not lose data
Ok. Thank you very much for answer
Then will try
chillout23 said:
Ok. Thank you very much for answer
Then will try
Click to expand...
Click to collapse
I would suggest using the root method mentioned here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Twrp does not have good results for most people.
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
chillout23 said:
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
Click to expand...
Click to collapse
If your bootloader is unlocked, you should not lose any data just installing magisk
Yes...my fault. My BL is unlocked already.
But I posted in that thread...because of some reason does not work. But this is not thread about it
Thanks for help
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
chillout23 said:
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
Click to expand...
Click to collapse
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
uptowner said:
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
Click to expand...
Click to collapse
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
uptowner said:
Because your not supposed to install the twrp image just boot from it
Click to expand...
Click to collapse
Installed TWRP image. I know what is .img
mauronofrio said:
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
Click to expand...
Click to collapse
oops sorry i should check what thread this is before trying to answer a question i blame alcohol .
Thing is there are posts out on the net that advices people with the a2 lite to install the twrp image to their inactive slot and not to just boot it and that's where things seem to start going wrong.
This has absolutely nothing to do with this tool and sorry i just dived in here and confused people.
maybe some kind passing mod will get rid of the post apologies again
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
mesuahas said:
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
Click to expand...
Click to collapse
Read the op follow it exactly how it says if u don't know something research it.i have root with no problems if u do as the op says u shouldn't have no problems
Will this work on pie at all?