Related
Im on Z008 2.19.40.12_20150612 I cant seem to flash twrp no matter how hard I try. Im rooted and unlocked BL. Is fastboot easiest way or sideload or from twrp manager? Does someone have the download link of which IMG I would need?
Check the General resources thread, you might have to upgrade your stock firmware version.
Download twrp manager from app store. Use that.
Sent from my ASUS_Z00AD using Tapatalk
I've tried that but what img file do I need for my firmware?
I see the new one is 2.20.40.63 what would be the right twrp img file to flash?
cell2011 said:
I see the new one is 2.20.40.63 what would be the right twrp img file to flash?
Click to expand...
Click to collapse
You must be on 2.19.40.18 - 2.19.40.22 to unlock your bootloader. Only after unlocking your bootloader can you flash TWRP onto your phone permanently...
Go to general section and check out the 1st stickied post, it will give you the info you need to do this...
I'm already unlocked and rooted. What img twrp should I flash based on my firmware?
cell2011 said:
I'm already unlocked and rooted. What img twrp should I flash based on my firmware?
Click to expand...
Click to collapse
TWRP officially support Zenfone 2 (551ML) so get from there....
I'm 550 ml now what? Can anyone just send me a link to the right img?
What are the steps to flash this TWRP recovery 2.8.7.0 OTG-USB NTFS.zip. This is for 550 ml
I'd use untethered Twrp then flash, but that's me.
Twrp manager automatically picks the right recovery.
Sent from my ASUS_Z00AD using Tapatalk
I should be able to flash a rom through CWM that way right? I'm already unlocked bootloader and rooted and su is on my sd card. Can I flash a rom gaps and su again through CWM and I'm good? But I'll be stuck with that rom till I do perm recovery right? CM 12 not for 550 yet?
ultramag69 said:
I'd use untethered Twrp then flash, but that's me.
Click to expand...
Click to collapse
I should be able to flash CWM rom gapps su that way right? But then I'd be stuck with that rom till I'm perm recovery?
cell2011 said:
I should be able to flash CWM rom gapps su that way right? But then I'd be stuck with that rom till I'm perm recovery?
Click to expand...
Click to collapse
Yes...
From what I've read it seems that you have to unlock bootloader to do this. Which is something I am finding hard to digest.
Do I really need to unlock bootloader to flash official build? Or is there some official way which I can't seem to find?
Piyush Rawal said:
From what I've read it seems that you have to unlock bootloader to do this. Which is something I am finding hard to digest.
Do I really need to unlock bootloader to flash official build? Or is there some official way which I can't seem to find?
Click to expand...
Click to collapse
Didn't find a way without data wipe.. but my bootloader is locked and never rooted on this OP3, as long as your OP3 is encrypted I don't think there is a way without loosing data.
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Piyush Rawal said:
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Click to expand...
Click to collapse
Seems like adb drivers issue (on Windows?) many are facing. What worked for me is to cut/paste zip to desktop and then immediately cut/paste back to adb folder (without closing command prompt) and typing adb sideload zip again..
See if it helps..
Piyush Rawal said:
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Click to expand...
Click to collapse
Had that issue recently. Just rebooted my PC, and that fixed it.
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
vibraniumdroid said:
I flashed the wrong bootloader so fastboot does not work. I still have TWRP Working but anything I flash does not boot. I am looking for a full factory OTA that I can flash via TWRP so it will re-flash the proper bootloader and all the other factory images so I can un-brick it through fastboot. I have tried to flash many different update files but it gives an error 7 and says to be on 6.0.1 or 7.0 before installing it. Can someone please help me un-brick this or link a full OTA that I can flash via TWRP. I attached the bootloader.img so if anyone could make a flashable zip to flash the stock bootloader that would probably work.
Click to expand...
Click to collapse
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
ROM_HUNTER said:
Follow this discussion.
"https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492"
Click to expand...
Click to collapse
does not work
vibraniumdroid said:
does not work
Click to expand...
Click to collapse
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
flashallthetime said:
If fastboot works then you're not hard bricked, most likes soft brick. I would suggest flashing magisks 14 after you flash the rom as dm-verity will check if your system is modified , dm-verity needs to be disabled
Click to expand...
Click to collapse
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
vibraniumdroid said:
I already tried flashing magisk. Also I can boot into the bootloader but the computer does not see it in fastboot anymore (probably because I flashed the bootloader.img for the moto z play droid accidentally)
Click to expand...
Click to collapse
Hard bricked for sure
flashallthetime said:
Hard bricked for sure
Click to expand...
Click to collapse
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
vibraniumdroid said:
not exactly because twrp works. If I could flash fastboot images through TWRP I could un-brick it. If somebody could modify the stock rom's updater-script and remove the requirement to be running a stock rom then I could flash that and I would probably be unbricked.
Click to expand...
Click to collapse
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
so you are sure that it is impossible to make a flashable zip of bootloader. Maybe it is just my computer I'll try booting of linux on usb and then see if fastboot can see it.
flashallthetime said:
Bootloader can not be flashed through twrp so you'll need to flash the bootloader through fastboot. If your device is not recognized when you plug it in your computer then you're hard bricked, if fastboot is not accessable then you're hard bricked
Click to expand...
Click to collapse
how do you fix a hardbrick?
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
flashallthetime said:
Here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Click to expand...
Click to collapse
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
vibraniumdroid said:
I tried that does not work:crying: also I got windows to see the phone as addison fastboot s but when i do fastboot devices it does not show up
Click to expand...
Click to collapse
Have you tried using these albus (Z2 Play) blank flashes as mentioned here to repair your bootloader? https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181
https://forum.xda-developers.com/showpost.php?p=73411048&postcount=206
These may hopefully get your device to the point where it's recognised in fastboot and you can then flash the stock ROM via fastboot.
vibraniumdroid said:
how do you fix a hardbrick?
Click to expand...
Click to collapse
You don't. That's why it's called a hard brick.
flashallthetime said:
Do you have the correct driver,, if you use Linux there is no need for the driver just install minimal ADB and fastboot
Click to expand...
Click to collapse
booted of linux from a usb and that worked thanks
hi guys
i try to install a new update (7.0 20a) and after the reboot the twrp disappeared. I try to reinstall it but i believe write on bootloader and not on recovery.
Now the phone is bloked in download mode (dm), if i reboot open only dm. I do not enter in system, adb / fastboot dosn't work the, the key combination work for dm, imei code and reset (return in dm).
I try with .kdz and nothing. The .tot file for my H825 EU and dll i can not find.
I try this sw: LGUP , Flash_Tool, B2CApp
i've been looking in the xda and internet for find a solution.
ideas for help me?
ps: sorry for english:crying:
mrcry said:
hi guys
i try to install a new update (7.0 20a) and after the reboot the twrp disappeared. I try to reinstall it but i believe write on bootloader and not on recovery.
Now the phone is bloked in download mode (dm), if i reboot open only dm. I do not enter in system, adb / fastboot dosn't work the, the key combination work for dm, imei code and reset (return in dm).
I try with .kdz and nothing. The .tot file for my H825 EU and dll i can not find.
I try this sw: LGUP , Flash_Tool, B2CApp
i've been looking in the xda and internet for find a solution.
ideas for help me?
ps: sorry for english:crying:
Click to expand...
Click to collapse
its normal no twrp cause you flash stock rom. stock dont have twrp but LG recovery.
there is a way to install twrp. i use h811 so i dont know. but i heard after 7.0 command dont work.
raptorddd said:
its normal no twrp cause you flash stock rom. stock dont have twrp but LG recovery.
there is a way to install twrp. i use h811 so i dont know. but i heard after 7.0 command dont work.
Click to expand...
Click to collapse
if I try to send commands with adb or fastboot the phone answers I do not know or impossible to flash this partition then is impossible install the twrp
thanks anyway
mrcry said:
if I try to send commands with adb or fastboot the phone answers I do not know or impossible to flash this partition then is impossible install the twrp
thanks anyway
Click to expand...
Click to collapse
it is possible.
@steadfasterX
install twrp with N bootloader >?
how?? i remeber reading please answer so next time i can give better help.
raptorddd said:
it is possible.
@steadfasterX
install twrp with N bootloader >?
how?? i remeber reading please answer so next time i can give better help.
Click to expand...
Click to collapse
This is covered in the official TWRP thread find the topic installation
Sent from my LG-H815 using XDA Labs
raptorddd said:
it is possible.
@steadfasterX
install twrp with N bootloader >?
how?? i remeber reading please answer so next time i can give better help.
Click to expand...
Click to collapse
N bootloader? Nougat
I install the 3.2 TWRP, later install 29a beta official by LG.
Now the phone is blocked in download mode. I don't send comand with adb for start recovery.
mrcry said:
N bootloader? Nougat
I install the 3.2 TWRP, later install 29a beta official by LG.
Now the phone is blocked in download mode. I don't send comand with adb for start recovery.
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
raptorddd said:
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Click to expand...
Click to collapse
thanks but the problem not is twrp.
I follow this guide once again https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
with the usal fail at 24 % woth error 0x2000 invailed command response
i try to change LGUP_8994.dll with a new version extract by .kdz i wanted install (Italy 20g 0720) but nothing
screenshot : https://www.dropbox.com/s/tt1kaay41ymad3s/Screenshot (6).png?dl=0