This happened just a little bit ago, but when I woke up this morning my phone was on a screen that said "Your device is corrupt. It can't be trusted and may not work properly." Then it gave me a link which just lead to the google help page for android, as well as a message at the bottom saying "to continue press the power button", though pressing the power button did nothing. After looking things up I loaded the bootloader and tried to activate recovery mode, but trying to do that just lead back to the screen. And I couldn't boot in safe mode since I can't even get to the loading animation. Is there anything I can do short of sending it to the manufacturer to flash the phone?
To my knowledge I've not downloaded any files recently beyond a few pictures, but those are all from trusted sources, and I've never tampered with the software, so I have no ****ing idea what could be causing the corruption.
Did you unlock the bootloader? If you did, you can flash the last official Google image for the device from their pages and restore your device to working order. Keep in mind however that anything on the phone will likely be lost if you didn't back it up, especially if you had set a pin or password for the device.
Related
A bit after using setcpu, My phone wouldn't respond when I tried to wake it up.
I had it set to ~700 powersaver when screen off and ~800 conservative in normal, but 1.5ghz when plugged in. It was plugged in and when I woke it, the screen wouldn't respond. I got to the homescreen by flipping open the keyboard (to unlock, I have no pattern). I think everything was working except for the touchscreen and soft keys.
Eventually, I pulled the battery, and now it won't boot.
when I turn it on it takes me to the screen with the androids on skateboards and when I push power for the first option it says
"SD Checking...
Loading...[PC10DIAG.zip]"
it takes a long time for it to get the message "No Image!"
then it looks for the .nbh, (not found) and starts looking for more files, none found
any fix? or am I screwed?
I brought it second hand, so no warranties...
BUMP
Help please?
Should I find and download the PC10DIAG.zip and put it on my sdcard?
I kinda need it fixed asap.
Ok, well I saw that I shouldn't flash the PC10DIAG.zip since I'm S-Off, So i tried to flash recovery through fastboot, still couldn't get into recovery, even though it seemed to flash successfully, and no matter how many times I rebooted it or how.
eventually I tried "Fastboot reboot" and the thing started up normally, wtf?
problem solved, but I'd kinda like to know what was wrong just because.
otherwise this thread can be closed
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.
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
When I first got this phone, I was having a hard time getting an RUU to image the phone and I loaded a zipped image from one of the threads that automatically loaded when the phone was rebooted. That worked fine even though I figured out my RUU issue later on.
Anyway, when I go into download mode, I get the following warning and I have no idea how to remove it, any ideas???
"Security Warning
If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing your personal and financial information to unknown sources.
FILE /mnt/media_rw/ext_sd/2PS6IMG.zip
File NOT FOUND"
I still get this message even after flashing a bunch of different images and even doing a factory reset and other wipes. Any help would be greatly appreciated. I searched high and low for an answer, but couldn't find one.
That is just the standard message you get when you unlock your bootloader. Its nothing to worry about. There are a couple of ways to get rid of it -- using a hex editor, and so on, but why bother? You could end up damaging your phone in the process. I've become rather fond of that red text. Looks pretty cool.
what about that file not found crap? why the hell is it looking for something.
It automatically looks for that file as an OTA update. If the file is found it is executed. If not, you get the file not found msg. Again, this is totally normal. Its all good.
Hello fellow android lovers!
I need help with said Smartphone from everyone with a knowledge bigger than mine.
Ill start from the beggining:
Friend of mine had this phone for a really long time. The condition of said device is nearly new (Few minor scratches here and there).
He decided not so long ago, to change his phone to newer one, so that one went to the drawer where it was for like a year or so.
He came to me a week ago with this phone, because he wanted to give it to his child as a first smartphone.
On that HTC device, after booting the system, there is a notification "Decrypt Storage" where you need to enter password to decrypt ROM memory. He said he never used any password on his device and even on new smartphone, he did not put any lock kode or pattern.
After entering any password, even with one letter, the notification says: "The password is correct, but unfortunately your data is corrupt" then there is a "reset phone" whitch restores smartphone to factory state.
Sadly, this doesnt work. It shows the same notification after factory reset. More like a bootloop but with a note.
I tried to hard reset it, but after i choose in bootloader "Factory reset", it takes me to main menu of bootloader and it says "Failed"
I also tried to get to the phone via USB. I installed htc usb drivers, got the binares to unlock bootloader and the fastboot option works, adb isn't.
I tried to use Fastboot factory resset command, tried also flashing TWRP recovery and nothing.
The wierd thing is, that the bootloader unlock binaries is not working as i see on the device because after "Unlocking" Bootloader, i go to the Bootloader menu and it allways says:
*****LOCKED*****
*****SOFTWARE STATUS: MODIFIED*****
*****SECURITY WARNING*****
Click to expand...
Click to collapse
The wierd thing is, that software status was modified even when he gave me this phone to work with. He is not the type of android poweruser. I doubt that he will modify his software.
Can somone help me with some tips how to flash a new system or get this device to work? I am banging my head on the wall right now. I am out of options.