Related
I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.
Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492
Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??
What!
can you get in the recovery?
Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.
Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!
Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?
Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window
I just recently installed Arch Linux with KDE as the GUI and I can't for the life of me figure out how to mount my Nexus S. It doesn't show up in /media so I don't know how on earth I can mount it. I've tried in CWM with mount USB and still nothing shows up anywhere on my system. Prior to Arch I was running OS X (10.7) and it was mounting fine. Obviously very different OS and Arch is a lot more complicated to use. I've spent several hours trying to figure out how to mount it but I can't find anything that solves it. Maybe anybody out there using linux could give me a hand?
Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.
Harbb said:
Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.
Click to expand...
Click to collapse
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.
Try in recovery first if it doesn't show up in Android. If it still doesn't show up I'll try to break my arch and fix it, whether its in android or cwm.
tycruickshank said:
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.
Click to expand...
Click to collapse
I've experienced this before as well. It turned out that I had a dodgy cable that's just not compatible with my NS for some reason.
If you want a pop on your KDE desktop when you enable UMS mode on your phone, make sure you udev is added to the daemon list in /etc/rc.conf. Then, you can either reboot or do /etc/rc.d/udev start and restart KDE again.
I've tried everything that you guys have said and still no luck. Its not showing up anywhere. Not in fdisk -l, I tried lsusb, looked in /dev/disk and it wasn't there. Nothing was pointing to a device being connected. I checked the everything.log file as well. Last photo is the everything.log and of course these were all taken with my phone connected to my computer. I tried multiple different USB cables too.
Sent from my Nexus S using Tapatalk 2
Just curious, with the phone on, and screen unlocked, what do you get with:
adb devices
?
Sorry but try to check it with other OS to be sure that your USB host is good .
Sent from my Nexus S
Unplug the USB. Then plug it back in then immediately run lsusb. If you dont see the device should be /dev/sdb1 should be the device according to your current fstab.
If it does not show in /dev/ or lsusb you have a bad cable.
Sent from my Nexus S 4G using xda premium
Well this morning it decided to work. I had turned my computer off last night and I tried it this morning with the same cable and it decided to work. I hope it's not going to be intermittent but seems to be working for now. Thanks everybody for all the help!
hey guys, for those that havnt seen it today Ubuntu has been released for the Nexus 7 and for both 8GB and 16GB Models! wondering if anyone in the community has figured out how to dual boot it or if it is even possible? thanks all!
Heres the link of how to install if your wondering
What you will need:
Nexus 7 Tablet (8GB or 16GB)
Standard MicroUSB Cable (should come with the device)
Ubuntu Nexus 7 Desktop Installer installed on your development system
Ubuntu 12.04 LTS or Later
Optional
Micro USB Host Cable (OTG Cable) - used for attaching keyboard, mouse, etc. Directions on how to get and use one of these are towards the bottom of this page.
Ubuntu Nexus 7 Desktop Installer
A simple one-click installer has been provided, and is available in a PPA.
sudo add-apt-repository ppa:ubuntu-nexus7/ubuntu-nexus7-installer
sudo apt-get update
sudo apt-get install ubuntu-nexus7-installer
Usage instructions for the installer are provided below.
Unlocking the Nexus 7
The Nexus 7 ships with a locked bootloader. You must unlock it in order to flash different images to the device. Fortunately, this is a trivial process, and you only need to do it once.
Warning: Unlocking the bootloader erases all data and resets the device to factory defaults.
Reboot the Android device into the Android boot loader. To do this, hold the volume down button and press the power button. Continue holding the volume down and power buttons until you see the boot loader UI. The device now displays the boot loader GUI, which looks like this:
Verify fastboot lists the device:
$ sudo fastboot devices
1234567891234567 fastboot
Start the bootloader unlock process:
sudo fastboot oem unlock
You are prompted on screen to unlock the bootloader on the Android device screen. Follow the on-screen directions to continue. Your screen should now look like this:
Complete the process by rebooting:
sudo fastboot reboot-bootloader
Or simply press the power button.
Installing Ubuntu on Nexus 7
Once all setup has been completed, the installation can start. To install, ensure the Nexus 7 is in fastboot mode, plug it into your computer (and make sure NO OTHER DEVICES are plugged in).
Find the installer in the dash (search for 'nexus'):
This will provide a Graphical Interface for installing Ubuntu. This tool will download the latest image automatically, and flash it accordingly. The flashing step should take about 2 minutes. Once the flashing is complete, the device will reboot and finish the installation. This step can take 10-15 minutes.
Returning your Nexus 7 to Stock Android
Warning: Disconnect ALL other mobile devices connected from your computer or they might get erased too. This will erase ALL DATA on your Nexus 7.
In case anything happens while developing, the system image for Nexus 7 can be found here: https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
After downloading the above tarball, uncompress it with the following:
tar zxvf nakasi-jro03d-factory-e102ba72.tgz
Then, place your machine into fastboot mode and run the resulting script:
cd nakasi-jro03d/
sudo ./flash-all.sh
You may get the following warnings, which you can ignore, the restoration will continue anyway.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Troubleshooting the Install
If you have problems installing the image, please use the following troubleshooting steps:
Detach the USB cable, restart the tablet back into fastboot mode, and re-attach the USB cable.
If problems persist, reboot your host PC.
If you still have issues, try a different USB cable.
If you have a 16G tablet, try using the 8G image.
If you still have issues after doing all this, return the image to stock using the directions above and re-try.
If none of that works, ask a question on Ask Ubuntu using the mobile tag, or ask for help in the #ubuntu-arm channel on freenode. If you believe it's a bug, file a bug against ubuntu-nexus7 in Launchpad.
Ehm, do i miss something or is this ubuntu only installation?
Edit: i mean, not dual boot, but only ubuntu
Do I need a mouse and a keyboard to use Ubuntu? Or I can also without them?
Rusl1TA said:
Do I need a mouse and a keyboard to use Ubuntu? Or I can also without them?
Click to expand...
Click to collapse
it has a built in touch keyboard/mouse, so you can do either way
you can use a touch screen for it, mouse and keyboard is compatible
what do you mean ubuntu only install?
sorry if you mis understood, but i posted the guide there but i am also curious if theres a dual boot avaliable.
is bluetooth not usable in the in ubuntu while installed?
And I saw this install method over at androidcentral.com and I dont recall it being dualboot. It did a complete install of ubuntu only and erased android from the device
As of right now, dual-booting is not an option, however, this build did just come out today, and in the coming weeks, we'll likely have many updates and options, so i'd hang tight. Needless to say, it's a great experience
yess dual boot will be awesome.
Download and follow the instructions in the complete Linux installation guide. (Its an app in the play store) It works pretty well and you can use Ubuntu, Debian and a few others without wiping your system. I prefer the Ubuntu lite version. Something else to try out
Sent from my Nexus 7 using xda app-developers app
technolust109 said:
what do you mean ubuntu only install?
sorry if you mis understood, but i posted the guide there but i am also curious if theres a dual boot avaliable.
Click to expand...
Click to collapse
Why did you title the thread as "Dual Boot Ubuntu" then?? Confused as well.
Change your thread title,its misleading.
yes my question was about dual booting, sorry if theres any confusion caused.
Folks, it's not that hard of a question when you actually read what the poster states. CURRENTLY, THERE IS AN INSTALLER THAT INSTALL UBUNTU TO THE NEXUS 7, BUT DOING THIS WILL CAUSE THE DEVICE TO BE FULLY WIPED FIRST REMOVING ANDROID. HE IS WONDERING IF THERE COULD BE [OR IS] AN INSTALLER THAT INSTALLS UBUNTU ALONGSIDE ANDROID TO BE ABLE TO BOOT THE DEVICE TO EITHER OS AS THE USER WISHES [ ALSO ASKING IF DUAL BOOTING BETWEEN THE 2 IS EVEN POSSIBLE.SO HE KNOWS IF IT IS WORTH HIS TIME TO INVEST IN MAYBE FIGURING IT OUT ON HIS OWN]. I am going to assume some form of dual booting would be possible as Linux bootloaders are generally very capable of booting OSes that use environments totally different from itself.
I am wondering the same thing as I am a very good technical user who can deal with a lot of issues, but have never gotten deep in to the programming side of things. I am shocked that for such an alpha build [really flaky Bluetooth, [Wi-Fi is solid] Unity crashes quite often and nVidia has had sucky Linux driver support for years now [wish they would take Linux more seriously but hey at least they have drivers]]. All leads to a painful experience for most [especially if you are not a nerd or techie and not used to dealing with very new alpha Linux type issues, if you don't mind it it does work].
Why wouldn't they have set it up as a dual boot to begin with? That way if you know something you need to get done can be done in Android and not in Ubuntu then you could just restart and choose the different OS. Not to mention if this is for modders and enthusiasts to test bed things on the tablet then they are going to most likely be some Android developers to start who would love to say use Eclipse to develop Android code for whatever and then oh no restart in to Android to I dunno test their work.
All that to say PLEASE SOMEONE WITH THE KNOW HOW let's figure out a way to fully dual boot a NATIVE Linux [not that install a loop file system and have it use VNC server to view the session junk you see on the Play Market, it's quaint and all, but not nearly as nice as a full Linux with full access to the hardware [I use it too, much love to backtrack] but am dying to dual boot an Android/More full [ I REALLY want Backtrack 5+ but Ubuntu would be worth keeping around until Backtrack gets around to working out their builds to be dual boot on some Android based systems] Linux as needed.
The approach that the Boot Manager app uses would probably work. They modify the /boot partition to point to a different device for /data than normal. Then you can switch between ROMs by flashing a different /boot partition. They automatically bundle the /boot partition into an update.zip and store them next to the image file on you SD card.
thanks for clearing it out RealPariah! by the way your username link to the band pariah orr? Cheers.
I would like to try this but what's the best/easiest way to back up my system? (I.e. app and game save data as well as for directory bind and folder structures). I tried clockworks backup process before, but I either did it wrong or it doesn't cover everything.
Can I just copy paste everything from my root folder?
Nikguy said:
I would like to try this but what's the best/easiest way to back up my system? (I.e. app and game save data as well as for directory bind and folder structures). I tried clockworks backup process before, but I either did it wrong or it doesn't cover everything.
Can I just copy paste everything from my root folder?
Click to expand...
Click to collapse
you might want to try and use titanuium backup and copy out the entire "titanium backup" folder onto your computer, so when you revert back to android you should be able to copy it back in and restore from titanium backup. hope it works.
technolust109 said:
you might want to try and use titanuium backup and copy out the entire "titanium backup" folder onto your computer, so when you revert back to android you should be able to copy it back in and restore from titanium backup. hope it works.
Click to expand...
Click to collapse
Huh great idea! Thanks, I'll give it a shot
all good mate! good luck!
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Here are the photos
njking25 said:
Here are the photos
Click to expand...
Click to collapse
njking25 said:
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Click to expand...
Click to collapse
That is something interesting. It is asking which os to boot to, not install.
I'd like to know how you got into the bios? I am looking for a way to install Linux....
Sent from my YOGA Tablet 2-1050F using Tapatalk
njking25 said:
Here are the photos
Click to expand...
Click to collapse
Did you get this figured out?
I can see "fast boot" enabled. Have You tried to switch it off? any other menu is displayed?
Have You tried to "power+vol down" on it?
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
zach181 said:
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
Click to expand...
Click to collapse
This guy seems to have stumbled on it also. I flashed the stock kk firmware and I am trying to do it but can't get Lollipop update to work. But it won't boot after it fails so I am reflashing KK again.
http://forum.xda-developers.com/showpost.php?p=60490907&postcount=578
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
zach181 said:
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
Click to expand...
Click to collapse
If you try it do let me know. I need to get into the bios to get started on a dual boot to Linux on this bad boy...
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
So... conclusion. we have to damage firmware to boot efi...
If we could swap img file before upload to tab (during this 25 second wait) we could make windows installation possible. Am i right?
zach181 said:
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
Click to expand...
Click to collapse
@social-design-concepts suggested we should try to change the boot order using efibootmgr. I've been communicating with him. Here is the post in the Venue thread... http://forum.xda-developers.com/show...postcount=2083
Links giving 404
zach181 said:
Links giving 404
Click to expand...
Click to collapse
here it is again... http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083 it got truncated.
Thanks workdowg.
It seems it's not as clear cut as first thought. Mind you, I didn't expect it to be. I did try a HP keyboard with OTG in Android and that got picked up ok (No lights on keyboard)
I'm a bit in the same mind as Social-Design. I'd rather have a definite way to restore Android from a totally blank internal drive before I have a go. Just up to page 214 in the thread so it may be covered later.
UEFI soft brick?
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Yosha1 said:
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You can get it to boot from USB? Get someone with to use tethered twrp and get a backup of the esp and fastboot partitions.
I have 2 things you can try if the goal is getting back to booting stock Android.
Yosha1 said:
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
Have You tried booting any x64 linux iso from flash drive?
dreamnewbie said:
Have You tried booting any x64 linux iso from flash drive?
Click to expand...
Click to collapse
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Yosha1 said:
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Click to expand...
Click to collapse
extract and dd this to a usb drive and see if it is able to boot it View attachment 3415895 if it successfully boots replace the fastboot.img thats on the thumbrive with one for your devices and see if it boots. if your fastboot.img is named droidboot.img rename it to fastboot.img.
If you can successfully get your devices droidboot/fastboot.img to load you can then disconnect the usb-otg cable and reconnect it to your PC and use the phone flash tools to restore your device completely.
Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!
What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol