Related
Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.
So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.
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.
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.
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.