Develop Bugs

[JailBreak Issue] Windows RT locked out by BitLocker infinity loop, won't boot up

I'm not sure where this threat should goes, as it should be Windows RT Troubleshooting but there isn't such forum. Please don't delete it.
The Problem:
Now, if I turn on Surface, under the Logo it says "Preparing BitLocker recovery"
and ask me for BitLocker key to continue.
After I enter the key, the "unlock" was successful and goes to Recovery,
but everything after that failed:
1. If I choose Exit and continue to Windows RT, I got locked out again and everything above happened again. Infinity loop.
2. Same thing if I choose Turn off your PC, I turn it on and I was again locked out.
3. Automatic Repair couldn't repair, Refresh& Reset stuck on 1%.
How this was caused:
I had my Surface RT unlocked (jailbreak) using Netham45's RT Jailbreak Tool 1.1.1 during that boot:
I was using a normal Metro app (PPTV) to download some video just as usual, and I closed my cover to put it in sleep mode. Several minutes later I found out the power was off (it suddenly shutdown) , from then it stays in the locked out infinity loop.
I have seen similar situation when "testing signing mode is on":
mamaich said:
But be careful when hacking. There are known problems with BitLocker when test signing mode is on. The OS simply would not boot. Lets hope that we could disable BitLocker on our devices...
Click to expand...
Click to collapse
(The Original threat this came from)
So it might because the sudden shut down didn't turn of the test signing mode, so BitLocker locked me out.
Anyone has idea what to do to make my Surface working again? Anyway to disable test signing mode using Command Prompt? I don't care about my files inside!

shog7n said:
So it might because the sudden shut down didn't turn of the test signing mode, so BitLocker locked me out.
Click to expand...
Click to collapse
Seems unlikely, as the "jailbreak" is in-memory only. More likely some catastrophic corruption of storage happened.

This is not a dev or hacking issue; this thread belongs in General or Surface if it belongs anywhere on XDA-Devs at all.
I'm going to agree with schettj here; this sounds like storage corruption. Contact support and see if you can get a warranty replacement. Don't mention the jailbreak, obviously, but since it is in-memory only it shouldn't matter (although it's possible that the jailbreak might cause a kernel memory corruption that messes up the storage stack but doesn't cause a bluescreen, this seems unlikely).
Incidentally, if it's a production device, you can be sure you weren't in testsigning mode to begin with unless there's a lot more hacks out for RT than I'm aware of; the SecureBoot configuration prohibits testsigning. Also, you shouldn't be getting asked for the BL recovery key unless you messed with either the bootloader or the EFI image. If you didn't do those things and are getting prompted anyhow, that reinforces the likelihood of a problem with the device storage.

This is (most likely) nothing to do with the jailbreak. If you can get your hands on a recovery drive you may be able to use it to reinstall windows, else take it back to MS and don't mention the jailbreak to them.

Or just decrypt the bitlocker volume from the recovery mode. It would be automatically reencrypted at the next boot.
To decrypt - boot to recovery with CMD, enter bitlocker recovery key, then run the command "manage-bde.exe -off c:"
this would start the decryption process and exit immediately. To check the progress - periodically type "manage-bde.exe -status". Here is the tool command line reference: http://technet.microsoft.com/en-us/library/dd875513(v=ws.10).aspx
But in the case if this is a disk corruption - I'd recommend to checkdisk it first from the recovery console ("chkdsk c: /offlinescanandfix").

GoodDayToDie said:
Also, you shouldn't be getting asked for the BL recovery key unless you messed with either the bootloader or the EFI image.
Click to expand...
Click to collapse
BitLocker recovery key is asked on every boot into the recovery environment, otherwise it would be unable to mount the C:, at least on my device I see this behavior. It may be kept in TPM - I don't know, but my device always asks it in recovery.
Once I was able to permanently decrypt the disk so that it was not reencrypted at next windows boot - but I don't remember what I've done, and I've trashed all settings when playing with recovery USB

A fair point. But, it shouldn't *be* booting to recovery unless the button combo to do so is pressed, or that option was selected at shutdown. Typically, you would at least get a bootloader menu offering a normal bootup or a recovery session...

GoodDayToDie said:
A fair point. But, it shouldn't *be* booting to recovery unless the button combo to do so is pressed, or that option was selected at shutdown. Typically, you would at least get a bootloader menu offering a normal bootup or a recovery session...
Click to expand...
Click to collapse
If the bootloader fails to load the core resources (winload.efi, ntoskrnl.exe, I believe) that are required on the system partition it should automatically boot to recovery.

Recovery
I've ran into a similar situation, when I played around with some startup options for the Surface. The only way I was able to recover was to reset the settings on the Surface. (OS Refresh) You can try the other recovery options, like system restore, or try booting into safe mode. If you can get to safe mode you can try disabling the startup of the Jail Break tool. If that doesn't work than I doubt the jail break was even related to the problem you are experiencing. (it is already highly unlikely that this is the case.)
Good luck.

Zephnath said:
I've ran into a similar situation, when I played around with some startup options for the Surface. The only way I was able to recover was to reset the settings on the Surface. (OS Refresh) You can try the other recovery options, like system restore, or try booting into safe mode. If you can get to safe mode you can try disabling the startup of the Jail Break tool. If that doesn't work than I doubt the jail break was even related to the problem you are experiencing. (it is already highly unlikely that this is the case.)
Good luck.
Click to expand...
Click to collapse
It's not even getting to the point where the jailbreak would run.

netham45 said:
It's not even getting to the point where the jailbreak would run.
Click to expand...
Click to collapse
Believe me I know where it is getting to. However if there is a remote possibility that the jailbreak affected the startup processes of the OS, then removing the jailbreak could revert those changes, however unlikely it is still worth attempting.
As I said the possibility is unlikely. Which is why a system restore and OS refresh are most likely the only options.

Zephnath said:
Believe me I know where it is getting to. However if there is a remote possibility that the jailbreak affected the startup processes of the OS, then removing the jailbreak could revert those changes, however unlikely it is still worth attempting.
As I said the possibility is unlikely. Which is why a system restore and OS refresh are most likely the only options.
Click to expand...
Click to collapse
That doesn't even make sense. It doesn't boot into Windows, let alone to the point where the user can log in and the task scheduler can be initialized, so there's no way it's also booting for the two minutes it takes for the jailbreak to launch.

I received a Vivotab tf600t. When I turn it on, it goes to Preparing Automatic Repair and then goes to Diagnosing Your PC. It never gets out of this loop--Prepaing then Diagnosing. Is this due to jailbreak gone wrong? Any chance to factory reset it? TIA.

9394888 said:
I received a Vivotab tf600t. When I turn it on, it goes to Preparing Automatic Repair and then goes to Diagnosing Your PC. It never gets out of this loop--Prepaing then Diagnosing. Is this due to jailbreak gone wrong? Any chance to factory reset it? TIA.
Click to expand...
Click to collapse
What was done before it went into this infinate loop? Chances are the Jailbreak didn't do it.
There is a way to factory reset the tablet. You will need the Bitlocker key, if you don't have it you can recover it from your skydrive. Use this url to go to the recovery keys attached to your skydrive account: http://skydrive.com/RecoveryKey (you will have to logon with the primary microsoft account for your tablet)
You should be able to get into the advanced recovery options for the tablet, some of which will allow you to reset the tablet (which wipes the tablet of everything, thus restoring it to factory defaults), or to refresh the tablet (which uninstalls programs but maintains files and documents)

Zephnath said:
There is a way to factory reset the tablet. You will need the Bitlocker key, if you don't have it you can recover it from your skydrive. Use this url to go to the recovery keys attached to your skydrive account: http://skydrive.com/RecoveryKey (you will have to logon with the primary microsoft account for your tablet)
You should be able to get into the advanced recovery options for the tablet, some of which will allow you to reset the tablet (which wipes the tablet of everything, thus restoring it to factory defaults), or to refresh the tablet (which uninstalls programs but maintains files and documents)
Click to expand...
Click to collapse
Excellent piece of information.

Soft bricked RT during complete restore.

Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?

The CD key ought to come from flash ROM, but it depends on how the recovery image works, which I don't know >.<
If you can use his recovery image to boot to command prompt, you can mount your SSD's registry hive and dump the product key data, then decode it on a Windows PC. Then after recovering with the image, even if the product key ended up copying your colleague's Surface's key, you could just go to System and click "Change product key" and type your own key. (In this situation, the desktop will likely be black, a sign that Windows was unable to activate. Changing the key to yours will fix that, of course.)
I'm not saying that this is easy or anything, but this ought to work, with my understanding of Windows NT.
Note that you don't need to bother decoding the registry data if you notice after recovering that your product ID in System is different than your colleague's, and it also says that Windows is activated. This would mean that the recovery image grabbed your CD key out of flash ROM.
EDIT: I guess what I meant to say is that when you boot to command prompt, run regedit. In regedit, go to HKEY_LOCAL_MACHINE then File/Load Hive. Find your system hive on your SSD, which may be on a different drive letter than usual, in somewhere like Z:\Windows\System32\config\SYSTEM. Give it some name like "meow". Find the subkey meow\SOFTWARE\Microsoft\Windows NT\CurrentVersion. Go to File/Export and export that to a .reg file on your USB stick. If there is an option to do so non-recursively (I forget, and I'm on my iPad), use it because that key is big. Once you've backed it up, you're safe to recover, because now you have everything needed to find out your old key if required.
If in fact you do need to use that .reg file to determine your old key, let me know so I can help you out. Some tricks will be required to proceed.
Melissa

munsterrr said:
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
Click to expand...
Click to collapse
If you recover using an 8.1 recovery image form somebody else it won't mess with the keys. Worst case is that you may have to activate and you do not have a key. If you look at this post by Osprey you will see how to get the key from a 8.0 installation. That won't help you of course unless you have access to the registry and hive as Melissa suggested.
I actually recommend you use an 8.0 image to recover your RT and then upgrade. The only thing you have to do is get the image and "burn" it to a thumb drive. There are no steps required to obtain your key. Make a bootable thumb drive with an image you can download from here and start from scratch. Your system will automatically activate going this route. I've done this several times to switch between Preview 8.1 and 8.0. Follow the instructions above from Osprey's post to obtain your key just in case you do need it sometime in the future. Then you upgrade to 8.1 (nothing necessary in terms of activating this way).
Here is a post with a link on how to recover with a USB recovery image. One important point when you put the image onto the thumb drive is that it has to be bootable. Use UltraIso or Rufus to put the image onto the thumb drive (FAT32 formatted).

munsterrr said:
Any ideas/direction/thoughts AT ALL are greatly appreciated.
Click to expand...
Click to collapse
Apparently this is a widespread problem, and one of the reasons I haven't upgraded to 8.1. Heres the solution: http://kickthatcomputer.wordpress.com/2013/10/19/windows-rt-8-1-upgrade-fails-with-boot-configuration-error/

Thanks for the replies everyone. My colleague was able to upgrade to 8.1 on his RT with no problems. We were able to copy the image(minus recovery partition) over to a thumb drive and I was able to boot from that and eventually upgrade myself.

cant wipe windows surface bit locker issues

Hello,
I am trying to factory reset my windows surface and running into some issues. The tablet was given to an ex employee and he set everything up. Now he has been dismissed and he wont provide login info nor big locker information.
I have went over the steps for a hard reset and tried them. But after all my efforts I am always promoted to enter bit locker number.
So is there any way around this? Can I wipe the system another way or boot software to over ride this issue?
Will gladly provide paypal funds to anyone that can help me resolve this problem. I have a new employee starting this week so this tablet is needed asap.
Thanks much.
updated
so far what i tried is
I downloaded the files needed for disk image
followed these steps
rt 8.1 boot steps- download files extract format usb- boot up
when i get to the hold the power button and volume down button the screen just turns off line below the middle for a second and off.
Wont load or boot?

Don't know simpler method, but you can always boot from recovery pendrive into command prompt and remove/recreate system (and perhaps boot too?) partition using diskpart
http://technet.microsoft.com/en-us/library/hh825686.aspx
This can be used on clean (wiped from partitions) drive - that's how I restored my XPS10, so it may be helpful here too, just remove partitions first.

How to find original build version when soft bricked?

Ok, I have searched the internet and these forums for hours and have not seen an answer to this anywhere.
I can't believe I'm the only person who has ever wanted to know how to determine this information!
I repair Nexus 7 2013 as a hobby - usually with broken screens, but now and then buy a soft bricked one.
I have the same issue every time - trying to find what is the original build number when it is soft bricked and you can't access Recovery either. I have even tried to see if Asus has a cross reference of serial number to original build number - no they don't.
I use the Wug tool and so far the score is 3 saved, one that even has Wug stumped, and the one I'm working on tonight that I simply can't get to work.
I always have to guess and try versions. tonight I've tried the single version of 4.4.4 and 3 other version of 5 to 6. Each time the best that I can get is a sluggish boot that usually eventually freezes while trying to run setup. That is BEST CASE. Worst case would take pages to describe. It sort of works on lmy47v a little and not at all on any other build. Manufacture date is March 2015.
If I didn't know better, if this was a PC, I would say there is a bad RAM chip.
Regardless, I would feel a lot happier if I knew I was installing the right build which leads back to the original question - how do you find the original build if it's soft bricked?
Thanks to anybody who can answer this!

Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?

k23m said:
Do this:
PC: download TWRP image, e.g. twrp-2.8.6.0-flo.img
N7: boot in fastboot mode
PC run: fastboot boot twrp-2.8.6.0-flo.img
N7: in TWRP UI mount system
PC run: adb shell cat /system/build.prop > build.prop.txt
View build.prop.txt on PC:
Code:
ro.build.id=LMY48Y
ro.build.display.id=cm_flo-userdebug 5.1.1 LMY48Y ceb9c142ee test-keys
ro.build.version.incremental=ceb9c142ee
But why do you bother to restore "original build number"?
Most of them are locked and will lose all data in the process of unlocking.
Then why not flash the latest OS image?
Click to expand...
Click to collapse
Thanks for your reply. No less complicated way to find that out eh? I'm afraid that's a bit over my head (or perhaps its just the way its worded - no offense intended). If it was PC, and particularly DOS, I would be laughing.
When nothing else was working on this particular tablet, I did try for the heck of it to use the Wug toolkit to root and install TWRP, and it would just lock up and never install - no error messages or anything.
As far as why not use the most recent image, there are lots of opinions, and the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device. Since you have to take every opinion with a grain of salt, it just seems to make sense to use what it came with. 2 out of 3 tablets I have been able to do that with I have be able to save. Only 1 where I used a random build worked.

consumer61 said:
No less complicated way to find that out eh?
Click to expand...
Click to collapse
The simplest way is to check it in stock recovery but you say it is not an option...
consumer61 said:
the majority I have ever read says if you don't use the original build you will get all kinds of problems right up to completely bricking the device
Click to expand...
Click to collapse
Please post a link to one of them.

k23m said:
Please post a link to one of them.
Click to expand...
Click to collapse
I wish I could. Just random things read from hundreds of pages over a couple of years, and of course when you look for them you can't find them. I have on and off been trying to find an answer to this question for over a year.
Even the wug toolkit encourages you to make a backup of your own system rather than re-flash a random stock image. Since as soon as you unlock you lose everything anyway, there hardly seems any purpose to a backup as opposed to just re-flashing with the newest version - ergo that also leads you to believe you need to use the exact version that was there before.
I don't discount the possibility that even though not said, what was actually meant was that each device model has a version specific to it. Again, that was never clearly said, I am just using logic based on your concept that you can install any image at all, with absolutely no issue.

consumer61 said:
I wish I could... when you look for them you can't find them.
...rather than re-flash a random stock image.
Click to expand...
Click to collapse
That's it, all those horror stories are from "random stock" flashers. If you choose wisely the very latest stock image then there is no danger whatsoever.
Let's talk about the latest case - is it unlocked already?

I was able to unlock, but could not access recovery - when booting to recovery it would still just sit at the Google logo.
In order, I tried from the list that comes up on the Wug tool, a 6.01 version, then lmy47v, then lmy48g, then finally thought I would try going back quite far since there was only one version for 4.4.4 - ktu84p, then finally lmy48t.
With tiny variations, all had the exact same result - no errors when wiping or reloading. The circling balls would just around as normal, then eventually grind to halt - moving a tiny bit every 5-30 seconds. After maybe an hour, sometimes you would finally get the normal "pick your language" screen, although most times, after about 30 min I would just shut it down and power it back on.
That would result in sometimes getting the "pick a language". Sometimes able to get as far as entering a gmail address, but the system would always lag - registering a touch many seconds after doing it. Once single time, I got a full boot up. Then it came up with the OTA as it should. ran it, and back to soft bricked.
Also a couple of the times I was able to get it to boot, as soon as you would reboot, it would be back to soft bricked.
Motherboard got exceptionally hot, and battery was down to 18% once, and 27% another time from full charge - so it was working abnormally hard
I have been playing with and building pc' etc since the Vic 20, C 64 and so on, and it behaves just like a bad RAM chip. I did find a post on here saying the Kingston/Toshiba chip can get corrupted and must be replaced, with a link to the same guy selling MB on ebay - can't remember his id on here, but here is the ebay sale:
http://www.ebay.ca/itm/121637666631?_trksid=p2055119.m1438.l2649&ssPageName=STRK:MEBIDX:IT
Overall this is similar behaviour although not quite as bad, as the other motherboard that stumped Wug. He finally said it must be hardware in that case, and I certainly tend to think the same thing here.

consumer61 said:
He finally said it must be hardware in that case, and I certainly tend to think the same thing here.
Click to expand...
Click to collapse
Let's find out exactly. As you are comfortable with DOS then the following should be piece of cake:
download twrp-2.8.6.0-flo.img from https://dl.twrp.me/flo/
go to Wug(NRT)\data folder - can you see fastboot.exe and adb.exe there?
boot the Nexus in fastboot mode (when off press power+vol.down), connect it to your PC
in Wug's data folder open a DOS command window and copy/paste: fastboot boot twrp-2.8.6.0-flo.img [Enter]
when TWRP is up and running, copy/paste in the DOS: adb shell dmesg > dmesg.txt [Enter]
you will find dmesg.txt in Wug's data folder
zip up the file and attach it to your next post
This is THE hardware log and another chance to play with DOS-like stuff :laugh:

Ok excellent instructions. (did tech support for years).
I had pulled the MB and replaced it, so I just switched it back.
Install TWRP worked fine. TWRP screen came up.
Typed command for the msg file, and dos error was "error: device '<null>' not found
I know of TWRP, but have never used it. I hit the centre button on the screen which brought up what appears may be an install log, and its full of errors.
Goes down over a full screen, but the common statement is:
"unable to find partition size for /boot" /recovery /misc and about 15 more lines.
Also other errors like unable to mount cache, data, system
I just took a photo of the screen but it seems you can't post actual images, only links to images stored on the internet, not something off your hard drive.
Just to let you know, I did try various spacing around the dmesg > dmesg.txt command just to be sure, same error every time.
Now that is from the TWRP screen with all the buttons on it. If you meant for me to open a certain function of TWRP, I didn't.
Regards,
UPDATE: had a brainwave and loaded up Wugfresh and device manger. Showed exclamation mark beside the device so re-installed adb driver. Now the log worked. It is only 64k, and both the twrp photo and the log file should be attached now.

I looked through the log, and even not knowing the internals of the system that well, only one part stood out as appearing bad:
<3>[ 0.277130] msm_gpiomux_install: write failure: -22
<3>[ 0.277221] msm_gpiomux_install: write failure: -22
<3>[ 0.277404] msm_gpiomux_install: write failure: -22
<3>[ 0.277496] msm_gpiomux_install: write failure: -22
<3>[ 0.277648] msm_gpiomux_install: write failure: -22
<3>[ 0.277740] msm_gpiomux_install: write failure: -22
<6>[ 0.278656] Registering gpio keys
<6>[ 0.278778] Reconfigure VOL_UP(GPIO155) and VOL_DOWN(GPIO189) with PMIC
<4>[ 0.278991] 8921_l17: Failed to create debugfs directory
<4>[ 0.280609] ------------[ cut here ]------------
<4>[ 0.280700] WARNING: at arch/arm/mach-msm/subsystem_restart.c:573 subsys_restart_init+0xd8/0x104()
<4>[ 0.280883] Modules linked in:
<4>[ 0.281066] [<c0015f44>] (unwind_backtrace+0x0/0x11c) from [<c007ae88>] (warn_slowpath_common+0x4c/0x64)
<4>[ 0.281250] [<c007ae88>] (warn_slowpath_common+0x4c/0x64) from [<c007aeb8>] (warn_slowpath_null+0x18/0x1c)
<4>[ 0.281433] [<c007aeb8>] (warn_slowpath_null+0x18/0x1c) from [<c0c0c600>] (subsys_restart_init+0xd8/0x104)
<4>[ 0.281616] [<c0c0c600>] (subsys_restart_init+0xd8/0x104) from [<c0008718>] (do_one_initcall+0x8c/0x15c)
<4>[ 0.281799] [<c0008718>] (do_one_initcall+0x8c/0x15c) from [<c0c00a24>] (kernel_init+0xe8/0x1a4)
<4>[ 0.281982] [<c0c00a24>] (kernel_init+0xe8/0x1a4) from [<c000fdf8>] (kernel_thread_exit+0x0/0x8)
<4>[ 0.282104] ---[ end trace ff63e6c2cba9c001 ]---

consumer61 said:
Typed command for the msg file, and dos error was "error: device '<null>' not found
Click to expand...
Click to collapse
When TWRP is running please type adb devices and it should respond like:
Code:
List of devices attached
087777e8 recovery
If not, re-plug USB cable, check Windows device manager for new hardware. You may need ADB driver but Wug would install it before.
Please upload the picture(s) to http://imgur.com/?noFlash
We don't need to interact with TWRP for this task at all.
Btw, TWRP was not flashed, but only temporarily booted so you may need to repeat it all over again.
Cheers

I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!

consumer61 said:
I suspect you were writing your reply above, as I updated the info. Please see the end of page 1 - the photo and the log file are attached.
simply put is was my mess up - adb had to be re-installed every time you plug a device in when running XP Pro. (Yes I know XP. Hate 7 and 8 and 10, but this is the last version where you had SOME semblance of control over your own computer lol)
Thanks!
Click to expand...
Click to collapse
Yes.
I use Linux and ...XP too :highfive:
Please check my last post here.

Sprint note 4 n910p (boot failure) recovery image from working note

I have created boot recovery files based on Samsung's pdf titled "[14-96]_Boot_Recovery_Guide_Qualcomm_APQ8084_[includes_SM-N910F]__Rev_3.0"
These were done on a 32gb clas 10 microSD, they are imaged to a file via Norton Ghost portable (GHO file.
If your note doesn't boot, that might help. (No charging light, PC detects as QHUSB 9008 mode etc)
Download these GHO files and norton ghost portable.
Insert an empty microSD, Open norton ghost > Local>Image>to Disk the choose your microSD.
Your disk capacity might show up less, but don't worry, you can restore later on with Minitools (Check online on how to use).
I have also created an eMMC backup image of n910p running MM (PE2 build version)
It's a 2gb file, on unzipping with 7zip, around 4gb. (While creating, the output from adb shell is shown in the pick. Not sure if it's an error... is it supposed to be bigger? it was on a clean stock but rooted.. no user content)
Follow this guide http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ to check it's in new 9008 mode.
Then my file might work for you.
All files are at https://mega.nz/#F!qRAGBZDY!_k24QWYaA0We2IQoAgE2Ng

Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks

dray_xclusive said:
Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks
Click to expand...
Click to collapse
And my phone its same
I hope to find way to solve it

i have also same issue does any one solve ?

an interesting read... curious, under what circumstances would this be more convenient / more practical than a simple odin flash?
is this supposed to recover hard bricks / bad bootloaders?

Took N910P back to Sprint.
I experienced my problem when I was using my secondary (not activated, clean esn) Sprint N910P as an MP3/MP4 player. After the last update which i don't know... it would not boot into the OS after the Sprint splash screen, so it would continue to do this constantly after removing the battery and rebooting even after optimizing apps screen. I researched and found XDAs forums with a lot of How tos, troubleshooting and workarounds. Long story short the Reactivation Lock was not disabled and even using the techniques supplied here I did not have any success.
I took it to the Sprint store and they deactivated my Primary LGV20 and activated the Note 4 so they could service it and then flash it to the current OS. They couldn't flash it and were going to have to send if off to replace the motherboard or replace the phone. The tech told me that this has been happening to Sprint Note 4 phones after an update and since it was a update error there will be not charge to me. Now I had insurance on the Note 4 for six years prior to upgrading to the LGV20, so they had to activate it to be able to service it. I will update their findings when i receive my phone in 7 to 10 days.
I pray this helps someone in my situation, as for me it is bittersweet. I didn't fix my phone but I found a new forum and I can tell everyone here is as passionate about what they do as I am!
- Jacob