Related
i dont have twrp and cant go into download mode,only fastboot. need to send my phone back to t mobile. is there a way to root or install twrp with the problems i have?
Still_living714 said:
i dont have twrp and cant go into download mode,only fastboot. need to send my phone back to t mobile. is there a way to root or install twrp with the problems i have?
Click to expand...
Click to collapse
Does you phone boot into your OS? If not since downloadmode doesn't work you need to push these files via fastboot.
vel0city said:
Does you phone boot into your OS? If not since downloadmode doesn't work you need to push these files via fastboot.
Click to expand...
Click to collapse
when typing adb devices my phone shows up. when i type fastboot devices nothing shows up. i installed the drivers but i still cant get it to work?!
Still_living714 said:
when typing adb devices my phone shows up. when i type fastboot devices nothing shows up. i installed the drivers but i still cant get it to work?!
Click to expand...
Click to collapse
Do you have the fastboot installed or present on your computer?
vel0city said:
Do you have the fastboot installed or present on your computer?
Click to expand...
Click to collapse
yes i do but when typing command fastboot devices it doesn't show up
vel0city said:
Do you have the fastboot installed or present on your computer?
Click to expand...
Click to collapse
when i give commands on adb like reboot it works but not fastboot devices..am i missing something?
Still_living714 said:
when i give commands on adb like reboot it works but not fastboot devices..am i missing something?
Click to expand...
Click to collapse
It should work if you have the fastboot.exe file. Your folder should look like this image with the fastboot.exe and the files you want it to push:
https://hostr.co/file/LjdhzxB/Android folder.JPG
vel0city said:
It should work if you have the fastboot.exe file. Your folder should look like this image with the fastboot.exe and the files you want it to push:
https://hostr.co/file/LjdhzxB/Android folder.JPG
Click to expand...
Click to collapse
thanks brother, got everything sorted out.
Trying to flash twrp in fastboot mode, but not having much success. Adb devices doesn't list my device and when i try fastboot flash recovery it says that it's written something but when i try to go to recovery mode after reboot it just takes me to the stock recovery which resets the phone.
Have latest lg drivers along with 15 second adb installer installed. Running win 10 x64.
Any idea how i can successfully install twrp?
Thanks
Spaceboy60 said:
Trying to flash twrp in fastboot mode, but not having much success. Adb devices doesn't list my device and when i try fastboot flash recovery it says that it's written something but when i try to go to recovery mode after reboot it just takes me to the stock recovery which resets the phone.
Have latest lg drivers along with 15 second adb installer installed. Running win 10 x64.
Any idea how i can successfully install twrp?
Thanks
Click to expand...
Click to collapse
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok read through it, inc a couple of guides mentioned in that thread. Rebooted to bootloader no problem
However when i type fastboot boot twrp.img i get the error:
FAILED (remote dtb not found)
typing fastboot flash twrp.img is down as successful but when i try to boot recovery it just takes me to the stock recovery reset.
All fastboot and lg drivers installed.
Spaceboy60 said:
Ok read through it, inc a couple of guides mentioned in that thread. Rebooted to bootloader no problem
However when i type fastboot boot twrp.img i get the error:
FAILED (remote dtb not found)
typing fastboot flash twrp.img is down as successful but when i try to boot recovery it just takes me to the stock recovery reset.
All fastboot and lg drivers installed.
Click to expand...
Click to collapse
No there is only one official twrp thread (see my signature) and there is only one guide to flash.
Try fastboot boot but with version 3.0.2.0 instead
#
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Yea just read the main XDA twrp thread carefully! You did it wrong and its all there.
And fastboot is not adb! In fastboot mode you can't use adb
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
steadfasterX said:
No there is only one official twrp thread (see my signature) and there is only one guide to flash.
Try fastboot boot but with version 3.0.2.0 instead
#
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Same error:
FAILED (remote dtb not found)
Spaceboy60 said:
Same error:
FAILED (remote dtb not found)
Click to expand...
Click to collapse
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
gentr said:
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
Click to expand...
Click to collapse
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.
Spaceboy60 said:
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.
Click to expand...
Click to collapse
maybe problem is not on the driver but haw to write comand, use this ( flash recovery twrp-2.8.x.x-xxx.img ) or ( fastboot flash recovery twrp-2.8.x.x-xxx.img ). use and this twrp 2.8.... if the problem is on the driver's use this link http://www.guideitech.com/mobile/android/risolvere-errore-waiting-for-device-android-adb-fastboot/ this section adb kill-server adb start-server
Sent from my LG-H815 using Tapatalk
Spaceboy60 said:
That's the guide i was following. Still get same error when issuing command. Think it's to do with the drivers in win 10 under fastboot mode.
Had an explanation mark against android. I selected update driver and then adb bootloader interface from the list.
Click to expand...
Click to collapse
if you wanna be sure that this is not a driver issue just try FWUL
but back to your problem. This error can happen when u have a older/newer bootloader flashed which works in another way as it should.
What is your current ROM version?
gentr said:
http://www.androidrootguide.com/2015/06/how-to-install-twrp-recovery-and-root-lg-g4-h815.html
Click to expand...
Click to collapse
gentr said:
maybe problem is not on the driver but haw to write comand, use this ( flash recovery twrp-2.8.x.x-xxx.img ) or ( fastboot flash recovery twrp-2.8.x.x-xxx.img ). use and this twrp 2.8.... if the problem is on the driver's use this link http://www.guideitech.com/mobile/android/risolvere-errore-waiting-for-device-android-adb-fastboot/ this section adb kill-server adb start-server
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
steadfasterX said:
if you wanna be sure that this is not a driver issue just try FWUL
but back to your problem. This error can happen when u have a older/newer bootloader flashed which works in another way as it should.
What is your current ROM version?
Click to expand...
Click to collapse
Stock ROM. Was running MM at one point but downgraded to lollipop with lgup as i was having issues. Software info screenshot:
Spaceboy60 said:
Stock ROM. Software info screenshot:
Click to expand...
Click to collapse
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.
steadfasterX said:
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.
Click to expand...
Click to collapse
Ok tried FWUL. although my phone shows up on the desktop adb and fastboot don't see it.
steadfasterX said:
most ppl are on MM or N these days which has a newer bootloader.
This should solve your problem.
otherwise just try all TWRP versions you find - from high to lowest version. hope u will find a working one for LL.
Click to expand...
Click to collapse
Spaceboy60 said:
Ok tried FWUL. although my phone shows up on the desktop adb and fastboot don't see it.
Click to expand...
Click to collapse
Edit: upgraded to MM. Still get errors when i try to boot or flash twrp. Beginning to think there's something wrong with my phone.
Ok, I can boot TWRP using fastboot boot twrp-3.0.2-1-h815.img. However when I try to flash it I get the following error:
fastboot flash recovey twrp-3.0.2-1-h815.img
target reported max download size of 536870912 bytes
sending 'recovey' (16860 KB)...
OKAY [ 0.499s]
writing 'recovey'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.523s
Any ideas?
Thanks
Spaceboy60 said:
Ok, I can boot TWRP using fastboot boot twrp-3.0.2-1-h815.img. However when I try to flash it I get the following error:
fastboot flash recovey twrp-3.0.2-1-h815.img
target reported max download size of 536870912 bytes
sending 'recovey' (16860 KB)...
OKAY [ 0.499s]
writing 'recovey'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.523s
Any ideas?
Thanks
Click to expand...
Click to collapse
Good so it is actually a bootloader thing. Please read the official twrp thread (see my signature) and find the installation guide. The behavior above is expected and there is a way to solve. Just read carefully.
#
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Good so it is actually a bootloader thing. Please read the official twrp thread (see my signature) and find the installation guide. The behavior above is expected and there is a way to solve. Just read carefully.
#
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, so followed the guide from https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 (which was in your signature)
Installation
General Howto Guide
The general guide seems to do not work properly when it comes to flashing so here is an additional howto which seems to work 100%:
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
done.
You can now reboot into recovery again to check it has worked.
However, despite booting into twrp ok and flashing the recovery ok (according to twrp), when i restart the phone and go to recovery it's the stock recovery, not twrp.
Spaceboy60 said:
Ok, so followed the guide from https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 (which was in your signature)
Installation
General Howto Guide
The general guide seems to do not work properly when it comes to flashing so here is an additional howto which seems to work 100%:
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
done.
You can now reboot into recovery again to check it has worked.
However, despite booting into twrp ok and flashing the recovery ok (according to twrp), when i restart the phone and go to recovery it's the stock recovery, not twrp.
Click to expand...
Click to collapse
ok. do the same again but when you have flashed twrp from within TWRP grab the recovery log (like described in FAQ #4-A)
hope we get some meaningful information.. because this really should work.
EDIT:
oh and please try the latest BETA here: https://forum.xda-developers.com/devdb/project/dl/?id=22169 !
.
https://paste.omnirom.org/view/3f6a4e1e
https://paste.omnirom.org/view/72c6b7a1
Reboot to recovery worked within the booted twrp, just not when I turn the device off and try to enter recovery from the hardware keys. Using hardware keys and selecting Yes twice just took me to stock recovery which does a factory reset and wipes device.
Didn't try adb reboot recovery.
Spaceboy60 said:
https://paste.omnirom.org/view/3f6a4e1e
https://paste.omnirom.org/view/72c6b7a1
Reboot to recovery worked within the booted twrp, just not when I turn the device off and try to enter recovery from the hardware keys. Using hardware keys and selecting Yes twice just took me to stock recovery which does a factory reset and wipes device.
Didn't try adb reboot recovery.
Click to expand...
Click to collapse
ok thx will look into this soon.
In the meanwhile and because you mentioned it one more question: which hardware key combo do you try exactly?
#
steadfasterX said:
ok thx will look into this soon.
In the meanwhile and because you mentioned it one more question: which hardware key combo do you try exactly?
#
Click to expand...
Click to collapse
Volume down and power button together. Release power button for a second when LG logo appears and then press and hold it again until reset screen appears. Usually from there i select yes and yes again and twrp would appear (when it was working)
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Code:
D:\Programs\Minimal ADB and Fastboot>fastboot.exe flash recovery twrp-3.1.1-0-addison.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11374 KB)...
OKAY [ 0.255s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.246s]
finished. total time: 0.510s
Is there a way to avoid this error ?
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
FSabbane said:
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Is there a way to avoid this error ?
Click to expand...
Click to collapse
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Jimi Mack said:
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
Click to expand...
Click to collapse
I've changed the filename to "twrp.img" and used the command:
Code:
fastboot flash recovery twrp.img
The output is exactly the same as before.
Kap_Tutan said:
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Click to expand...
Click to collapse
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
FSabbane said:
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
Click to expand...
Click to collapse
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Kap_Tutan said:
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Click to expand...
Click to collapse
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
FSabbane said:
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
Click to expand...
Click to collapse
Did u unlock bootloader?
Yap it should be in pc adb folder
Kap_Tutan said:
Did u unlock bootloader?
Yap it should be in pc adb folder
Click to expand...
Click to collapse
Yes, I did unlock it with the unlock key received from motorola:
Code:
fastboot oem unlock UNLOCK_KEY
After that a message is displayed at each start:
your device has been unlocked and can't be trusted
ID: bad key
your device will boot in 5 seconds
Click to expand...
Click to collapse
FSabbane said:
Yes, I did unlock it with the unlock key received from motorola:
After that a message is displayed at each start:
Click to expand...
Click to collapse
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
flashallthetime said:
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
Click to expand...
Click to collapse
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
still doesn't work for me
FSabbane said:
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
Click to expand...
Click to collapse
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
This is not an error. If your bootloader is unlocked this message will display at every boot.
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
FSabbane said:
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
Click to expand...
Click to collapse
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
velpoori said:
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
Click to expand...
Click to collapse
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
Click to expand...
Click to collapse
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
velpoori said:
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
Click to expand...
Click to collapse
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
FSabbane said:
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
Click to expand...
Click to collapse
I will try once I reach home by 6pm, you are so helpful thank you...
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
Click to expand...
Click to collapse
It makes no sense then to flash it. Why don't you just use
fastboot boot twrp.img
when you want to start it? Then no flash will be involved, and twrp will be just booted for this single usage. You can repeat this whenever you need it.
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse
Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.
5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!