Related
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
I was feeling adventurous and installed O on my Pixel, played with it for a few days and decided it wasn't quite stable enough for me. Right out of the gate, first boot I had a force close on the Settings App (something persistent about notifications on the lockscreen). Then following that I was having data connection problems...I don't have strong signal at my house to begin with but (thus far) with N I usually had 2 or 3 bars of LTE, while O only gave me 1 bar of LTE if the wind was blowing the right way, but I was usually confined to 2-3 bars of 3G while at home. Long story short I wanted to go back to Nougat just for stability sake.
After attempts to just downgrade using factory images from 8.0.0 to the July release of 7.1.2, I was unable to open TWRP.
Finally, I flashed Oreo back on, used the modded TWRP for O, and I did a full factory reset including internal storage, data, system, dalvik. Then I used Stock July 7.1.2 flashall.bat (included -w), used fastboot for O-compatible TWRP.img so I could switch slots, then I used the 7.1.2 flashall.bat again while on the other slot. after this, I was able to successfully boot into a fresh clean 7.1.2 (also was able to flash/boot older TWRP.zip)
Long story short, now that I'm back on 7.1.2, I am having similar connection problems I was having on O... that is, it prefers 3G instead of LTE at home. When I drive around and switch between towers I cant send messages until I switch Airplane Mode on/off, my messages app (although completely fresh) shows an odd "loading effect" underneath my actual texts.. I've seen this "loading effect" before but only after using TB to restore my texts.. I no longer bother with backing up/restoring texts so Messages should be totally clean, right?
I guess my question is, did I do everything right to fall back from O to N or did I miss something? Do the radios not downgrade? Is there something that just didn't get wiped fully?
If someone would be so incredibly generous to offer a step-by-step on downgrading fully, successfully, I would appreciate that soo much!
Thanks in advance
I don't quite get your method steps order,,,
However, I think I read that you did flash-all for 7.1.2 then did some slot jumping with TWRP...
I recommend another full wipe and flash-all, of 7.1.2 or 8.0.0, and start over without TWRP for now
Sent from my sailfish using XDA Labs
nednednerb said:
I don't quite get your method steps order,,,
However, I think I read that you did flash-all for 7.1.2 then did some slot jumping with TWRP...
I recommend another full wipe and flash-all, of 7.1.2 or 8.0.0, and start over without TWRP for now
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
That's correct. I did a flash-all for 7.1.2, then used the modded TWRP for O image (fastboot boot image.img) so I could change from slot b to a. I read somewhere else on XDA that you had to switch slots when downgrading and then flash again because simply downgrading on only one slot left behind some partition changes, but switching slots and flash-all again would correct the partitions.
I will try again using fastboot to switch slots.. I dont know why I didnt just do that to begin with.
I will report back, thank you in the meantime.
jake5253 said:
That's correct. I did a flash-all for 7.1.2, then used the modded TWRP for O image (fastboot boot image.img) so I could change from slot b to a. I read somewhere else on XDA that you had to switch slots when downgrading and then flash again because simply downgrading on only one slot left behind some partition changes, but switching slots and flash-all again would correct the partitions.
I will try again using fastboot to switch slots.. I dont know why I didnt just do that to begin with.
I will report back, thank you in the meantime.
Click to expand...
Click to collapse
For some reason, but I haven't read all downgrade threads, flashing 7.1.2 would seem it should be not used with the 8.0 TWRP.
If you can switch slots with fastboot and do the flash-all twice, hopefully that works, or do the 8.0.0 flash-all again (maybe on each slot) but boot up and setup completely before doing any boot mods. That helped me several times when flashing the whole factory image, to boot up completely instead of rushing the process.
Also, there may be a specific change to vendor.img or another that
fastboot flash --a (or) --b xxx.img
would help with if flash-all is too automatic
Sent from my sailfish using XDA Labs
nednednerb said:
For some reason, but I haven't read all downgrade threads, flashing 7.1.2 would seem it should be not used with the 8.0 TWRP.
If you can switch slots with fastboot and do the flash-all twice, hopefully that works, or do the 8.0.0 flash-all again (maybe on each slot) but boot up and setup completely before doing any boot mods. That helped me several times when flashing the whole factory image, to boot up completely instead of rushing the process.
Also, there may be a specific change to vendor.img or another that
fastboot flash --a (or) --b xxx.img
would help with if flash-all is too automatic
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
At one point yesterday I'm pretty sure I was rushing things. I did a flashall for an older version of 7.1, I think from april or may, then immediately tried to hop into TWRP (older version for 7.1.x) and it kept erasing all my internal storage between boots. Looking back, that must have been because I didnt let Android boot yet and it hadn't *actually* created a fully functional Internal Storage yet.
I just tried your suggestion of doing a full wipe and staying out of TWRP for now. I was able to use fastboot to switch slots between flashalls. Currently waiting for all the app updates to complete. On a positive note I currently have 2 bars of LTE. Unable to comment on Messages or connection reliability at this time.
Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.
More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.
update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.
I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
I had updated from my oneplus 2 to the oneplus 6. and with great ease was able to unlock,flash android P.
Bad to hear that you are facing such problems, as my switching was error free.
One of the solutions which you could try for the Zip signature verfication:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
inderjeet.c7 said:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
Click to expand...
Click to collapse
I have tried TWRP with both the current 3.2.3.0 and the previous 3.2.3.2, both downloaded from twrp.me. Sideloading failed, too. Same zip signature error.
I may have to wipe the device and start over yet again. I'd blame myself for doing something wrong, which may very well the the case. But the zip signature issue was there before I installed anything with the stock system.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
Try this https://www.bouncegeek.com/fix-signature-verification-failed-oneplus-devices/. I don't know if it'll work for your device as this is for one plus 5t but they are similar in this regard. I would also download all files fresh to make sure there is no corruption. Also disable any lock screen security (finger print, Pin, face lock, etc.)
Among the things I've tried were that I had happened to find that article earlier. Some of it, I can't do. Like clearing the cache of System Update. I'm not seeing that listed in the Apps on Oxygen like it may have been on Hydrogen. One thing I did do, though, almost the only thing, before unlocking and rooting, was to let the system update with an OTA from 5.18 to 5.19. So that could have played a role based on the article's premise.
In any case, I can't sideload, I still get the zip signature failure in spite of what the article says. I tried the other approach. I'll try again later.
This is frustrating. I bought this phone in no small part because it can be rooted and there is a dev community for it. But if I can't do with it what others are and what I want, it may not be worth keeping. I wish I knew exactly this failure is occurring. That it's not rare, I get. But maybe there's nothing wrong with the files. Can all these repeated downloads be bad ones? I've tried both transferring from my Mac via ftp and downloading directly from the web to the phone.
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
helioXverse said:
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
Click to expand...
Click to collapse
Yes, I'm booting into TWRP via that command line. It's not permanent. I tried to flash the TWRP zip, but signature verification failed. That was the first of my various failures. If I can't find a way to get this straight, I may return the phone, or at least try and get them to trade it to me for another.
Is your oem lock checked?
netgar said:
Is your oem lock checked?
Click to expand...
Click to collapse
Do you mean is "OEM unlocking" toggled on in Developer Options? If so, yes, it is and has been.
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
NickStrupat said:
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
Click to expand...
Click to collapse
Interesting. I didn't try going back that far. I ended up abandoning zip signature verification and am just flashing without it. So far, no problems.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.