Story goes like this: I got a chromebook for christmas and i tried to install linux because i do gaming and chromebooks dont have a set execution file type, windows has exe, mac has dmg, linux has a few such as python and deb files....chromebook has nothing. i decided to use johnlewis.ie to change os entirely but i hit a snag...Every time i attemp to boot from flash drive it says "Booting from hard disk..." and hangs. how do i fix this?
Related
I have a Malata T2 with 3g and have been happily trying many of the excellent roms in development from here with no problemes. I thought i'd therefore try the new 1.2 Build T2 3g rom from the download section of the malata.com web-site but messed up and downloaded the T8 3g rom by mistake but didn't spot this until after I had run the NV Flash.
The T8 rom loaded so far but then bricks at the honeycomb screensaver (and the left half of the screen is poor resolution and the right side is a solid white block).
I have obviously tried re-connecting to my laptop so I can re-flash the Flashback rom I had been running but the tablet no longer goes into the recovery mode when starting up whilst holding down the + button; and no longer cannoect to the laptop properly if starting up whilst holding the '-' button.
If connecting to my laptop as I would to flash a rom, my windows 7 laptop makes the normal usb connection sound and recognises the tablet as the Nvida Harmony in my connected devices. However, the laptop now shows a problem with the tablet and when i check the properties it states that the 'WPD FileSystem Volume Driver' has an error code 10 and that the device cannot start. This is preventing me re-flashing an alternative ROM via NV FLASH and when i try to, the nv flash programme says that there is no tablet connected to the laptop.
Obviously, the biggest problem with the tablet is the nube idiot who mucked around and got out of his depth(... me!) but is there anyone on this forum who can help me out and tell me how to get the tablet back to the point where I can communicate with it from my laptop and nvflash a T2 rom again!
Any help would be greatfully appreciated.
Turbo_kf
Try doing the nvflash on Linux. Follow instructions in this post and run a live CD.
1. You will have to use a Linux version of the nvflash utility that you use on the T2. And, before you ask: I don't know if the Linux nvflash program for the gTab will work on the T2. It may; it may not.
2. After you've booted into the Linux desktop, download all the files needed somewhere. I recommend putting it all--both the extracted .img files and the nvflash program--into some directory in /tmp, say /tmp/nvflash-t2. Boot the T2 into APX mode, run the Terminal Emulator, then type:
Code:
$ [B]cd /tmp/[I]nvflash-t2[/I][/B] [I]Change to dir containing all files[/I]
$ [B]sudo ./nvflash [I]... [/I][/B][I]Run nvflash with superuser permissions[/I]
anyone else have a solution that doesn't involve running linux cd's
okay with windows, but not with linux
still stuck
I have taken the advice, run the linux cd and still cant rescue it. From shell, i can see it is there at ./dev/sdb and it sees the tablet when i type lsusb. But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Any suggestions... going of on holiday next week and woukd love to have it recovered by then
Turbo_kf said:
But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Click to expand...
Click to collapse
1. Most likely, you did not put the T2 into what's called APX mode--this is a common mistake. Please, read my original post more carefully.
Also see this post for more info (it's for the gTab, but, it may also apply to the T2).
2. Did you use the nvflash for the T2 (if one exists)? What were the exact commands you used?
still stuck... cant get apx mode
I can assure you that i have been trying to get APX mode from the moment it went wrong ...the inability to get APX mode no matter what i try is where the problem is.
i have run the adb.zip i read about on this forum and run dmesg on both the shell (dmesgshell.txt) and normal (dmesgnvid.txt) and have attached the two outputs.
There is clearly some software problem with having run the T8 rom that is preventing the T2 tablet form going into APX mode and a noobie like me just doesn't have the knowledge to work out what i do now...
any help in how to restore the APX mode so i can flash back the malata T2 stock base1.2 rom would be appreciated.
Thanks
I wanted to reflash Android after unsuccessful Xposed install and accidentally used the wrong file in the Manufacturing Flash Tool.
I now have no Android, no Windows -- just BIOS and fastboot are functional. When it boots normally all I see is a UEFI shell with the list of partitions.
I've tried using MFT with the correct file and it didn't help.
I think I need to set up proper (dual-boot) partitions thru fastboot and only then try flashing Android again. Can anyone please help?
Android flashed just fine once I switched from a Windows XP running in a VM to a laptop running Windows 7 64bit.
I'm having problems rolling over the Windows image, I'm guessing it's because I've messed up the partition table -- it can't find the drive with the images now. Anyone had that?
I have a Dell Laptop running windows 10 and boots via UEFI. I have installed Remix OS beta (64 bit version) several times on the HDD using the Remix program available when downloading from their website. Apart from one occasion only, Remix usually hung and I remained patient, waiting for a version that would work. That happened with the latest version (2.0.403) i.e Remix finally works and the OS boots up normally. However (as is usually the case with life in general) whilst Remix works, when selecting windows from the Grub loader it says that it cannot find the path to windows and I cannot boot into windows. I appreciate that this is a Android forum but this problem is specific to Remix I think and some entry in the grub loader and as such I turn to this forum in case anyone has any ideas so that I can fix the grub loader or whatever and be able to boot into windows - I am of course happy that I can boot into Remix but I also still need my windows!
Thanks a lot in advance
Andrew
did you installed them in 2 separate hard drive?
and your computer use bios or uefi.
if it is uefi you should check if the old windows boot loader is still here.
and if it is 2hdd you should boot directly to windows hard drive. by changing your boot settings.
tailslol said:
did you installed them in 2 separate hard drive?
and your computer use bios or uefi.
if it is uefi you should check if the old windows boot loader is still here.
and if it is 2hdd you should boot directly to windows hard drive. by changing your boot settings.
Click to expand...
Click to collapse
Thanks. They are on 1 hdd and it is UEFI. I don't know how to check if old boot loader is there but I have tried the repair option on the windows CD/USB including repair MBR without any luck. So I think the old boot loader is gone and replaced by Grub.
Ajd34b said:
Thanks. They are on 1 hdd and it is UEFI. I don't know how to check if old boot loader is there but I have tried the repair option on the windows CD/USB including repair MBR without any luck. So I think the old boot loader is gone and replaced by Grub.
Click to expand...
Click to collapse
to see if the bootloader is still here you should go to your uefi and boot option.
it is generaly holding del while booting to acces it.
you should see in boot windows boot loader and grub.
you should be able to switch them
if your windows installation is not gone.
tailslol said:
to see if the bootloader is still here you should go to your uefi and boot option.
it is generaly holding del while booting to acces it.
you should see in boot windows boot loader and grub.
you should be able to switch them
if your windows installation is not gone.
Click to expand...
Click to collapse
Thanks. On the Dell laptop it is F12 and there is an option under UEFI BOOT to choose Windows Boot Manager but selecting this goes to the Grub Loader. I need somehow to edit the Grub loader to point it back to where windows is residing unless Remix has deleted the windows partition??
Ajd34b said:
Thanks. On the Dell laptop it is F12 and there is an option under UEFI BOOT to choose Windows Boot Manager but selecting this goes to the Grub Loader. I need somehow to edit the Grub loader to point it back to where windows is residing unless Remix has deleted the windows partition??
Click to expand...
Click to collapse
yes if you used command lines to install remix ,it can format the boot loader partition...
i hope this will help you.
http://www.howtogeek.com/howto/33433/restore-the-windows-boot-loader-after-an-ubuntu-update/
edit; here win 10
https://blog.d0zingcat.xyz/2015/09/28/Windows/How to repair the EFI Bootloader in Windows 10/
tailslol said:
yes if you used command lines to install remix ,it can format the boot loader partition...
i hope this will help you.
http://www.howtogeek.com/howto/33433/restore-the-windows-boot-loader-after-an-ubuntu-update/
edit; here win 10
https://blog.d0zingcat.xyz/2015/09/28/Windows/How to repair the EFI Bootloader in Windows 10/
Click to expand...
Click to collapse
Many thanks although this did not work. Clearly something went wrong when Remix was installed but I cannot understand what exactly. Anyway, I feel that I should not trouble this forum further since it seems like a problem now more to do with a corrupted Windows or Grub Boot loader issue than a Android issue. What I was hoping in particular was that someone had had the same issue after installing Remix and how therefore they dealt with it but it doesn't seem that this is the case. Looks like I am the only (un)lucky one!
Thanks again
Andrew
Ajd34b said:
Many thanks although this did not work. Clearly something went wrong when Remix was installed but I cannot understand what exactly. Anyway, I feel that I should not trouble this forum further since it seems like a problem now more to do with a corrupted Windows or Grub Boot loader issue than a Android issue. What I was hoping in particular was that someone had had the same issue after installing Remix and how therefore they dealt with it but it doesn't seem that this is the case. Looks like I am the only (un)lucky one!
Thanks again
Andrew
Click to expand...
Click to collapse
UPDATE: I placed a Windows 7 installation disk in the laptop and turned it on (as I had read that trying to use the bootfix from a USB may not work). The laptop then started to boot windows 10 normally and by-passed the Grub loader! I cannot explain how this is possible but once Windows booted I uninstalled Remix. I rebooted and the Grub loader was gone. I then installed Remix 3 (as I am a sucker for punishment) and the new Grub loader works fine - the laptop now boots into Windows & Remix!
Thanks for those who replied
Regards
Andrew
So, I done this again, I was trying to install remix os. Since my pen drive was full of documents and the spare one was not at home, I tried installing it on my hdd and now I'm ****ed. I did it the "unofficial" was using easybcd 2.3 .
The whole process is given below. 1 - made a 18 gb partition. 2 - copied content of the iso into the drive. 3 - made a new entry in easybcd. 4 - rebooted pc and the problem started,
The problem is that I don't get the option to choose between Windows or remix os. I can't boot from my windows disk because the keyboard is not recognized by the system. Can't choose between guest or resident mode. Since my keyboArd is not working, it boots into residence more after 20-30 seconds. It gets struck on the remix os logo. Been there since then.
Don't known what to do, maybe have to take my system to an engineer.
Any help will be appreciated. Thanks !
Hmm..
Thats wierd... I tried the easybcd options ones or twice..
If you add boot ISO.. then your first default boot should still be Windows
Perhaps a different Keyboard? its win8... So a mouse should work if you have the metro bootloader
Anyway... If you have Windows Install Disk... you can use Recovery console..
https://neosmart.net/wiki/recovering-windows-bootloader/
A better/quicker? solution.. Hirens Bootcd.. Mini WinXP... then edit BCEdit
But whats your hardware?
Can you access grub? When you get option quest/resisdend Try hitting keyboard : Tab (try adding DEBUG=1 to boot parameter)
Goodluck..
Thanks but
Thanks for the reply. But the problem is that I can't access grub. My keyboard doesn't work when I'm at choosing whether I want to use best mode or residence mode. I wait for 30 seconds and then it automatically boots into residence mode. When the remix os logo appears my keyboard starts working. I can turn on caps and num lock. But what's the use of it ? Also, I have a p/s 2 keyboard. I have asked my father to bring a usb keyboard. If that works , I would boot into guest mode that seems to be working for other people. I would also try changing the default boot system to Windows.
A hard brick is where your phone starts to bootloop but you cannot enter recovery nor fastboot. A hard brick is caused where you flashed a incompatible ROM/Recovery/Firmware,etc. If you ever hard bricked your phone then this thread can unbrick your phone. Any OS is supported. Linux, Mac and Windows. Now to get started, install this softwares:
SP Flash Tool
Python 3
Virtual Box (MacOS)
You also need knowledge in bash, python (I am not responsible if the steps did more damage than you hard bricking your device)
For users who's doing this guide in MacOS. Make a Windows 10 Virtual machine then download SP Flash tool in it. Download MTK Driver here in the Virtual Machine then run it.
And maybe sure to drain your phone's battery first before doing something.
After installing, download this link below (Code > Download ZIP):
Bypass (Bypasses MediaTek's Security inorder to flash)
Payloads (So that the bypass can work)
Download Stock ROM here then extract it. (For MacOS users, download it in the Virtual Machine.)
(Credits to the owners who made this scripts)
After downloading, unzip the 2 files and in the exploits_collection folder (Payloads), copy the two files and folder named "default_config.json5" and "payloads" then put it to the bypass_utility folder (Bypass). Once done, open terminal and type following:
pip install pyusb json5
Also for MacOS users, dont run it in the Virtual Machine you made or else it wont be recognized.
Run the script and just like i said you must drain the battery first or else it will error in SP Flash Tool. After running you will see a message that says "Waiting for device". Hold Volume Down then plug your phone (Volume Up or Volume Down+Up if not recognized) then you should see a message that says "Protection Disabled". DO NOT UNPLUG IT OR TOUCH IT
python main.py
If ur running in MacOS > Launch the Windows 10 Virtual Machine, open SP Flash Tool.
If ur running in Linux, Windows > Open SP Flash Tool
Open SP Flash Tool then go to Options in top left, go to Connection, press UART. If your phone is connected and bypassed, you should see a option in the selection COM. Then go back. Press Select in "Scatter Loading File", locate to the Stock ROM you downloaded then go to images. You should see a file named "Scatter" in the end of it then select it. The Flash Tool will read it then you can press download. It if succeed, you will see a checkmark window popped. Then reboot the phone. If you dont like the Stock ROM, fastboot is back again and you can flash anything you'd like. Any problem? Check out FAQ below
FAQ
1. When flashing, an error popped up saying STATUS_RAM_EXEPTION
You din't drained the phone's battery. If you did not, you have to wait a couple days. You can check if its drained by holding the power button.
2.I cannot detect my phone while bypassing.
Close VirtualBox or any softwares that is catching any USB devices.
3.Cannot find device in VirtualBox
Download the extension pack after downloading then go to VirtualBox, press ur Windows 10 Virtual Machine, press Settings in the top, go to Ports then USB then choose "USB 3.0". Press OK
4.I cannot find my question here
Comment down below.
Sorry for the wrong grammar i placed in this thread.