Yoga Book Android - Can i boot to bios? - Lenovo Yoga Book Questions & Answers

A couple days ago i bought a Yoga Book Android with the intention to install Windows. Sadly i havent been able to do so because the bios boot menu seems to be hidden. However ive read some users that bricked their android os and the tablet automatically boots into bios which means there is a way to do it.
Anyone knows how?

Read the forum. This has been discussed like 1000 times. Short answer: not possible and never will as different bios on android devices

yes, you need to prees F7 (of Course by using external keyboard) before it boot up, Keep in mind the wrong using of bios will break your device

THE MAXIMUM POWER said:
yes, you need to prees F7 (of Course by using external keyboard) before it boot up, Keep in mind the wrong using of bios will break your device
Click to expand...
Click to collapse
F7 does not work on Android devices... It's ridiculously more complicated...
https://forum.xda-developers.com/yoga-book/how-to/boot-bios-how-to-android-t3593340

Related

Android for Netbooks/PC

I tried installing Live Android on a USB for my Acer Aspire netbook running Win 7 Starter but i can't figure out how to make it run from the USB drive?
Any help would be appreciated.
http://www.sizzledcore.com/2009/07/22/how-to-run-live-android-on-pc/
http://www.sizzledcore.com/2009/10/29/download-live-android-0-3/
http://www.sizzledcore.com/2009/07/22/create-a-liveusb-of-live-android/
To boot it, i'm guess you have to get to the BIOS screen. (i'm not too sure, err).
Try pressing F12, and then you should see a black screen, gray letters. (not sure how its setup on WIN7).
It should be an option to boot from the Flash Drive/Removable disk. Let me know how it works out.
Jincos said:
To boot it, i'm guess you have to get to the BIOS screen. (i'm not too sure, err).
Try pressing F12, and then you should see a black screen, gray letters. (not sure how its setup on WIN7).
It should be an option to boot from the Flash Drive/Removable disk. Let me know how it works out.
Click to expand...
Click to collapse
I was going to do this but was afraid i couldn't go back to normal booting. How would i go back?
matrix2004 said:
I was going to do this but was afraid i couldn't go back to normal booting. How would i go back?
Click to expand...
Click to collapse
I'm testing out the setup now. I know for linux, they do dual boots at the startup screen, asking you would you like to boot linux or windows.
I'm guessing when you install it, it might ask for a dual-boot or delete the windows partition and make android your OS. I'll test it out on my computer first. Then i'll report back to you.
I've done it just change the option to boot off external
It just boots from that and then when its unplugged it boots nornally
Sent from my Incredible using XDA App
matrix2004 said:
I was going to do this but was afraid i couldn't go back to normal booting. How would i go back?
Click to expand...
Click to collapse
I booted it on a Virtual Machine but anyway, there's no option to install therefore once you restart your computer, it'll boot your normal OS. No worries.
bump...............
Did this on my desktop and also created a VM.
i'm stuck on live android splash screen..............acer aspire 1 w win 7 starter
For those who cant boot to usb due to bios constrictions I found a way around it with this boot manager that has a Run from CD with an ISO file and it works flawlessly.
I might also point to similar thread here although OPs is older there is a lot of other useful info that might be helpful as well.
Guys ... check this out. http://www.android-x86.org/
I'm tested. 80% of the devices is working, except WiFi.
** Tested on Dell Latitude 2100 **

Problem with BIOS Tablet Onda v820w

I updated days ago with bad rom the Tablet Onda v820w with windows 10.
I found the correct Bios and now I have the correct file.
But now, I can´t access to windows to update the flash.
How to unbrick this tablet.
Some method to flash the bios outside windows?
The tablet power ON but screen is black, but microusb works It turns on the light of the hub that I have put
The BIOS brand is "Insyde".
If need moore details please ask me.
Very Thanks four your help.
Regards
can you access command prompt (CMD)?
or
can you access the bios and flash from there instead?
only ever flashed bios a few times (on desktop) but ive always done via the bios screens rather than in windows itself.
.
Hi
I can´t access to CMD, because the screen don´t turn on.
Only can put pendrive and Keyboard with MicroUsb hub. (This turn on the light when push the power button)
But I don´t know if tablet have some method to rescue the bios from Bad update.
Thanks
I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?
locoslaw said:
I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?
Click to expand...
Click to collapse
Hi I have the same tablet, when it works it is perfect, but the screen scrambles and the console become Un usable and freezes, i thought that it might just be windows 8.1 so I managed to put windows 10 on it last night but today it is doing the same thing. Could some one offer some advice.
Well...
Hi, I was able to fix a v975i tablet that was completly dead, because of wrong bios update, in my case i use a programmer unit and pro skills to weld. Basically you will flash the bios and download the correct bios , but i had to desolder the chip from the motherboard.

cm 12.1 rom is fine but "System UI has crashed" ;-;

My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
wifiwitch987 said:
My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
Click to expand...
Click to collapse
I think first I'd replace the PC. If that's not practical, try to boot it to this .iso once you've burned it to CD:
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Download the recovery.img to root's home, connect to the MOJO and turn it on, open a terminal and issue:
# fastboot -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
Should boot the MOJO into the recovery. If you can't get your PC to boot properly I think you're OOL. You might look into getting a used PC, one that's out-of-date or simply has a bad (or no) HDD, that you can pick up cheap, and use this simple Linux distro (Puppy Linux it is, with fastboot and adb binaries installed by me) for an OS. But be careful, Linux is addictive, and you may find yourself in the same predicament as I am: losing patience with the bloated domineering Windows OS.
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
wifiwitch987 said:
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
Click to expand...
Click to collapse
You can flash this (or most other linux live-CD .iso files) to a USB drive with a utility called Unetbootin. IIRC it's available for Windows, Mac, or Linux. I have no idea whether your Alpha is capable of booting to it, though. Any chance of borrowing another PC, maybe one a bit more traditional? Your little brother's old slow laptop maybe? FWIW I just finally managed to get fastboot and adb working on a Chromebook with an ARMv7 processor, but I doubt you want to go through that much work. Does the Alpha have an Intel processor?

Phone died, but I have another one. Any way to clone it to save the other?

Sorry for the confusing title. English is not my native language.
What happened is that I wanted to install Lineage OS on my phone (It have root+USB debugging and its in MM), but since I'm a noob, I ended up briking it.
It happened at the step where you should unlock the bootloader. In some way I could not achieve it, so I assumed it was because I did not know the "aboot partition" of my phone.(I still don't know what that is xd)
Long story short, I flashed the file "aboot.img" (which should go in "mmcblk0p5") in some other partition.
Yes, I know now how stupid I am ;-;
Now the phone is totally bricked.
No recovery mode, Download mode, Fastboot or Firmware mode (of which I'm aware) works. It does not even show the LG logo.
However, the phone responds to being connected to the pc (it vibrates!). It is even recognized in the Device Manager panel, as "LGE androidnet usb serial port (COM <any number>)".
It also responds when the battery is removed being connected by displaying an image on the screen.
So I conclude that the phone is not totally lost?...
The other part of the situation is that I have a spare Spirit. It's exactly the same as the other one, but it works (albeit the wifi deactivates itself every 5 seconds since a hit, so it's not useful for me).
And I was thinking if there is any way to make an exact copy of the other device or something like that? (like in a computer) Or use it in some way to save my main Spirit.
I mean, it's completely functional, apparently. It has a problem in the partitions, sure, but it seems that there is still some way to access the phone, right?
I know I'm new in this (I have some experience with computers, but little to nothing with Android devices), so I'm sorry if I just said a lot of stupid things.
But I would appreciate some help
Thank you very much for reading
nzkn said:
Sorry for the confusing title. English is not my native language.
What happened is that I wanted to install Lineage OS on my phone (It have root+USB debugging and its in MM), but since I'm a noob, I ended up briking it.
It happened at the step where you should unlock the bootloader. In some way I could not achieve it, so I assumed it was because I did not know the "aboot partition" of my phone.(I still don't know what that is xd)
Long story short, I flashed the file "aboot.img" (which should go in "mmcblk0p5") in some other partition.
Yes, I know now how stupid I am ;-;
Now the phone is totally bricked.
No recovery mode, Download mode, Fastboot or Firmware mode (of which I'm aware) works. It does not even show the LG logo.
However, the phone responds to being connected to the pc (it vibrates!). It is even recognized in the Device Manager panel, as "LGE androidnet usb serial port (COM <any number>)".
It also responds when the battery is removed being connected by displaying an image on the screen.
So I conclude that the phone is not totally lost?...
The other part of the situation is that I have a spare Spirit. It's exactly the same as the other one, but it works (albeit the wifi deactivates itself every 5 seconds since a hit, so it's not useful for me).
And I was thinking if there is any way to make an exact copy of the other device or something like that? (like in a computer) Or use it in some way to save my main Spirit.
I mean, it's completely functional, apparently. It has a problem in the partitions, sure, but it seems that there is still some way to access the phone, right?
I know I'm new in this (I have some experience with computers, but little to nothing with Android devices), so I'm sorry if I just said a lot of stupid things.
But I would appreciate some help
Thank you very much for reading
Click to expand...
Click to collapse
I had a same problem like you and i had to send it for a motherboard replacement.

Lenovo Tab M10 FHD Plus (X606f) won't power on after flashing older ROM

I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again ?
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
ldeveraux said:
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
Click to expand...
Click to collapse
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
python_rocks said:
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
Click to expand...
Click to collapse
assuming windows, check that your drivers are detecting the recovery module
ldeveraux said:
assuming windows, check that your drivers are detecting the recovery module
Click to expand...
Click to collapse
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch)...
Click to expand...
Click to collapse
Cool. Are you doing a Halium port for this device?
Yahoo Mike said:
Cool. Are you doing a Halium port for this device?
Click to expand...
Click to collapse
I'm not a Halium dev but I'm trying to flash the device. Me and another member of the community have our tablets dead after flushing it with supposedly Android 9 ROM. Not even Lenovo's Rescue Tool is helping now.
python_rocks said:
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
Click to expand...
Click to collapse
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
ldeveraux said:
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
Click to expand...
Click to collapse
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
python_rocks said:
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
Click to expand...
Click to collapse
Oh i misunderstood completely! That is worse, i have no clue how to fix it...
python_rocks said:
The tablet won't power on at all.
Click to expand...
Click to collapse
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Yahoo Mike said:
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Click to expand...
Click to collapse
Yeah, I've ordered opening kit. I'm going in. Quite a few people got their devices working by disconnecting the battery and connecting it back. I've noticed that no matter how long the
tablet is on charger the LED stays red, it doesn't change to orange or green.
This same problem has happen to two more members of the community. Same tablet.
We had to flag that ROM as it bricks the tablet.
python_rocks said:
We had to flag that ROM as it bricks the tablet.
Click to expand...
Click to collapse
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Yahoo Mike said:
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Click to expand...
Click to collapse
Thank you for trying to help.
The flash tool doesn't do anything when I click Download and plugging in the tablet while holding the volume down button. Dropdown option was set to "firmware upgrade" as advised.
The guide suggests that it's for people who can at least power on the device. It says "switch off the phone ..." which I don't need to do since I can't even switch it on
python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again
Click to expand...
Click to collapse
Did you mange to fix it?
A. Alaska said:
Did you mange to fix it?
Click to expand...
Click to collapse
You need to use a rework station heat gun or maybe a hair blow dryer might work to heat the sides of the screen to remove it.
I recommend cutting a water bottle in a square or rectangle shape then using the corner to slowly pry the screen off. After that remove the battery ribbon and hold the power bottom for 20-60 seconds to fully drain the charge.
Then recconect it and turn it on 100 percent works.
Just remember you must have the flash tool app and firmware ready in upgrade or download mode while holding down vol. It will reflash the tablet and bam will unbrick.
Just to note down my experiences here as well. I now also got into the same trouble. I tried
TB-X606F_S100015_191127_BMP.zip and also TB-X606F_S300091_201215_BMP.zip
It turns out that with these two you cannot start up the device anymore. Just as the thread-creator described. In my case pluging out and in again seems to give the SP FalshTool the chance to flash again (put it in "Download"-Mode before). So the latest firmware by today - TB-X606F_S300429_21110_BMP.zip - helped me to revive it again.
For me this is nice, but I also wanted to put Ubuntu touch on it just as described here: https://gitlab.com/ubports/community-ports/android9/lenovo-tab-m10-fhd-plus/lenovo-x606 ... unfortunately I am blocked now due to not being able to bring Android 9 on it. btw: There is no proposal on the site which firmware-version is even Android 9. I just guessed from the date.

Categories

Resources