Related
I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.
Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
if fastboot flash doesn't work you probably have fastboot locked.
brando56894 said:
if fastboot flash doesn't work you probably have fastboot locked.
Click to expand...
Click to collapse
Thanks mate. Do you know how to unlock fastboot?
ilpolpi65 said:
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Sway327 said:
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Click to expand...
Click to collapse
Are you able to get back into system? If so, run this command with an active ADB connection.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Hi, I was wondering if you were able to fix your tablet. I have this problem right now and haven't found any way of fixing it.
NYCHitman1 said:
Are you able to get back into system? If so, run this command with an active ADB connection.
Click to expand...
Click to collapse
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
viii_xvi said:
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
Click to expand...
Click to collapse
Did you get your tablet to work? I have the same problem
qAnAthemA said:
Did you get your tablet to work? I have the same problem
Click to expand...
Click to collapse
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
viii_xvi said:
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
Click to expand...
Click to collapse
Have you tried to ask Google for a USB bootable recovery + ZIP file ?
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
My ZE551ML is unlocked/rooted running the stock MM from asus, everything worked fine for a long time now.
This morning my phone booted in TWRP, and whatever I try, it always boot in TWRP. The only thing I know has changed is that yesterday Magisk installed an update.
How can I recover my phone? adb is working, I can go in TWRP, but what else?!?
Try wiping your misc partition:
Code:
adb shell dd if=/dev/zero of=/dev/block/by-name/misc
Problem was Magisk v11.5 that updated itself, it is not signed. I restored a previous boot backup and back in business.
So people, do not update Magisk using their builtin updater!
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
michi6278 said:
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
Click to expand...
Click to collapse
hello, same problem here. i update the magisk and all go wrong.
i fixed the problem only flashing the magisk again, in the TWRP.
and boot works fine
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
itizar1 said:
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
Click to expand...
Click to collapse
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Kaisogen said:
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Click to expand...
Click to collapse
You dirty flashed your rom then. Everytime you update, first wipe your system (not data!), then flash everything you need (not sure about gapps and stuff, just flash them to make sure)
Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M
xoth said:
Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M
Click to expand...
Click to collapse
Magisk installed?
Can you boot into download mode?
kurtn said:
Magisk installed?
Click to expand...
Click to collapse
No, what's that?
Can you boot into download mode?
Click to expand...
Click to collapse
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?
xoth said:
No, what's that?
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?
Click to expand...
Click to collapse
Yes, sorry. From there you can install stock ROM or twrp.
kurtn said:
Yes, sorry. From there you can install stock ROM or twrp.
Click to expand...
Click to collapse
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)
xoth said:
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)
Click to expand...
Click to collapse
In fastboot mode you don't need adb. You need fastboot.
kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ooooooh, ok! Yeah, that makes sense. (In my head fastboot was always something using adb, not something completely different.)
Ok, so I should be able to fastboot to something like twrp, hopefully make a backup there, and then try and flash something else on it? I'll see if I manage that, thanks! :fingers-crossed:
kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?
xoth said:
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?
Click to expand...
Click to collapse
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either
kurtn said:
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either
Click to expand...
Click to collapse
Very funny. Dying of laughter over here...
But seriously, this is LOS regular file encryption, I know the correct pattern, so I'd expect something mature like TWRP to be able to mount that. But all I've found so far are open bug tickets of this happening over a range of devices.
Quick Update: I managed to get my device running again using the following steps:
1. Fastboot into twrp.
2. Go to Advanced -> ADB Sideload and activate it there.
3. Sideload an earlier LOS 16.0 nightly. (In my case, I used 16.0-20200322-nightly-payton-signed.zip.)
4. Reboot.
5. Do all the backups.