Temporary CWM possible? - ZenFone 2 Q&A, Help & Troubleshooting

Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?

This would be the wrong section, but that's alright it'll get moved once a moderator sees it if I'm not mistaken! I don't think that method will work at all tbh.

tasar said:
Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?
Click to expand...
Click to collapse
Thanks for pointing out
It works! Well, at least i can start CWM, but i didn't try functionality yet.
Use this version: http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352
Choose T4 option.
You will get some distorted animated logo at the center for several second, then you will get CWM menu.

Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!

Need CWM version compiled for Zenfone 2.

sorg said:
Need CWM version compiled for Zenfone 2.
Click to expand...
Click to collapse
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.

Reviewers said:
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.
Click to expand...
Click to collapse
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
tasar said:
Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!
Click to expand...
Click to collapse
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.

sorg said:
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.
Click to expand...
Click to collapse
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM

Reviewers said:
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM
Click to expand...
Click to collapse
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).

sorg said:
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).
Click to expand...
Click to collapse
can you share one click batch file with us? if we only could back up the rom it would be awesome..

With this temporary CWM custom recovery, am I able to flash any zips in it? Sorry about the noob question, wanted to use it to flash the disguised version of Cerberus.

Related

[RECOVERY] [OFFICIAL] TWRP 2.2.2.1 for Acer Iconia Tab A100

Teamwin Recovery Project for A100 version 2.2.2.1​ -godmachine81 release-​
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
​
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha
Broken links, so you can correct it.
Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.
Installed and working perfectly!
Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?

[Q] [HELP] Trying to flash TWRP on V50020b

Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Thank You.
You can use dd to write the aboot.img of 4.2.2 back. This will allow the old Loki flash method.
Sent from my LG-V500 using Tapatalk
---------- Post added at 01:25 AM ---------- Previous post was at 01:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2698267 Step 3
Sent from my LG-V500 using Tapatalk
bloommax said:
You can use dd to write the aboot.img of 4.2.2 back. This will allow the old Loki flash method.
Sent from my LG-V500 using Tapatalk
---------- Post added at 01:25 AM ---------- Previous post was at 01:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2698267 Step 3
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
i tried doing this couldn't get it to work.. i have of done it wrong?
could you post the steps in noob style?
or does anyone know of a guide on how to install a custom recovery on a V50020b running stock 4.4.2 (i managed to root just need recovery)
gklute said:
i tried doing this couldn't get it to work.. i have of done it wrong?
could you post the steps in noob style?
or does anyone know of a guide on how to install a custom recovery on a V50020b running stock 4.4.2 (i managed to root just need recovery)
Click to expand...
Click to collapse
I had the same problem until I ran across this post: http://forum.xda-developers.com/showthread.php?t=2698267 {Acually the same you quoted}
If you'll go down to the download Step #3 and copy that zip file to your computer and unzip it and run the bat file it will install TWRP v2.7. Of course you'll have to install the LG USB drivers and install from your computer. (Won't work otherwise) Also be sure and use the second down connection for USB on your tablet - M-something, but not the charging one.
Also - get a good reboot app so you won't have to hold the buttons.
ruhelking1 said:
Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Click to expand...
Click to collapse
You're being vague! Which TWRP?
Cal said:
I had the same problem until I ran across this post: http://forum.xda-developers.com/showthread.php?t=2698267 {Acually the same you quoted}
If you'll go down to the download Step #3 and copy that zip file to your computer and unzip it and run the bat file it will install TWRP v2.7. Of course you'll have to install the LG USB drivers and install from your computer. (Won't work otherwise) Also be sure and use the second down connection for USB on your tablet - M-something, but not the charging one.
Also - get a good reboot app so you won't have to hold the buttons.
Click to expand...
Click to collapse
I also have this version V50020b and this method didn't work.
When boot to recovery there's still the android recovery!!
What am I doing wrong?
Thanks in advance.
luisbraz said:
I also have this version V50020b and this method didn't work.
When boot to recovery there's still the android recovery!!
What am I doing wrong?
Thanks in advance.
Click to expand...
Click to collapse
You're quoting an old post (way back in April 2014).
1st - Do you have a recovery installed?
2nd - If so, you should update to at least TWRP 2.800
I may be confused about exactly what you are doing...now if you're only booting with the buttons (power-sound down, sound up) that is the message you get and you have to push 'power' 2 times to enter recovery. Are you doing that when you see the display of android recovery after using the cold boot, then the volume and power buttons?? And you are expecting to see TWRP opening, but instead of going straight to TWRP recovery - you're getting what you say 'Android Recovery', or Factory Reset?
Post back so we will understand please. Hope I'm not being confusing in my answers...
Cal said:
You're quoting an old post (way back in April 2014).
1st - Do you have a recovery installed?
2nd - If so, you should update to at least TWRP 2.800
I may be confused about exactly what you are doing...now if you're only booting with the buttons (power-sound down, sound up) that is the message you get and you have to push 'power' 2 times to enter recovery. Are you doing that when you see the display of android recovery after using the cold boot, then the volume and power buttons?? And you are expecting to see TWRP opening, but instead of going straight to TWRP recovery - you're getting what you say 'Android Recovery', or Factory Reset?
Post back so we will understand please. Hope I'm not being confusing in my answers...
Click to expand...
Click to collapse
I know that is an old post. I was trying to flash the TWRP recovery without any downgrade of the software, since this method was suposed to work with the software version V50020b.
I simply want to flash TWRP recovery, the tablet is all stock with root (TowelRoot), but I just realised that I have to downgrade the software (http://forum.xda-developers.com/showpost.php?p=58198471&postcount=44), and wanted to avoid this! I already softbricked the tablet with only 3h of usage, and now I'm a little afraid! lol
Do you now any method that works without the downgrade trick?
Thanks.
Flash TWRP with flashify (root) - (from Play Store).
This *should* work & if not I think no harm will come ... Flashify.app just won't 'work' if things are not correct.
Good luck!
Cal said:
Flash TWRP with flashify (root) - (from Play Store).
This *should* work & if not I think no harm will come ... Flashify.app just won't 'work' if things are not correct.
Good luck!
Click to expand...
Click to collapse
I did that. That's what softbricked the tablet!
luisbraz said:
I did that. That's what softbricked the tablet!
Click to expand...
Click to collapse
I would shut the tablet completely down.
You should be able to use the 'buttons' to get to 'Factory Reset'. Do what you know: Power/+down then all 3. If you can't get to TWRP, it must not be installed.
Check with a command window. Be sure & use 'su'. Ask a guru 'how'...I may not be 'expert' enough!
ruhelking1 said:
Im trying to flash TWRP on my v50020b but cannot seem to do it. Its currently on the stock 4.4.2 GB rom. Please can someone advise me how to do this.
Thank You.
Click to expand...
Click to collapse
Hi, i had the same problem as yours with v50020d 4.4.2
first i rooted with ioroot http://forum.xda-developers.com/showthread.php?t=2776198
second install step 3 http://forum.xda-developers.com/show....php?t=2698267
you have to run "runme.bat" from the zip. If did not install here is a post that helped me http://forum.xda-developers.com/showpost.php?p=54027265&postcount=9
then flash witch recovery you want with flashify or twrp app
if you have any questions message me.
good luck

(OTA) T-Mobile Lollipop 4.20.531.4 Sense 6.0 Zip

This is the official 5.0.1 Lollipop (4.20.531.4) Sense 6.0 OTA for T-Mobile HTC One M8. (4.20.531.4)
Nothing modified. Just a straight copy. Enjoy!
If you just need the firmware or rom you can download the zip and extract what you need from it. It's pretty simple.
I'll try to get around to extracting everything and posting links for the individual firmware as well. Don't get mad if I don't get around to it though.
Don't do anything with this unless you know what you're doing.
Download Link: https://docs.google.com/uc?export=download&confirm=mOs6&id=0B83tee7zNQDVTTRsTjJ1dzhHeUU
Would it be possible to upgrade to this without having to flash back to stock first?
How to go back to stock and apply OTA.
douglasf01 said:
Would it be possible to upgrade to this without having to flash back to stock first?
Click to expand...
Click to collapse
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
bradley_e_smith said:
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
Click to expand...
Click to collapse
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
douglasf01 said:
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
Click to expand...
Click to collapse
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
bradley_e_smith said:
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
Click to expand...
Click to collapse
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
bradley_e_smith said:
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
Click to expand...
Click to collapse
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
This is the issue I am presented with trying the CMD with fastboot
douglasf01 said:
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
Click to expand...
Click to collapse
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
bradley_e_smith said:
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
Click to expand...
Click to collapse
I went into the supersu application and there was an unroot option that clears the cache, system, and modifies something. I also flashed the stock recovery back after your last comment, I have never owned an HTC Android device and wasnt aware that was a default. I am going to try the OTA and see if this works out. I will let you know.
I have always just reflashed stock recovery.... Made sure I enabled all of the apps I disabled (like bloatware or whatnot), and then was always able to update. I actually can't recall if unrooting was required.
But I do know that locking the boatloader is not necessary.
---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------
I am just sad to say goodbye to Xposed....
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
When you get the red triangle, hold volume down for a few seconds...you should get a log screen (although it may be volume up, I can't remember, try both)...it will tell you what is wrong.
Also, from my past experiences, if I didn't flash a new stock Rom (but just tried to "clean up" my existing stock Rom), I would run into problems because I had some app on the phone that even if I had deleted it, had originally modified build.prop... And that is one key thing the update checks before proceeding with install. So you have to make sure you have a stock build.prop file.
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
You need to rename the recovery file.
Avoid using '+' in files names.
If you have spaces in a file name, ALWAYS put a "quotation mark" around the file name.
DROITURK182 said:
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
Click to expand...
Click to collapse
The link doesn't seem to work.
epsix said:
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
Click to expand...
Click to collapse
This is something that always happens with HTC devices. I don't know why.
OfficialLocdoGg said:
This is something that always happens with HTC devices. I don't know why.
Click to expand...
Click to collapse
Yeah, I try changing the sku id in ACC/default.xml to metro pcs, and other carriers it works but not good signal.
Okay, I have got APNs unlocked, root, restriction-free tethering working over IPv6, busybox installed, and a kernel with modified initramfs. Anyone interested in a nice simple debloated stock ROM?

TWRP and Encryption password for data.

Hello there! thanks for your time.
I swear that I tried everything.
I received my HTC 10 like 1 almost 2 weeks ago.
I unlocked the bootloader, flashed the recovery, supersu, everything just fine. Everything works. Except that when I boot into the recovery TWRP ask for the password to decrypt /data. I put my pin = password failed. I tried to resetting the pin, tried putting a password, leaving it blank (tested default_password too) but I cant make TWRP work mounting /data. It always says that password is incorrect.
I even tried factory reset 2 times.
the version is: 3.0.2-2
Any ideas?
Thanks again guys! have a great day!
Anytime its asked me for a password I just press cancel.
My understanding is that the HTC 10 in encrypted by a proprietary HTC code.
Yep - just hit Cancel on that screen.
See the TWRP thread here - http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
"NOTE: TWRP CANNOT decrypt HTC Sense ROMs!!"
And this in the second post
"5. My storage is encrypted, and TWRP can't decrypt it. How am I supposed to flash anything?
First, hit the "Cancel" button at the decryption prompt to continue to the TWRP Main Menu. Storage doesn't need to be decrypted to root the device or flash custom ROMs. If storage is decrypted on this device, mobile network will stop working.
6. Is it possible to retain encryption AND make a data partition backup in TWRP?
No. TWRP cannot currently decrypt /data on this device. That is due to HTC's use of proprietary encryption. Until someone figures out a way around that, the only way to access /data in TWRP is to unencrypt using the "Format Data" option in TWRP and disabling the forceencrypt flag in the ramdisk (which will break mobile network in Android)."
Hey! thanks!
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
well thanks again guys!!
deftoner said:
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
Click to expand...
Click to collapse
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
deftoner said:
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
Click to expand...
Click to collapse
If you're US unlocked variant, you can follow my guide, here:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you're another variant, reply in the above thread and I can help you find the versions of the files you need to flash.
deftoner said:
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
Click to expand...
Click to collapse
Reboot download
Make sure your mid matches the US one (I had super cid for mine but apparently if the mid doesn't match it will give error as well)
fastboot getvar all
will tell you
then once it was all set
fastboot flash zip nameof_file.zip
DO IT TWICE!
Then reboot your download to see if the changes took place
You then have to reflash your TWRP recovery because the zip will flash stock recovery
if you are still getting the password box, click cancel for TWRP, wipe > advance and wipe data
good luck
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
Are you asking for help?
jollywhitefoot said:
Are you asking for help?
Click to expand...
Click to collapse
No... I'm just complaining.
Orch4rd said:
No... I'm just complaining.
Click to expand...
Click to collapse
OK cool. Carry on then.
Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
you could...i do it often before flashing new build....
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
CryptoJones said:
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
Click to expand...
Click to collapse
hay I really need help as in phones setting in security tap is says "encrypt phone - phone is encrypted".
is that a good thing? I want my phone to be "data" unlocked if u know what I mean? help
also I got my phone about 3 weeks and unlocked the bootloader but S-on and I live in Europe.
I try the rom with f2fs support and always when I try to boot the rom with "data" and "cache" formatted as f2fs it doesen´t boot and I try to boot the compatible rom and kernel with ext4 first and when I got a full boot I go to recovery to format cache and data as f2fs but this time when it boots "data" reverts back to ext4 and cache stays as f2fs?
any idea!
I use disk info app and is it because my phone is encrypted data never stays as f2fs or something else as I don´t know much about "decrypt or uncrypt" and the other...
thnx!
TWRP not PIN Pattern
Moved this post to main TWRP

[Metro][Stock] SOFIAP-T QPRS30.80.64.6.2

100% Stock ROM for the Metro by T-Mobile Moto G Stylus
Requirements:
ADB & Fastboot from here:
https://developer.android.com/studio/releases/platform-tools
ADB & Fastboot set into your OS environment
(This allows adb to be used in any folder)
Instructions here:
https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
7-Zip to extract the .7z file:
https://www.7-zip.org/
Download:
QPRS30.80.64.6.2
Older Downloads:
QPRS30.80.64.6
QPRS30.80.64.3
Flashing Instructions:
1. Extract the zip using 7-Zip
2. Boot into Fastboot
3. Run the flash-all.bat this should automatically start flashing all the partitions
This will wipe everything. If you want to keep your data, before running open the .bat file with a text editor and remove -w from
Code:
fastboot -w reboot
​
(If on another platform than Windows you'll need to change the .bat file to your OS)
Looking for the Retail variant Stock ROM?
See Here:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
cbc0201 said:
QPRS30.80.64.6
https://mega.nz/file/nQkRHByR#md9YeMeAS4Vp6_lhL3pm9Bbqx1JrCeMHW8Lbkzr1RQo
Click to expand...
Click to collapse
Thanks for the download. I added to the OP with the flash-all.bat
DMedina559 said:
Thanks for the download. I added to the OP with the flash-all.bat
Click to expand...
Click to collapse
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
Click to expand...
Click to collapse
I have QPR30.80.64.6 model XT2043-4
LinuxAndroidAlwys said:
Okay so I have a question based on my observation maybe stupid may not be I don't care
Q: how do I identify if my phone is the RETUS or the SOFIAP-T?
Q: Sorry this is the observational question,the build number nomenclature in my phone does not have an s at the end of the QPR but in this forum it does but when you download the file it does not. Or does that not matter?
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
I have QPR30.80.64.6 model XT2043-4
Click to expand...
Click to collapse
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
DMedina559 said:
You should be able to tell in the about phone menu in the settings. And the S might be a typo I'm not sure I'll have to check
Click to expand...
Click to collapse
I figured it out but I'm still confused about the s
LinuxAndroidAlwys said:
I figured it out but I'm still confused about the s
Click to expand...
Click to collapse
The s is just a typo on my end. I'll fix asap
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
worked great
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
LinuxAndroid4evr said:
Not sure If I'm in the rightr thread or not but need serious help !!! I had twrp on my phone was trying to reboot system and hit a slot phone went black and will not boot into fastboot turn on, nothing! It is as dead as a dorrnail ie hard bricked . I have loaded all the drivers for phone and qualcomm. Computer only recognizes phone as Qualcomm 9008 mode not bulk mode. Anyone know how to restore phone at least to be able to get into fadtboot? Anyone help would be very much appreciated this is my daily driver and I am screwed without it.
Click to expand...
Click to collapse
i did the same thing, booting into slot b got me into the device normally
cbc0201 said:
QPR30.80_64_6_2
https://mega.nz/file/2UMGDb7B#4OZmO_DMUXiJnSkuyf4Y1w3LHVxoXM-P7umpRUWqaAQ
Click to expand...
Click to collapse
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Updated OP with build QPRS30.80.64.6.2
CorporalCactus said:
Hey man this is my current version as well, but it doesnt have the flashall bat file, do you know if i could just use one from the links in the OP? i am new to flashing roms in this manner and i dont really know how it works
Click to expand...
Click to collapse
Yeah using the old flash-all.bat file works with newer builds, just put all the flahsing files in /Recovery-Files/ with the flash-all.bat outisde that folder
Is any way to completely delete Metro PCS bloatware? I have rooted phone. No success to delete bloatware. Can I replace Metro PCS ROM with retail ROM? Is that possible? Any ideas? Thank you
Hello please I used the Moto g stylus as well, using MetroPCS with QPRS30.80-64-6-2, I want to know if this rom is unlocked , will it remove the sim lock on my device as the remote unlock fails. Thanks
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Where is the flash-all.bat ?
MotoLindvall said:
Hi new guy here. Got couple moto g stylus (2020 pro). Mine Ive tried out arrow, havoc cr stag, bliss and resurrection. My wife's exact same phone she decided to have me install resurrection remix and magisk root it. ADB installed until last step which was fastboot -w. Had error about not auto formatting RAW format. I managed to fix that but still boot looped or twrp 35. Sofia will load but can't install any rom from zip. Stag logo bootlooeded.. hard to even explain.. damn. Anyway
Any suggestions?
Click to expand...
Click to collapse
If you still need to figure out the crazy flashing procedure for our device...best answer is make sure you are on STOCK Android 10...if you have updated to Android 11 you will not be able to flash custom ROMs or have a fully functional TWRP recovery...and Magisk root is not good with A11..You can flash GSI on Android 11 Stock firmware or use the DSU loader to install the Beta of Android 12...and the GSI situation is 50/50 if it will boot or not....what I do is flash the A10 stock final upload from the lionnet archive using the ever so awesome Moto flash tool...the tool does everything...and fixed your Beta partition so you can flash custom ROMs...once you finish with the tool reboot into STOCK recovery and format data..reboot to Stock Android 10 once you get to the Android setup welcome screen reboot to boot loader and flash TWRP recovery to both recovery slots...reboot to recovery...and format data...then reboot to fastbootd...your first custom install is recommended to be flashed from fastbootd on both slots...now when you finish reboot to Stock 10 recovery and format data...boot the rom first before and mods installed...then once you boot the rom you can flash mods with TWRP..get in a habit of after new system install format data in stock 10 recovery...now any custom ROM flash at this point forward do from TWRP and before flashing format data in TWRP after format again in stock 10 recovery...gapps install after first boot...Magisk install only after you fully go through the flashing procedure and setup the Rom make sure to enable dev options or it won't boot..and again flash Magisk after full setup and reboot..this procedure works...I keep a copy of stock recovery and TWRP recovery on my sdcard and platform tools on pc...you can flash stock 10 and TWRP in mobile if your rooted with any root kernel mgr so that way you don't have to use pc...the moto flash tool is the best way to setup the phone for custom ROMs.....

Categories

Resources