Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Kris the wizz 15 said:
Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Click to expand...
Click to collapse
and Now you have another brick in the wall... i'm really sorry for you.
puntoazul said:
and Now you have another brick in the wall... i'm really sorry for you.
Click to expand...
Click to collapse
I haven't given up yet. The way I see it, the only option I have is to figure this out, as it will prove invaluable for others. If I figure this out, then it will be impossible to completely brick this device, a critical factor in this time of development. Inevitably, someone else will brick their device, and if we can find out how to fix it, then it will be of great benefit to all, don't you think?
I also need some help... my huawei mediapad 7 youth (no sim) is on bootloop.... no recovery mode working ... but I can update firmware .. every time I updat3 it ..showing sd fails.. any help..
Related
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Tech1381 said:
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Click to expand...
Click to collapse
Most definitely not bricked. I've recovered from a much worse situation (bootloader wouldn't even budge - couldn't boot into recovery or regular at all).
Since you are able to boot into recovery, there's probably a way to get things working without resorting to nvflash (we'll get to that in a second - nvflash is the failsafe mechanism, and you should be able to re-nvflash your tablet back to its original state if all else fails).
Here's roughly what I'd try in order:
Option 1) Figure out why you are unable to mount as USB in recovery. I've actually never heard of this problem. Are you using the right cable - i.e. a working USB-to-mini-USB cable (I don't think this works at all with the full sized USB port under the latch cover). Have you tried it with another computer - perhaps there's a driver issue on your PC?
Option 2) If for some reason you really aren't able to get USB mounting working in recovery (I'm skeptical - again, I've never heard of that problem - unless you really did flash a bum recovery image or something - but seems unlikely), then I'd see if you can get ADB working properly when you are in recovery mode. Search around and read about setting up ADB if you haven't already - just a matter of getting the right driver installed on your PC and installing the binary stuff (either from the full Android SDK or one of the packages that just has the ADB stuff floating around). Search the forums, you'll find some references to help you get this working and download the right stuff.
If ADB works, you can always use "adb push filetoflash.zip /sdcard/filetoflash.zip" to put a new file on your internal SD card area and flash it.
Option 3) You can always use nvflash. I'm not going to write up a tutorial on it here - search the forums for nvflash, there are several HOWTOs. Look for the stuff Roebeet posted. You'll need to install the APX driver on your PC first before this will work, and Roebeet's posts don't explain how to install it on Windows, so you'll need to search separately for that. I have gotten this to work before, but it's a pain and I only recommend it if your recovery image is truly trashed or your bootloader is malfunctioning as mine was. In other words, don't bother until you've exhausted the first two options.
So in short - you are in a pain-in-the-ass situation, but you have by no means bricked your tablet - it is very, very far from bricked. Give us more info on *exactly* what happens when you try to "mount as USB" while you have your mini USB cable plugged into the G Tablet - do you see a drive appear on your PC? Are you running a Windows box? Mac? Linux? Have you verified that a USB keychain drive works fine with your PC but the G Tablet won't mount? Basically we need some more info to guide you in your search.
Ok finally had some free time from cleaning/packing and house hunting to try fixing the tablet.
Good news is that I was able to mount the USB. I didn't notice the cat nibble on my cable... So once I dug a spare out, I was able to copy a TnT-Lite image (still had on computer) onto it right quick. Restarted and it installed the image.
So now it has TnT-Lite, though it is weirdly stuck on the setup wizard. It tells me to touch the android to continue and shows an animation of a hand touching the android. But when I touch the android, it turns white and thats it. Also I can change the language to UK or American English. Plus when I press the menu button, I can go to wireless settings, as in cell phone wireless settings. Lastly, I can make an emergency call. So new worthless image. YEY!
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
So how do I go about screwing it up more?
Tech1381 said:
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
)
Click to expand...
Click to collapse
CWM is not installed
flash the latest firmware using stock recovery
read read read
http://forum.xda-developers.com/showthread.php?t=892090
It almost sounds like you now have stock recovery in your Gtab.
If that's the case, then maybe copy a stock TNT update.zip onto the external Sdcard, and create recovery/command file on there with the string for SDCARD2, then reboot w power and volume+. If you do have stock recovery, that should flash it back to stick TNT. Try Stock TNT 3452, since that'll also flash a stock recovery for sure.
Jim
Looks like Brian and I crossposted each other .
For the recovery/command file on the external SDCARD, put the following text in it:
--update_package=SDCARD2:/update.zip
NOTE THE 2 DASHES AT BEGINNING OF THE LINE...
Jim
No really, I've Bricked It
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
f3justusc said:
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
Click to expand...
Click to collapse
I'm freaking out, I think I bricked it...
I'm only getting the black android screen, I can't seem to mount USB, suggestions?
Ive been stuck right where you are a few times, not to big of a deal, just NVFlash back and start over. I am assuming you are getting the black screen you mention is the APX mode one you get by starting your tab by pressing vol down and power at the same time.
I'll put the question first for those not wanting to read the details.
I cannot get into CWM (internal) on my 16GB nook tablet. I can boot to CWM (external), but nothing works. When I try to activate ANY menu option, it takes me to a blank screen with the CWM hat logo in the background. Pressing power returns me to the main menu. Not even "reboot device" works. Can someone help? (I want to do a backup before i flash a JB Rom (internal), and to flash a JB Rom)
Now the long part:
I purchased and rooted my NT in December 2011 (about the 21st) using the snowball root (incase you are not familiar, as I don't see any post about it now, it was a modified zerg root borrowed from Albert's root method that with one menu option allowed rooting, recovery, and removal of certain nook apps and the addition of your choice of three launchers). I used it successfully on three nooks within a month or so, but this is the only one I did the complete nook removal option to.
Root works fine, but debug does not. When I run the NT hidden settings app to turn on debug mode, the developer options are listed twice (one compete set followed by another), this did not happen until after rooting, before they were only listed once. The bottom set was correctly checked to allow debug mode, and its how I rooted; however titanium backup says debug is not enabled every time I load it. (No complaints from RTB Pro) So I go into the developer settings and found two sets, the top one not checked... When I check it I get the pop-up warning, if I uncheck the bottom one, then debug does not work, if I check the bottom one I don't get the pop-up warning. With both checked, adb works, otherwise it does not. It had been this was since December 2011, and has not really prevented me from doing anything, although as the pop-up warns somethings may not work (converting apps to/from system, merging system app updates, restoring system app backups) and cause titanium to hang, but after a manual force close of titanium, most of the time the change was successfully completed.
Now, moving on one day I was being up my phone and thought "I can't remember the last time I did a nandroid of my nook" so I used RTB to reboot into recovery, the nook booted right back up into android, no errors, no different screen than a normal boot (with the nook --> hack logo, which incidentally takes about 12 minutes to boot every time, not sure if that is normal). So I tried an adb reboot recovery, but adb said no devices were attached. I went back into NT hidden settings and due enough debug was unchecked on the top, but still checked on the bottom (I've learned it lose it every reboot), do I rechecked it, got the pop-up, and went on my way. Adb reboot recovery also restarted my nook back into the OS, not into CWM.
I started to think that I may never have installed CWM, so I checked the root package I downloaded and viewed the script, first thing it does its copy the recovery image to the device, even before rooting, then installs it right after rebooting, post root hack. I thought maybe the posh was bad flash, so I searched XDA, downloaded a newer CWM, and manually adb pushed it to the phone and dd it per the instructions in the XDA thread. Reboot recovery, still nothing.
Please note I CAN get the factory reset screen to show up, but really don't want to try it without a backup, as I've been using my nook like this for 12 months and only have a titanium backup of the apps.
So I made a CWM SD from the NT thread here on XDA and booted to it :-/ intending on flashing 6.0.12 CWM to the internal emmc, the recovery on the SD was 5 something and none of the menu options worked, as mentioned above pressing power while any are selected gives a new screen with the background image, but no options. Pressing power again takes me to the main screen (same thing when selecting reboot device).
So I found a newer CWM SD package on XDA and swapped them out, this time a newer version 5.5.x, no change in how it works, so downloaded 6.0.12 and renamed the recovery image file and booted the SD. Small change this time (beyond the new version number and the option to power off, which also does nothing), when pressing the power button to select a menu option, the screen refreshes, but continues to display the same menu choices for all options in the menu.
I have also tried pushing each of these recovery images to the device and using adb to dd them to the recovery partition. Three nook will only boot the SD clockwork image.
Yes I made sure to select internal images for dd to the nook and external images for the SD.
So last night I installed nook tab recovery flasher, it said it successfully installed, before I clicked yes to allow it root access... the pressed the reboot recovery button, no good. So I downloaded and installed goo manager from the market and had it flash TWRP, same thing, reboot recovery ignores it.
Now to repeat my question, anyone have any clue how I can get recovery working spp I can make a nandroid and flash a JB Rom? (I know I can make a backup using adb, and Iam pulling one now, but I am wanting a recovery (that works) on my nook.)
Also, I am willing to try an adb push install of the Rom, I think I can make it work (although Ihave never tried it, on any device, I might be able to do it without further help), but I do not see how a new Rom will make any difference on my recovery situation and if I screw up, it would be comforting to know I had a working recovery at least.
Sent from my VS920 4G using Tapatalk 2
For selecting an option in recovery is N button not power one
Sent from my Xperia S using my fingers to swype.
Your question belongs in Q&A with all other questions and not in development. Only work being shared belongs there.
Thanks
AvRS
Caught that, and was able to flash CWM 6.1.15 (emmc) from the SD; but still cannot get to it.
Power+ nook= regular boot
Power+ vol up+N= regular boot
Power+ vol up= regular boot
Power+ vol down+N= regular boot
Rom toolbox pro reboot recovery = regular boot
Adb reboot recovery= regular boot
However, using goo manager to reboot recovery works, sort of...
I get the cyanoboot screen, hold N, use the menu to get to emmc internal recovery and I get CWM.
Now the problem starts about 3-7 minutes later (have not tried timing it, but it seems to be the exact same length of time each time), the nook reboots, don't matter what I am doing, using it, creating a nandroid, adb push or adb pull out apparently flashing cm10...
I decided to try a flash of cm 10 from a 11-28 build with multi touch firmware for 10 points. All was good, but I had to step away for about 2 minutes... I sneaked a peek and all was well, then when I got back my nook was on the "read forever" logo and has now been that way for 20 minutes. I checked the updater script in the Rom and it does NOT have a reboot command at the end.
I'll give it another 20 before ring to get back to CWM with out goo manager...
Sent from my VS920 4G using Tapatalk 2
Update
So, no change. Hiding the power button shut it off, I also tried plugging the usb cable in to activate boot, this causes a regular boot, which at this tinge never gets to "nook" but stays on "n" "read forever" which makes me laugh as it is currently the only thing I will "read forever" until I fix it.
Next up is to try to flash from an SD.
Update to my update
Booted from the SD, wiped everything three times, flashed the Rom, rebooted and ended up with TWRP, multi-touch and JB. Reinstalling apps through the market now, hoping previous issues are gone.
I successfully rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=2130276
Then I tried the following method to modify multi-window on the phone:
http://www.andromods.com/tips-trick/verizon-galaxy-note-2-adding-all-apps-to-multi-window-bar.html
And ran into this problem on this step:
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
PROBLEM: THE PHONE FROZE. THEN WHEN I REMOVED AND RE-INSTALLED THE BATTERY AND TURNED IT ON, IT LOADS UNTIL THE 4GLTE SCREEN AND REMAINS THERE INDEFINITELY.
- I did what it directs to do with the battery but it didn't work.
- I don't know what it means to "flash the root image with ODIN"
I've tried this to fix it:
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
and I believe maybe another thing with odin. Odin usually fails, maybe it's just my USB drive. But i have no idea what to do, or what to even look up to learn how to fix it because I don't know what my problem is called.
Can anybody help me by giving me a method to use or steps to follow or some information?
Try this
http://forum.xda-developers.com/showthread.php?t=2040264
It is called a boot loop by the way
God bless the American people.
barrackOBAMA said:
It is called a boot loop by the way
Click to expand...
Click to collapse
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Milimbar said:
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Click to expand...
Click to collapse
That's right, you understand. and perhaps I just don't know what it means but, I don't think it "freezes" on the 4GLTE screen, it loads until that screen and then continues to be animate, rings appearing and disappearing, loading indefinitely. I don't know if that's anything different, but just in case that clarifies anything.
and I tried http://forum.xda-developers.com/show....php?t=2040264 but to no avail. it always fails @ or immediately after the RECOVERY step.
Any ideas?
I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.