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.
Related
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.
I was picking up my surface rt last time for some bedtime surfing when ***WTF***!!! there was a prompt saying we've just applied rt 8.1 upgrade do you want to restart in 1/2/3...hrs?? really sleepy, i hit 5 and thought i'm going to handle this tomorrow.
next morning my tablet has already rebooted itself. darn it.
so starts my quest to downgrade. it is remarkable how scarce the resources are on the internet. all hail microsoft.
here's how i did it in case anyone is in the same predicament as i am. or until 8.1 jb comes out.
you will need:
1. usb drive with 4gb or more.
2. the rt 8 recovery image. get it from:
http://www.microsoft.com/surface/en...-recovery/surface-rt-startup-error-0xc000000d
The second one took a bit of hunting. All posts on the net seems to point to a page that has already moved on microsoft support. Okay enough *****ing. Follow these instructions carefully.
1. Backup your usb drive and format to **FAT32**.
2. **EXTRACT** the zip file you downloaded to the root of your usb drive. I had a hard time figuring out because nowhere on the microsoft support page did I see any mentioning that the zip file needs to be extracted.
3. attach the usb to your surface. Power down, hold the volume down (-) rocker while press and release the power button. Release the volume rocker when you see the surface logo.
4. choose language and keyboard.
5. ***DO NOT*** key in your recovery key. From the bitlocker screen, tap "skip this drive".
6. Troubleshoot > Reset your PC.
7. Choose ***Windows 8.1***. Yeah I know...
8. The next screen asks you whether to keep the existing partitions. I chose to reset all the partitions because I want a nice factory image. I reckon either choices are fine.
9. Choose reset and wait for the magic to work. Make yourself some coffee.
I still do not know how i got upgraded automatically. but just to be safe i hide updates kb2871389 and disabled the win8.1 upgrade nag screen:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\UpgradeNotification::UpgradeAvailable 1 > 0
ps/. finally nailed down the culprit: kb2973544. automatic upgrade to 8.1 ***without prompt***. is this even legal???
ps2/. if you don't want to upgrade to 8.1 too, uninstall and hide updates kb2885699 (nag screen), kb2871389 (nag screen and store). it seems that kb2973544 can't work without these 2 updates already installed.
Thanks a bunch for this write-up! As I mentioned in the thread on KB2973544 I got luckier than you and won't have to downgrade. But I will be uninstalling and hiding the updates you've listed.
domboy said:
Thanks a bunch for this write-up! As I mentioned in the thread on KB2973544 I got luckier than you and won't have to downgrade. But I will be uninstalling and hiding the updates you've listed.
Click to expand...
Click to collapse
hmm i wonder if i can do this with my nokia 2520 but where would i get the image i would need?
leo5111 said:
hmm i wonder if i can do this with my nokia 2520 but where would i get the image i would need?
Click to expand...
Click to collapse
I thought 2520 comes with rt8.1 right? Then you are probably out of luck...
Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73
Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...
Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.
Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie
Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie
added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie
The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.
Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!