Develop Bugs

[Q] Very strange recovery issue

I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2

Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.

where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.

Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app

What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0

kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.

el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?

kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app

[Q] Can't access to TWRP Recovery

Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.

RegularSam said:
Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
Click to expand...
Click to collapse
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hmm, wait, maybe I didn't catch what you were sayin, with "try to look your bootloader" you meant "try to LOCK your bootloader" right?
Because yesterday I've made root with Magisk, if I try to lock the bootloader I risk to brick the phone, isn't it true? Thanks anyway for your reply.

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found the trick. I applied from fastboot the two commands that I mentioned:
fastboot flash recovery recovery.img
fastboot boot recovery.img
Only difference? I didn't run the Command Prompt as administartor, as I did yesterday (I also tried before this operations using PowerShell without success), WOW. Now before reboot the phone I allowed the modification to the partition in TWRP recovery, I saved logs from kernel and recovery and I'm trying to make a backup. I will tell you the results.
Yesterday I've also tried to flash the recovery by using Flashify without success, just sayin.
EDIT:
After rebooting the stock recovery returned. I hate this thing. I've also renamed this two files:
recovery-from-boot-p
install-recovery.sh
It didn't work.

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Click to expand...
Click to collapse
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.

RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.

CazeW said:
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
Click to expand...
Click to collapse
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?

RegularSam said:
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
Click to expand...
Click to collapse
Locking the bootloader will not cause a boot loop if you're rooted. The reason I asked what happens when you lock the bootloader is that the 5x had had issues with the emmc going bad. A sure sign of that is the bootloader not staying locked after locking it and booting back up.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seriously, this thing is driving me crazy. Tried to go with your suggestions but I can't boot in the recovery, no way. I have also flashed the original recovery and the tried to get in with fastboot boot twrp.img, no success. I can't figure out why I have this problem.
EDIT: great, now even flashing the stock recovery doesn't work, the phone reboot every time I try to get in any recovery. I have no words.
EDIT 2:
GUYS, I think I've found the solution. As I said in the main post, I was thinking that maybe the problem was due to the BLOD bug, in fact the common twrp.img that you can find on the twrp page uses all the 6 cores of the Nexus 5X causing the rebooting which I mentioned. Now, I found this version of twrp 3.1.1 which is modified to use 4Cores, thanks to the user XCnathan32 and his thread about BLOD bug: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199.
Now it seems like the TWRP Recovery is stick to the phone and I'm really happy to say that. Thanks for all your support, you were very patient!
Click to expand...
Click to collapse

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

back stock rom to pc

i have tried to install twrp on my 5x, 6, and 6p, with the same results "do loop". doing a twrp backup of the stock rom doesn't work as flashing it results in the same "do loop". is there a good "how to" on backing up my stock rom to my pc without twrp? i have lineage 15.1 on my 6p but doing the twrp format cleans all.

I don't see the point of backing up stock rom in first place, and I don't really know what's your problem, explain... more precisely. Your twrp can't stick in stock rom, or phone bootloop after restoring backup? Answering last question: you can get factory system image right from google's servers.

i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.

dr1445 said:
i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.
Click to expand...
Click to collapse
Just curious what type of "errors" you are having with flashing the stock ROM? Is it possible you need to download a newer version of fastboot/adb?

@73 the old memory is not that great but i seem to recall format error. when i got the phone from ebay i did the full stock setup up to the latest 8.1. i recorded that info and that was my first google firmware flash with no joy. i had to go back to android 6 before i found one that would flash. i am running linux xubuntu, which i keep updated.

If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.

nowster said:
If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.
Click to expand...
Click to collapse
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.

dr1445 said:
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.
Click to expand...
Click to collapse
Why are you trying to use TWRP to flash the stock ROM (granted, I've seen the option to flash ".img" files but never used for anything other than "boot.img"). You should be using a pc and "fastboot".

For flashing stock you should be using fastboot, or the stock recovery and an OTA image.

Boot hang, TWRP Recovery unresponsive

Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.

When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?

Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.

@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).

pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?

motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch

Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"

motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help

Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.

motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse

Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot

jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?

Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258

Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!

I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL

edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!