Hi hope all is well.
Current Issue:
*when powered on tablet (surface rt 32 mb) displays surface logo in a continuous boot loop.
*when attempting to boot to uefi mode the tablet displays a black screen( shuts down) and will not restart unless a 15 to 30 sec. hardboot is performed.
*when booted from a ver. 2.0 USB with Microsoft surface rt image Surface2_BMR_102.1.9.0 and using parameters reset pc and fully clean, it stops installing @ 1% with a generic message ( ran into a problem and cannot continue).
*When attempting to boot from the refresh your pc option: the operation fails with error message ( The drive containing windows is locked).
*Whe attempting startup repair, the operation fails with message (ran into problem cannot continue).
COMMAND PROMPT REPAIR ATTEMPTS:
DISKPART:
*list disk shows 29gb/29gb free/gpt
Detail disk shows disk information and also shows there is no volume for disk
*clean disk operation succeeds
*create partition primary operation fails with message virtual disk service/the object is not found
*format fs=fat32 fails with msg virtual disk service/the object is not found.
So far the best positive is that disk detail does show the ssd drive information so I know that it can be seen.
ORIGINAL HISTORY:
*Tablet had low battery and died during software update.
*Tablet was secured with bitlocker key but key was lost and has since been found albeit to late for what trouble shooting steps subsequently followed while it was misplaced.
*As remedy to not having the bitlocker key a full clean and reset was performed via the USB stick recovery software for the tablet.
*Upon reinstalling the operating system the errors contained in this message manifested themselves.
From what I can tell,it seems that diskpart cannot see the ssd for anything beyond knowing that it's there and that may be one of the reasons that the installation media has nothing to install to. 🤔
NOTE: I am not able to boot into uefi mode using vol. up and power button, whenever I do this the tablet will die to black screen and I have to press the power button for 30 sec. to get the tablet to start again. I have attached some images to give the community a better idea of my issue.
I am taking a pretty good whipping on this one but I don't mind because it's all about learning except now I am not sure of what questions to ask myself and it's really difficult to learn that way, that's when I know that I need help, so someone ,anyone, everyone lol please chime in if you will.
Also having this issue with my Surface 2. First its touch screen mysteriously stopped working, and then it started having random issues that I can't entirely recall, but one of last ones was being unable to open the settings app. Ended up doing a full reset with repartitioning, and now I get exactly these symptoms with these exact steps to attempt to troubleshoot. I wonder if this is a firmware thing, or a common disk issue - as the symptoms from before could very likely be pointing to disk issues too.
Yes I know this is a couple years old, but I decided to check to see if there's been any progress on knowing why or what the issue is with this, as I still have this Surface 2 lying around. If it can't be used for anything else (since I don't think it can boot anything other than its own recovery software due to secure boot stuff?), then I suppose it could be something for me to experiment with opening up devices that aren't very user-friendly-replaceable.
Related
So, right away today I decided I would format my TF-101 and start fresh to try and fix a weird sound issue that I had. In a lapse of judgement, I installed (which I now know I should not have done) CWM and now I'm in a bootloop...Which would seem easy enough to fix, but I have an even stranger issue...
When I try to push files to my device, anything over a few MB will fail. The things I have been able to push haven't helped me...
When I go to APX mode, the device shuts down whenever I enter a command or run a program that tries to interact with it. So, for instance, I put it in APX mode, tried to run EasyFlasher and it turns off. I know its off because I hear the device removal notice, and the devices drops from my device manager...Try to run Rootkit 8, it turns off...
I don't know what else I can do...Unless I have the wrong driver installed, I seem to be stuck. I can not enter any other modes besides the CWM screen v.5.8.3.4 btw, and the Power+Vol Down mode. If I choose cold-boot linux, my laptops call it "Android MTP Device" but by tablet never boots or leaves that screen...
I'm pretty stumped, waving my flag at this point...
Any help is appreciated..!
AYHJA said:
So, right away today I decided I would format my TF-101 and start fresh to try and fix a weird sound issue that I had. In a lapse of judgement, I installed (which I now know I should not have done) CWM and now I'm in a bootloop...Which would seem easy enough to fix, but I have an even stranger issue...
When I try to push files to my device, anything over a few MB will fail. The things I have been able to push haven't helped me...
When I go to APX mode, the device shuts down whenever I enter a command or run a program that tries to interact with it. So, for instance, I put it in APX mode, tried to run EasyFlasher and it turns off. I know its off because I hear the device removal notice, and the devices drops from my device manager...Try to run Rootkit 8, it turns off...
I don't know what else I can do...Unless I have the wrong driver installed, I seem to be stuck. I can not enter any other modes besides the CWM screen v.5.8.3.4 btw, and the Power+Vol Down mode. If I choose cold-boot linux, my laptops call it "Android MTP Device" but by tablet never boots or leaves that screen...
I'm pretty stumped, waving my flag at this point...
Any help is appreciated..!
Click to expand...
Click to collapse
** Edit **
I knew that I would figure this out the minute I posted it...I'm still having issues, but PERI-V0.4 broke the ice and at least allowed me to get some type of on CWM boot thing going...I'll post details for the next troubled soul with a similar issue, though I am still curious about why it kept disengaging...
Hi, so yesterday after powering my Surface 2 down (it was working fine), it no longer boots up. Instead, it will show the 'Surface' on the screen for about a second, and then the screen will go black for 8 seconds, and repeat until I turn it off or the battery dies.
I've been having a hard time finding other people with this problem, but the few I did said that sending it to MS (and getting a new one) is what they had to do. One person did say that they were able to fix the problem with a bootable Surface 2 recovery USB. I have a lot of work on my surface that I don't have copies of, and would really like to be able to save those files.
Things I have tried: Holding the power button with a combination of volume rocker/home key. Holding the power button for 20 seconds followed by 2 seconds off and on. I have fully charged it and know it has enough battery.
Help would be greatly appreciated.
Hi John,
What was the solution to fi this problem?
I encounter the same problem.
Regards,
Hans
You should be saving your stuff to your OneDrive...anywho
If you have a USB recovery drive, you could try booting from it and doing a refresh,(NOT a reset) that would keep your files.
If you don't have a USB recovery drive you could make one using the 8.1 RTM ISO, I wrote a how-to guide here;
http://forums.wpcentral.com/microso...w-install-windows-rt-8-1-rtm-surface-2-a.html
or you could download one here;
https://onedrive.live.com/?cid=203A62CBEDC78BA2&id=203A62CBEDC78BA2!6247&authkey=!AIcBVsLygTfpZxQ
(I think that one is for the UK, but that shouldn't matter, just do a full reset from your recovery once you get your files off)
Hope this helps.
A co worker had her surface rt crash on updating and now its stuck at the booting surface screen.
I tried the steps I could find fiddling with the volume button and power button but it gets no where.
Honestly I have zero experience with these and normally use android.
Is there a way to connect this thing to a PC and push recovery files to it as it doesnt seem to want to see the recovery USB at all. It does know its there cause the power/reading light on the USB drive lights up.
Im trying another attempt at downloading and remaking the recovery USB just to see if I got a bad download but honestly wondering if this thing is toast. Just really trying to help them out cause it just ran out of warranty and MS wants to charge them 200$ to repair it.
Thanks
Hello there,
I would like to propose again this question, I summarize the problem of a Surface,
in my case a Surface 2 with Windows 8.1 RT stuck at the 'Surface Screen' and looping
in reboots alternating with the screen of 'preparing automatic repair', and then stuck.
If I reboot by holding down power button for 10 or 30 seconds, nothing changes and
the loop restarts by telling 'there is a problem screen', automatic reboot, 'Surface screen' and stuck.
I've tryed with 2 versions of the recovery image, an old one and one new, with two different
usb sticks. I've booted with "volume down" etc, the usb light flashes a couple of times but
the loop described above does not change.
Seems that many people out there suffer from the same problem, with almost all versions of the Surface, up to the Pro 4.
Many of them solved it with the usb recovery, but also a lot of them still have the same problem. Maybe we do something wrong
with the recovery files?
Any help is welcome, thanks for reading.
Try to keep the device on charge and leave it running for some hours, does it still stay stuck?
Hello Kephax,
I tried several times many strategies, even the one you suggested, nothing to do, always the same loop.
Hence I contacted Microsoft on 15th december, the support was very polite and efficient, in a week I was able to pack my device and give the pack to UPS. After 3 days, they returned me a new Surface2 for free.
I must say mine was only 6 months old, so warranty was still valid. On 24th december I was playing with the new device, so the whole procedure took 9 days. I am very happy.
However, I cannot say what was the fault of my Surface, a hardware problem or some updated went wrong? that's the question, I'm frightened that it was an update problem and that it can happen again to the new device. I can only guess it was a hardware problem because of the experience with the new device, less laggy, more fluid for graphics animations. Also the battery lasts longer.
I hope that this experience can help other user with same problem.
Best wishes for a happy new year,
dott_mat
Create a surface rt 8.1 bootable usb and boot from usb device.
If USB Device bootable, then first connect usb device, then press and hold vol down button, then press and release power button, when surface logo appears then release vol down button.
If all successful then surface will boot into recovery or directly boot from usb drive.
Hi guys looking for some advice for some problems I am experiencing with my Tesco Hudl 2. I was directed here by a friend of my mothers, so I am new here. I have searched and searched for a possible solution and haven't had any luck however I sincerely apologise if this question has already been asked.
So onto my problem I have a roughly 2 year old Hudl, other than the current problem it is in good condition, never been out the case or dropped and I haven't rooted it. This is the first problem I have had. A few months ago a friend was using it and despite me telling her not to, she played some Facebook games on it. After that it started coming up with crash reports and error messages and within a few hours was switching itself off. I had a quick search for some help at the time but as I have very little experience with android devices and couldn't find any kind of help I switched it off and left it at that. I realise now being switched off for that few months may not have helped.
Yesterday I tried switching it on to see if I could get it working, on switching it on with a full charge, it goes as far as the powered by android logo, sits for a minute, switches off and then tries again. I have attempted to perform a reset using the power button only, this done nothing.
I also attempted to bring up the Android system recovery menu using the power and volume up buttons. This brought up and error message stating that the 'efi hard drive boot failed', the next error message was 'no bootable device, hit any key' '[ok]', from here I can do nothing. The touch screen and the volume buttons are unresponsive.
Holding the power button eventually powers off the device.
I know this means that my boot partition is corrupted as I have previously performed boot partition fixes on a pc when a Linux clean install went haywire but I have very limited Android experience. The advice I received was that I have to factory reset the device and install a new copy of my boot partition, using abd on my laptop and to come here to XDA-developers forum for help with the process. I am using a windows 7 laptop currently. To be honest I don't know where to start and any advice would be hugely appreciated! Thanks in advance and sorry about length!
Back story:
My beloved tablet ran down on power as I was using it today (note to self - change warning percentage from 5% to something like 15%)! I tried shutting it down, but it died before the shutdown was finished. I put it on the charger and let it charge until about 65%, took it off the charger, powered it up. It started coming up, got to the the PIN screen, then nothing. Couldn't do anything, touch screen wasn't doing acknowledging anything. I think things got corrupted as it was powering off...
Powered it down, waited a few minutes, then powered back up. Took about 10 minutes to start after I entered my PIN, and it was behaving strangely:
1. WiFi said it was off, but I was getting e-mails (sent one to myself from another device to confirm it)
2. Settings would start, but got nothing, just a white screen.
3. Most apps would start but really slow, then suddenly shut down
4. Tried booting into TWRP 3.1.1 - got the initial screen, there it sat for the next 20 minutes before I rebooted.
5. I can get into bootloader, but fastboot from my Linux laptop doesn't work - can't find any devices when the tablet is plugged in.
6. "adb devices -l " shows the tablet is connected, but get no prompt on the tablet screen about adb starting
6. "adb reboot bootloader" and "adb reboot recovery" from my laptop just sits there - nothing happens on the tablet.
I'm on Lineage OS 14.1 (latest weekly for the SMP-900) and TWRP 3.1.1 on the tablet, and Fedora 25 on the laptop. Rebooting is iffy - sometimes it starts, sometimes it doesn't and just sits on the Lineage boot animation. I also have my 128Gb SD card set up as part of the internal memory (i.e., can't pull it and stick it into another device) Every reboot takes longer, and I fear the next power on will have me just sitting there, staring at the Lineage boot screen forever.
I have Nandroids from TWRP, but doesn't do me much good if I can't get into TWRP to use them. I have TWRP image and tar files, but jodin (a Java based Odin type of program that works in Linux) doesn't get a response from the tablet and therefore won't flash.
If I could get the tablet back to the point where I can get TWRP working again, I can reload from the TWRP backup. I also don't have a Windows computer available at all, but I do have Windows XP in a VMware virtual machine as an absolute last resort on my laptop.
Does anyone have any ideas or pointers to get me running again? Right now, it's powered off and charging...
Thanks for any help....
Patience, patience, patience ...
I'm answering this myself - just so there is an answer.
If you ever run into this problem, read the heading above! I got the tablet to boot up finally by pulling the 128 Gb SD card first, then powering up the tablet. I plugged in the SD card back in and it started slowing down, but checking under Storage, it indicated it was checking the encrypted card. I set it aside, checked it 2 hours later - still checking the card. Plugged it into the charger and went to bed, got up this morning and it was shut off. Powered it up, it booted up, this time around it recognized the encrypted card as part of internal storage and Life is good again.
My assumption is that when the tablet died, the card was marked dirty (I.e., not shut down properly.) When I tried TWRP, it noticed that the card was flagged dirty and started checking it before it would give me the home screen - same thing with Lineage when it tried to boot. And yes, I changed the battery power warning to 15%.
Thanks for your update on that problem.