Related
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX
iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk
Ota KitKat update?
What phone do you have?
I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Bricked is right !
quyvinh said:
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
My recovery is still untouched, so does bootloader. That is why I said mine os softbrick. It means if I have the stock ROM, then I am ready to go back alive again. I cannot imagine how could you erase the stock recovery? Unless you failed the custom recovery, then it probadly hard bricked. If I can find how to fix it then I will post here. I am currently working around with MTK Droid tool and SP Flash tool, but they are working partially only. Cannot write out the scatter file. Man, this phone is tough.
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
min1968 said:
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
Click to expand...
Click to collapse
Did you do this?
emowing said:
13. select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
Click to expand...
Click to collapse
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
This is because first these phones are MTK67xx phone, and 2nd they are running on new android 5.1. So the way they are rooted different with the old ways.
grampyog said:
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
Click to expand...
Click to collapse
eksasol said:
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
Click to expand...
Click to collapse
Here you go. this is a twrp backup.
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
how do i restore the rom im kinda a newb i rooted my phone than restored and now im stuck a startup and it wont go it. just gets stuck on "checking connection" i have the vivo XL and i am in need of help so how do i get this rom back to original because i dont know what to do:fingers-crossed:
Bam-Great
Followed all of the instructions and many tries later I have a phone that boots and works just fine. What I'm not finding is an image of the original rom anywhere. Pretty sure I've looked closely but if anyone has a link take me to your leader. My thanks to the awesome person that put this tutorial together. If anyone has bricked their phone trying to root follow these instructions.
Note: The stock MS drivers did not work make sure to load the VCOM drivers.
Many thanks again,
Ken
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
Any ideas if this restore method with Bypass the Factory reset protection?
Just as a quick update. Simply formatting with the flash tool. And installing the gionee firmware was enough to bypass the Google factory reset prevention. Hope this helps anyone else that forget there Gmail address they used.
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
cas8180 said:
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
Click to expand...
Click to collapse
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
xdadev_user11 said:
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
Click to expand...
Click to collapse
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
cas8180 said:
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
Click to expand...
Click to collapse
That's strange. grampyog had the same problem. But the backup rom worked for me and eksasol. Very strange.
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
xdadev_user11 said:
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
Click to expand...
Click to collapse
That did it my good man! I have a complete bundle now with boot logo and the nvram secro files you included I feel compelled to mirror so let me work on that. Thanks a bunch thanks to you I am back in business!
Here is the link for the complete TWRP backup that should be able to restore any device back to stock. https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.
Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.
Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
I have the G4 LGUS991 gotta can I tell if it's h811?
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?
mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.
So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4
This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app
NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs
I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.
How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!
So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation
MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp