HI,
I have a serious problem with an update from first snapshot ZNH0EAO1QC to the second snapshot ZNH0EAO2NN.
The device was not rooted or otherwise altered and has the had the default cyanogenmod recovery. I have updated via update menu of the Z1. But restarting the devices from within this update process caused a bootloop.
Unfortunately it is not possible to go to recovery with power+volume, it also bootloops. Manually got to recovery gets the adb message:
su-wptnb8 /home/karbach: adb devices
List of devices attached
cfb1abbf unauthorized
su-wptnb8 /home/karbach: adb reboot recovery
error: device unauthorized. Please check the confirmation dialog on your device.
Unfortunately, the device stays black and nothing is shown
fastboot does endlessly wait for device.
Any idea?
Thanks in advance
Related
Since I'm a newbie here I can't post this problem to "[N10] CF-Auto-Root". If some kind person with permissions could alert the people there to this problem I'd really appreciate it.
I installed CF-Auto-Root on my Nexus 10, and after an OTA upgrade to 4.3 the tablet is seriously bricked. The sequence was as follows:
* Started from stock 4.2.2
* Downloaded the latest CF-Root (July 29)
* Manually re-rooted (as instructed on first page)
* Everything is peachy. su in adb shell works, get root prompt, etc. Browsed directories but made no changes.
* Attempted an OTA upgrade to 4.3 (Forgot to re-lock the bootloader). Upgrade failed, giving some generic (as in uninformative) error message. I think it was something about file check failed,
Now the tablet boot-up doesn't get past the colored X. I can get into bootloader/fastboot mode (robot on back with panel open). The device information is as follows:
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: MANTALJ12
Carrier Info: NONE
Serial Number: <looks okay>
Lock State: UNLOCKED
Reboot Mode Flag: NONE
This is where I was when I first loaded CF-Root. However, now "adb devices" on the PC (Arch Linux) gives a blank list of devices. When I try to load the factory 4.3 image with "fastboot -w flashall" the PC prints the message:
< waiting for device >
and sits there. Not surprising since adb can't see the device.
I can get into recovery mode (robot on back with red triangle), and can access the menu. Performing wipe data / factory reset hasn't helped. From my PC "adb devices" still shows a blank list of devices.
When I start the "Apply update from ADB" utility from recovery mode, "adb devices" on the PC shows:
???????????? no permissions
If I then enter "adb sideload <file>" on the PC as the prompt on the tablet suggests (the file I used was an Android 4.3 upgrade zip file), the PC responds with:
error: insufficient permissions for device
Does anyone have any idea how I can get my tablet out of this mess? Right now all I want is to get my tablet working again. Any ideas are most welcome.
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Solved
Got it solved (whew!). Had to run fastboot as root on the PC.
plastikowl said:
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Click to expand...
Click to collapse
Yeah, I knew I'd lose root, but I'd already installed CF-Autoroot. Figured it would be easy to root again after. Foolish me!
Afraid I forgot to write down the error so it's lost. I was trying to do a full flash but failing (see my "solved post"). The update attempt was desperation, trying to get to the tablet somehow.
Anyway, I managed to do a full flash to the 4.3 factory image, so my tablet is no longer an expensive paperweight.
Thanks very much for yout input.
Since I coudn't find any rooting guide in this forum I followed the this guide: http://www.theandroidsoul.com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
I successfully unlocked the bootloader. The next step is flashing TWRP and that's where my problem begins. I downloaded the latest TWRP image for my HTC U11 and issued fastboot flash recovery twrp-3.1.1-0-ocn.img.
When I tried to reboot into the recovery I only saw a screen with a smartphone showing a red sign with an exclamation mark. Seems something went wrong flashing the recovery.
Unfortunately since then adb doesn't seem to work any more. I managed to reboot the phone and everything is working but whenever I connect my phone to my windows laptop and issue adb devices I get the following error message:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
That's the reason why I cannot flash the recovery again. What are your suggestions now?
Helped myself. Even though adb still gave me the very same error message in download mode I was able to issue the fastboot flash recovery command again (fastboot devices did list my phone). This time it worked and now I successfully booted into TWRP. Guess you've got to be in download mode when trying to flash the new recovery. Puh...
simu_lacrum said:
Since I coudn't find any rooting guide in this forum I followed the this guide: http://www.theandroidsoul.com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
I successfully unlocked the bootloader. The next step is flashing TWRP and that's where my problem begins. I downloaded the latest TWRP image for my HTC U11 and issued fastboot flash recovery twrp-3.1.1-0-ocn.img.
When I tried to reboot into the recovery I only saw a screen with a smartphone showing a red sign with an exclamation mark. Seems something went wrong flashing the recovery.
Unfortunately since then adb doesn't seem to work any more. I managed to reboot the phone and everything is working but whenever I connect my phone to my windows laptop and issue adb devices I get the following error message:
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
That's the reason why I cannot flash the recovery again. What are your suggestions now?
Click to expand...
Click to collapse
Wait for a limited time and try again, if failed read this tutorial video:
https://www.youtube.com/watch?v=aOkDjaqspGQ
Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.
Oria Maymon said:
Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.
Click to expand...
Click to collapse
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like
zukcyprus said:
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like
Click to expand...
Click to collapse
I can't because device is not recognized via fastboot and I have to save user data
Sent from my Robin using Tapatalk
In my case I erased everything...and throw my gmail I recovered everything..and don't install after cyanogen ROM ...if you can install zui xosp hexagon viper mokee or nuclearom .
Try this: https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!
Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!
Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.
Hi all,
I used "adb sideload" method to update my S10+ (AUT) to oneui beta 2. Now I'd like to update to beta 3 but when in recovery "adb devices" doesn't see my device anymore so I cannot sideload. When I reboot to system, "adb devices" shows my device without problem. I'm using stock usb cable.
Any help greatly appreciated.
EDIT: I was trying on OSX so I checked on Windows 10 and the result was the same.
EDIT2: Ok, so I went back to Pie 9 with ODIN. After that, ADB in recovery mode is back to normal. I used "adb sideload" to install beta 2, all fine, boots fine. But when going back to recovery, I get errors and device is not visible with "adb devices" once I choose the ADB update method.
This message on the phone when entering recovery mode:
#Reboot Recovery Cause is [BL:Recovery Mode Set by keys]#
E:[libfs_mgr]Unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing
E:[libfs_mgr]Failed trying to run /system/bin/e2fsck
Supported API:3
And then upon choosing ADB update mode:
# MANUAL MODE v1.0.0 #
Now send the package you want to apply
o the device with "adb sideload filename..."
EDIT3 : I cleared cache partition and factory reset. Now the errors are gone when entering recovery but phone still not visible with "adb devices" after entering adb update mode.
EDIT4: Ended up reinstalling only recovery from latest pie through ODIN as adb sideload as that one worked to sideload pie -> beta 2 but alas "adb devices" doesn't recognize my device. Conclusion, once updated to beta 2, I cannot use adb sideload to install beta 3. Any help appreciated
I have the same issue as you do on the S10+, except my recovery was corrupted from the beginning, on stock pie ADB sideload couldn't load due to missing usb node and configfs file.
I flashed multiple times with ODIN and it didn't bring ADB back. Luckily I had an old SD card laying around, so I have been able to flash each beta .zip from that. I've been checking ADB at each beta version, and as far as I can tell, my ADB keeps throwing the same error as yours...I'm not sure if this is a Samsung beta issue, or if our phones are just special.
Hopefully, you can continue to install the betas using an SD card.
I had the same error whem trying to flash the beta 3 update, but i solved it aplying the update.zip from a SD Card and all worked. Like the above post.