Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
kaywoo said:
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
Click to expand...
Click to collapse
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
Yeah it's weird. Even after coming back to stock, unrooted, the hard-reset via stock recovery doesn't work unless USB is plugged in. Maybe some files are missing
Wow, I'm glad I stumbled on this thread, I was going nuts trying to figure out why I couldn't boot back into CWM after going back to the stock image and applying the OTA .zips.
Confirmed, I can get it to boot into CWM from fastboot only if I have the USB cable plugged in. Otherwise it just hangs on the Google splash screen.
Weird.
I've been able to boot into recovery using the app "quickboot" which had an option to reboot into recovery. My usb cable isn't plugged in.
Sent from my Galaxy Nexus using Tapatalk 2
This sounds a bit like my Nexus S i9020. It will only go into bootloader without the usb, and only go into download mode with USB attached (although it doesn't have to be powering it). This is the same on both handsets I've used. Maybe not a 'flaw' and more a nod to using fast boot/adb?
Sent from my Nexus S using xda app-developers app
I am currently having the same problem. Did anybody come up with a fix for this?
I'm having the same issue with the nexus 7. I've found out that you can boot into recovery if you have ROM Manager installed and select reboot into recovery.
Does anyone know if this is an OS issue or recovery issue?
Interesting. Was wondering why I couldn't get into Recovery from the Bootloader.
Another bug for me is that if I boot into Bootloader with the USB connected, I cannot make any selection using the volume keys. Only works if I boot in first without USB connected, then connect once I'm booted.
Its a bug, guys learn to search in the Development threads, I'm sure its being worked on,personally I've been able to get into recovery without have to connect via USB, if all else fails you can enter recovery via USB and ADB, by issuing the command adb reboot recovery in terminal/cmd
I had the same issue last week. Not sure what changed but now I'm able to get into recovery using the reboot menu or good mngr/rom mgr. No need for usb. I'm on modaco rom and used both clockwork and twrp.
Sent from my PG86100 using xda app-developers app
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
I have the same problem.
LTE Galaxy Nexus
Nexus 7 (16gb)
Miracle.vl63 said:
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
Click to expand...
Click to collapse
There are two different versions of CWM- one uses the power and vol-up/down buttons for keys- the other used the tablets touchscreen for button press functions.
You may have installed the touch(screen) version of CWM- try using the touchscreen for controls.
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
omegajester said:
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
Click to expand...
Click to collapse
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Trikkenut said:
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Click to expand...
Click to collapse
Nope, disconnecting the battery didn't change anything. Wug Fresh (Nexus Root Toolkit developer) informed me on Google + that it's a Google issue and it should be fixed in a future update. For now i'll be either plugging in USB to computer or ROM Manager.
I can't even get into the boot loader with my usb plugged into a charger not a computer
askho said:
I can't even get into the boot loader with my usb plugged into a charger not a computer
Click to expand...
Click to collapse
Try Quick Boot
Free, easy to use, will boot to bootloader, recovery, reboot etc... requires root of course, you already have that.
i dont't have root because it was screwed up right fromt he get go
Related
Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?
SpaceToast7 said:
Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?
Click to expand...
Click to collapse
Can you get to fastboot if you have the USB plugged in? If so you can use it to restore stock with the factory images from Google.
I managed to use the fastboot method to solve the problem. Everything went nicely for about a day, and just an hour ago my soft navigation buttons stopped responding to touch. A factory reset from the device did not resolve the problem. I'm going to try some work in ADB once I get access to a proper windows computer, but that may not be for a while, is there anything that might work that doesn't require a computer in the meantime? (I'm clueless when it comes to Linux. I tried installing Java and the Android SDK using a LiveCD of Ubuntu, but my efforts were met with frustration.)
You can just put windows on through a disk rather than buying a PC
Sent from my Nexus 7 using xda app-developers app
Nah, I have a fully functional custom rig, but windows killed itself and my cracked disk image of the install disk is on the same hard drive on the same partition. I'm waiting for my SSD to come in, so I can install Mint on it and burn the iso on my hard drive from there, then install Windows on my SSD.
At any rate, I used my friend's computer to flash to stock from fastboot and it didn't fix anything. Now, every time i try to touch the screen it just pulls the notification bar down to that point on the screen. I'm ready to re-lock my bootloader and bring it back to the store if nobody has a more convenient solution.
UPDATE: I rebooted from there and I'm back where I was in the last post. My navigation buttons at the bottom don't work, and sometimes touches don't register on the rest of the screen. The lock screen also doesn't respond to touch either.
ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium
player911 said:
ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
But I'm not attempting to do anything in ADB, unless there is some way I can use ADB to fix my nav bar and lockscreen.
UPDATE: It seems the lockscreen is working. Also, my navigation bar sometimes feels like activating buttons without me touching them.
UPDATE 2: And just like that my lockscreen isn't responding to touch again.
Bump?
can we launch fast boot while in recovery cause mine n7 always boot into clockwork recovery, i can not boot into my rom
Alright, I am having some trouble with the Nexus and hopefully someone can help me with this. Then Nexus was unlocked and rooted but I was still rocking the stock rom on there. The tablet used to be recognized by the computer and everything was fine. I used a car charger today to charge the tablet, came home, and the tablet would no longer show MTP when connected to the computer but rather would only charge.
I thought it was an issue with the rom so I downloaded a new rom, made a backup and went to flash it. Something happened when I was flashing the rom which forced the tablet to reboot and all it would get to is the Google screen. It won't go past that. I can get into the bootloader but can't boot into recovery or the system. Its not being recognized in fastboot mode either so I have no way to flash a recovery onto it...
Any suggestions?
have you tried force rebooting it a few times to try to get it ti boot up?
simms22 said:
have you tried force rebooting it a few times to try to get it ti boot up?
Click to expand...
Click to collapse
Multiple times. I have also used several different USB cables and ports on the computer. Still nothing
Any other thoughts?? I'm really in a bind
rmerchant786 said:
Any other thoughts?? I'm really in a bind
Click to expand...
Click to collapse
Can I take a look at it for you? Send me a PM and we will chat on google talk. I have some ideas though, we can connect remotely with teamviewer and I'll see if I can tell what's going on.
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Engstrom said:
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Click to expand...
Click to collapse
change your wire it maybe faulty or try it again on another pc
ngoralph said:
change your wire it maybe faulty or try it again on another pc
Click to expand...
Click to collapse
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Engstrom said:
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Click to expand...
Click to collapse
out of ideas but i used the wire given on the box and it worked but when i used different plug it didn't work
I have the same problem too after i meet flashing error in TWRP ~
I'm trying to flash Paranoid ROM update in TWRP, somehow the recovery show error when flashing so i decided to reboot system.
After that it stuck at Google logo and when I try to plug in the usb to computer, the fastboot freeze...
What to do man? Please help me
Please anyone help help ???
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
I had similar issue
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
Thanks for the reply mate
I can get into fastboot but once I connect the usb, it freeze and the toolkit I used (GNEX TOOLKIT) couldn't get my device :crying:
And sorry to ask, what is adb connection?
I only know fastboot, now my N7 only can boot in fastboot without usb plug in :silly:
But I will try to use the toolkit you recommend me, hope it works :fingers-crossed:
Thanks a lot
---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
wtgserpant said:
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
Click to expand...
Click to collapse
Haha...so what I have to do is wait for a few day and try again
Thanks for the advice
Google Fasfboot and ADB. Between the two of them, you can flash recovery, push & flash ROMs, etc. The Nexus 7 Toolkit makes Fasfboot & ADB commands pushbutton choices.
I'm not the lowest of the low, but I am the slowest of the slow.
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
So I managed to bricked Nexus last night trying to flash the factory images. It wouldn't flash correctly through the Nexus Root Toolkit, due to the outdated bootloader. I tried to install the 4.2 boot loader through recovery, (as it was flashable). It it didn't work, and I can't boot into recovery as it gets stuck on the splash screen. And of course I can do anything in fastboot because the tablet freezes when I plug in USB. Anything else I can try?
Here's some quick info.
Recovery- TWRP 2.3.3.x
Bootloader- 3.3.4
ROM- CM10.1
Sent from my Rooted Nexus 4
JiG Brick USB
JiG Brick USB might help, but i don't know for sure.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
Are you able to boot into boot loader? If yes, you are not bricked. You can flash the factory image and you can flash a new recovery.
Sent from my Nexus 7 using xda app-developers app
So I got back from school today and tried to turn it back on again, and it decided to boot up normally.
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Ethicistabdiel said:
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Click to expand...
Click to collapse
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
AndDiSa said:
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
Click to expand...
Click to collapse
What I mean is that as soon as the USB is plugged in, the bootloader on the Nexus becomes completely unresponsive, I can no longer use the volume buttons to navigate the options or the power button to progress. It appears for all intents and purposes frozen and remains so after the USB is unplugged. Commands sent from ADB while the Nexus is in the bootloader just say "awaiting device" and nothing happens and I can't see the Nexus with ADB Devices.
I may not be using the best terms, I'm assuming the bootloader is the screen where you are given the options of recovery, restart the bootloader, start and so on. That screen becomes completely frozen when the usb cable is plugged in. If I select for it to go to recovery and do not plug in the USB cable, it goes to the google splash screen and the recovery never loads. I've had this Nexus fully rommed before, it has Clockwork Mod Recovery Manager on it and I've had no trouble getting it to load previously.
I'm doing all this because I tried to install a new rom (Paranoid Android Nightlies, latest version) and it did not install properly, upon start it says gapps has stopped and the setup wizard has stopped working - the OS will not load but will just keep repeating these error messages. Thus, I'm trying to either get into recovery or send ADB commands to the tablet to fix it.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
All fixed now. It was actually the computer, an issue with the USB, did it on my laptop and was able to fix it pretty quickly. It was you differentiating Fastboot from ADB that got me there though, I tried that on my PC and when it didn't work I then did it on the laptop. Most likely wouldn't have gotten there without you, at least not so quickly. Thank you very much!
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.