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.
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
You are not bricked.
In order to update to the new OTA you need to go back to fully stock LCB43B image. That means flashing stock boot, recovery and system. BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Then reboot to bootloader and flash the stock recovery and boot files.
Next, download the OTA and reboot into stock recovery (not TWRP) in order to update using adb sideboard. Use the guide here: http://forum.xda-developers.com/showthread.php?p=65607393
Hit thanks if this has helped.
bigdave79 said:
BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Click to expand...
Click to collapse
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
avelinosilva said:
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
Click to expand...
Click to collapse
No.
Boot to bootloader and type "fastboot flash system system.img"
You should not be in recovery trying to fastboot flash. It will not work.
Latest SDK is fine on Windows 10. Make sure you use the fastboot and ADB from the latest SDK.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
/-\
|
|
This
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
avelinosilva said:
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
Click to expand...
Click to collapse
Good to hear!
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
I was stuck for last 12 hours and watch was in bootloop. i tried flashin again and agin . Scott i love you :laugh:
i think it was that i was using old adb and fastboot. the latest ones helped. Also there is no need to flash twrp. Even if you get file sparce issue.
Salute to You :good::good::good:
Now i am back to LCB43B will try to update to 1.4 via stock recovery now
Yeah, the ADB / Fastboot changed with Lolipop. Anything pre-lolipop will give issues.
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
kurosen said:
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
Click to expand...
Click to collapse
If fastboot flashing boot and system images went well, you can safely reboot your watch. First boot might take a while but it should boot OK.
@ausi
ausi said:
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
Click to expand...
Click to collapse
@ausi, can you please post again the solution, the link doesn't work anymore!!!
I really need it!!!
Please help!!!
I am in the same ****!!!
My watch doesn't work anymore!!!
Thank's for anyone help!!!
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
This DUDE RIGHT HERE. Did it. This was the missing piece. My fastboot files simply weren't good enough. x!!
Android SDK Platform Tools did the trick for me.
Hi,
I have a unlocked bootloader and a rooted phone(OnePlus3). I was clean flashing to a newer cm14 nightly on my oneplus 3 when I discovered a while later that my phone wouldn't boot into recovery mode. After flashing TWRP recovery, I booted onto my phone and selected recovery in the advanced reboot menu however it started to flash into fastboot whether i tried to fboot into recovery or into fastboot. So i, maybe mistakenly(i'm not sure), flashed stock recovery in command prompt and now there seems to be ,arginal improvement as I think a recovery mode may exist however the screen is blank so i have to power off by holding the button for a couple of seconds before anything appears on the screen and it does but only for fastboot and booting onto the system. Please help, I want to revert to Stock Oxygen OS with TWRP recovery but am unable to do do. I find it imperative for this to get resolved as my phone doesn't have gapps and doesn't offer much use beyond browsing. Any help would be massively appreciated.
Thanks!
P.S I apologise, in advance, if i have broken any forum rules; please tell me if I have so i will know not to do so again
P.P.S I may not understand some procedures or terms mentioned so please explain fully what to do as if I'm a complete noobie
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
On a side note, what version of TWRP were you on? You need to be on the modified TWRP, not the official TWRP, for official 14.1 nightlies.
Hw4ng3r said:
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
Click to expand...
Click to collapse
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Log_0 said:
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Click to expand...
Click to collapse
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Log_0 said:
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Click to expand...
Click to collapse
Just the version that is "officially" released by TeamWin. I believe current official version is 3.0.2-1
Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Log_0 said:
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear!
Enjoy the phone!
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.