I had a rooted, unlocked, unencrypted stock firmware running lyz28j. I then sideloaded, and had it re-encrpyt with lyz28j. I then wanted to go back to lock the firmware, so I locked it via fastboot, rebooted, and now it's just doing the dancing balls boot thing. It has been for 2-3 hours. So i've tried googling, found a few with the same issue, but now I am stuck because the device is locked status code 2. I tried fastboot format and fastboot format userdata and rebooted, gave it a half hour, still dancing.
I also tried nexus root toolkit with no luck.
Not sure what else I can try? I do not care if I lose data, as I already backed up, so I am down to try anything.
vivithemage said:
I had a rooted, unlocked, unencrypted stock firmware running lyz28j. I then sideloaded, and had it re-encrpyt with lyz28j. I then wanted to go back to lock the firmware, so I locked it via fastboot, rebooted, and now it's just doing the dancing balls boot thing. It has been for 2-3 hours. So i've tried googling, found a few with the same issue, but now I am stuck because the device is locked status code 2. I tried fastboot format and fastboot format userdata and rebooted, gave it a half hour, still dancing.
I also tried nexus root toolkit with no luck.
Not sure what else I can try? I do not care if I lose data, as I already backed up, so I am down to try anything.
Click to expand...
Click to collapse
If have TWRP can move a rom from PC to Internal storage and flash it. That about only chance I think.
and if you have stock recovery, theres nothing that you can do except try to get a refurbished phone in exchange.
wow, I got kind of lucky this worked, but I went to recovery, power + up button at the lil ! dude and wiped device, rebooted, and it let me in.
It even barked about a few mounts not existing, or being able to write to them.
Related
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Starcruiser322 said:
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Click to expand...
Click to collapse
Was there ever a resolution to this?
I believe I might be having the same issue.
Sent from my LG-VS980
Well, it was sort of resolved for me. If you follow the steps in THIS THREAD, you better hope you have enough battery to last through the process. If you do, great, you'll have your phone back in running order soon enough. A bit of Linux experience helps with this.
After my battery died it refused to come back on, and I brought it to the Verizon store and told them I woke up one day and it wouldn't turn on.
They replaced it under warranty.
I assume other major carriers would do the same.
Is your phone still under warranty? What model and carrier?
After a bit of searching, I did confirm that the 26A update locks the bootloader and implements tighter security policies.
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
madeofscars117 said:
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
Click to expand...
Click to collapse
Make sure you have latest HTC drivers installed on your computer, relock your bootloader and then launch the 6.23.651.6 RUU
Wow, I dont know why I didnt think of that. Everything must be running together.
Alright, so it updated. My phone is back to how it used to be looping like when it first broke. So, from here. Should I unlock it, flash the recovery to cwm, relock bootloader and see if it enters cwm recovery and try to push or sideload a rom?
when relock, i beleive it restarts, so i dont know if it that would stop the cwm recovery from working. Also, if i manage to get all of what i mentioned working. Wouldnt I get the 12 signature error?
Im sorry, its been days and nothing seems clear anymore since I havent been able to fix it
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.