Is there a way to flash a factory image to the thrive using android recovery via pressing volume up and power button and selecting the middle option which takes you to the menu to install.zip from sd card, I get that far and it gives me an error (e verification failed) I do not have root or Clockwork, and cannot install either do to the system/xbin file being deleted so the tool has nowhere to instal the ROOT and it says File Location Does Not Exist when Trying to add the xbin files.
So Is there a "Signed" stock rom available that I can just install from the sd card via the "Stock Android Recovery"
If anybody has a signed stock android Toshiba Thrive Rom that I can restore to the device without ROOT or CLOCKWORK that would be awesome and I would be most greatfull!!!
No, there is no signed stock image available. You can flash the stock ROM, but you will need to flash ClockWorkMod recovery onto the device and load the stock image available on thisone.org or thatone.com.
Now the Clockwork Recover Mod and The Clockwork Recover Tool from marketplace are two separate entities as I understand it, so I can flash the recover mod without root correct? I'm going to give it a run and keep you posted.
DaveNavy said:
Now the Clockwork Recover Mod and The Clockwork Recover Tool from marketplace are two separate entities as I understand it, so I can flash the recover mod without root correct? I'm going to give it a run and keep you posted.
Click to expand...
Click to collapse
The one on the market will not work with the Thrive. YOu will need to get my Easy Flash Tool from thisone.org or thatone.com. It hase a version of ClockWorkMod recovery that will work with the Thrive. YOu are correct that you do not need to eroot to install it. You do need to knoiw that you have to go back into recovery before the device boots or the ROM will replace the recovery with the stock version.
all back to stock and updated to the. 11 update, thanks so much
issues
update: *deleted*, figured it out.
Need help with Toshibe Thrive
I have a Toshiba Thrive 10.1 (with 32GB RAM) that recently quit on me. All it will do for me now is boot up to the splash screen (the one saying it's a Toshiba and such) and then stops doing anything other than showing that screen. I've tried the data/factory reset option, but that doesn't change anything (it still boots to the same point and locks up). The factory reset ROM's I've tried all fail at "Verifying update package..." with the error "E:signature verification failed" followed by aborting... I've been able to fix computers since Win 3.1 (yeah, showing my age a bit) up until now with no real problems, but Android is a different animal... I've tried the "Thrive USB ADB" utility, Toshiba Easy Flash utility, and a few different factory reset ROM's... All have failed....
Also worth saying.... When trying the Easy Flash Tool and doing exactly as it says (except for not being able to tell the device to go into USB debugging mode), all the utility seems to do is sit and wait for my device.
What I may need is a step-by-step, get this file, do this thing, type of help...
Keeblerdawg said:
I have a Toshiba Thrive 10.1 (with 32GB RAM) that recently quit on me. All it will do for me now is boot up to the splash screen (the one saying it's a Toshiba and such) and then stops doing anything other than showing that screen. I've tried the data/factory reset option, but that doesn't change anything (it still boots to the same point and locks up). The factory reset ROM's I've tried all fail at "Verifying update package..." with the error "E:signature verification failed" followed by aborting... I've been able to fix computers since Win 3.1 (yeah, showing my age a bit) up until now with no real problems, but Android is a different animal... I've tried the "Thrive USB ADB" utility, Toshiba Easy Flash utility, and a few different factory reset ROM's... All have failed....
Also worth saying.... When trying the Easy Flash Tool and doing exactly as it says (except for not being able to tell the device to go into USB debugging mode), all the utility seems to do is sit and wait for my device.
What I may need is a step-by-step, get this file, do this thing, type of help...
Click to expand...
Click to collapse
There isn't one, it needs nvflashed back to stock, it will work provided there is no emmc damage/failure which does happen occasionally. There's only a few people with the Toshiba files to flash it back fresh, shoot me a pm and I'll help you out with that.
Sent from my Nexus 7 - JBSourcery 4.5
Related
I installed ADW launcher, and like an idiot, didn't do a backup first, and upon rebooting the phone, it now hangs part way through the boot; It's Syndicate's Shuriken ROM, and it hangs at the "Samsung Epic 4G" screen with the multi-colored X. Is there ANY way to get into the phone's memory and pull phone logs, SMS, MMS and Angry Birds data? When I boot into recovery (although I have clockwork installed, I can only get to the samsung recovery), the SD card shows up on my PC as a drive without media since the SD card is mounted, so the PC sees the phone. ADB shows no devces connected, altough the only adb I have is what came with the andromeda one click flasher. Is there something else that I need?
Is there anything I can flash using the stock recovery that'll get the phone to boot or even only show up in adb? I don't realy care if the modem's there or not, or how stable it is. I've tried flashing a handful of "stock" updates, but all failed with various verification errors. I had CW installed, but apparently it got replaced by the stock one. All I need to do is run "Backup Everything" to get my SMS, MMS & Phone logs, and Root Explorer to get my AB data. After that, I can (probably will) Odin back to what I was running, or maybe one of the newer Froyo's until the official release is out.
If you have cwm you can just reflash a rom without a wipe to get the info you want. The only updste.zip i know of that can be flashed threw recovery is the one for dk28
Sent from my SPH-D700 using Tapatalk
The problem there is While I had CWM installed, I've always had trouble getting into it. It seems that at some point, the ROM overwrote it with the stock recovery, so the only way for me to flash anything is with the stock recovery, or to extract the flash data from download mode if that's possible. How do people get ODIN dumps? I assume that's just a complete read of the flash.
Been doing a lot of searching and reading, and came across this thread. Using Odin to flash the clockworkmod.tar (which has recovery.bin inside it) shoudl replace the factory recovery, shouldn't it? I tried flashing it and I still get the Samsung recovery. Is there a newer version than in that thread that I can download and try to flash in the same way?
Ok, I actually managed to get somewhere. I got CWM Recovery to take, but it's v2.5.0.4, and doesn't seem to be working 100% right. I can't mount the SD card to USB, it doesn't want to do a nand backup, and the smiley button moved the selection bar up, "H" is enter.
Edit: I then managed to get 2.5.1.0 installed, so now keys are functioning properly, and it would seem I was able to get a successful backup. Is there a way to get into the img files in the backup, or is it likely that if I odin it back then advanced restore the data back, it'll be accesable?
Well, I got all the data I wanted to get. As my last post says, *somehow* I managed to get CWM Recovery to take via Odin (Is try, try, try again, try some more perseverance or insanity? ), and then was able to update it to 2.5.1.0, at which point CWM started functioning properly. I then was able to use the DI18 > DK28 update zip, which got me into a funcioning device, which allowed me to back up the data I was looking to get. Of course from there, restoring it back to fully functional was easy.
EDIT: This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
Not trying to be rude or anything, but I don't remember this ever not working.
I am having issues with 3e. No matter how carefully I follow the instructions (flash->reboot->reinstall packages always fails) when flashing recovery from current Rom Manager and Premium License, it does not work. Additionally, the premium license is persistent in my applications list and no premium ROMs ever show up in my download list. Even when I select Vibrant MTB and either 2.x or 3.x, all I get is a message that states current recovery will be used. I'm still going thru posts for a possible solution.
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Yeah, I was misinformed. This is not a result of ROM Manager, this is a result of installing Overstock 1.4.3 which also installs CWM recovery.
If anyone want to do this it is really simple with the SGS kernel flasher app. Download your overstock kernel of choice from here or your choice of kernel that includes CWM from the dev bible, unzip it, move the zimage to the internal phone memory and then choose that file as your kernel with the SGS Flasher.
Note: I have not been successful with going back to stock kernel when I tried to but that may have been because I didn't disable the lag fix.
jneal9 said:
Try putting this in the root of your internal SD, reboot to recovery and reinstall packages twice.
Click to expand...
Click to collapse
I'm 100% stock on 2.2Froyo except for root/unlock and am puzzled by this. I know it's not ROM Manager because it worked on my first SGS4G which died and totally bricked after a week (TMO exchanged it happily cause it wouldn't even go into download mode or charge).
What's in this update you linked? Cause I'm smart, but not as smart as most of the posters here and I recognize only a couple things in the file.
It installs CWM.
Are you using a Vibrant or SGS4G?
SGS 4G for TMobile.
BTW... I totally appreciate the help here. I don't know the ins-n-outs of the android phones like I do IOs, not that I'm all that up to date on that either.
Update... Still does not work. I get the failed signatures error and the update is aborted. I tried doing a factory reset and re-rooting the phone in case something didn't work correctly and get the same error. At this point, it's all gravy since the only thing I really needed was the unlock but now I'm in a "I just want to know how this works" mode.
Thanks for the help.
Ok yeah that my be the problem since that zip is for the Vibrant. So just to be straight, you are unable to get CWM on your SGS4G?
That's correct. I can't apply any update.zip nor does flashing CWM recovery work. It says it's flashing but then when I do the 3 button reboot to get to recovery, it's the 3e version still and when I go to reinstall packages, it starts but then fails as it tries to verify signatures.
I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?
You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM
Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh
I'm new to the Moto Droid world coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
beeewell said:
I'm new to the Moto Droid world
coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
Click to expand...
Click to collapse
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Thank You !!
ATTACK said:
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Click to expand...
Click to collapse
Thank you so much for your reply, and for pointing me to the correct TWRP for my device. It worked like a charm !! :good:
:crying: My device boots in CHERRYVIEW D1 PALTFORM/INTEL (CHTTYETI.X64************) ((something like Windows BIOS??)
And that all.
I tried Platform Flash Tool Lite but missing flash.xml file. but even I am not sure it will work...
any advice or other solution please....
mmusaad said:
:crying: My device boots in CHERRYVIEW D1 PALTFORM/INTEL (CHTTYETI.X64************) ((something like Windows BIOS??)
And that all.
I tried Platform Flash Tool Lite but missing flash.xml file. but even I am not sure it will work...
any advice or other solution please....
Click to expand...
Click to collapse
what did you flash and what did you exactly do?
Hi
I have twrp backup..
I wiped everything using twrp...
Then restore my backup..
in restoring option I had two bootloaders I removed first bootloader and used the second bootloader..
Also I removed data backup...
Then it start to load only bios screen
mmusaad said:
I have twrp backup..
I wiped everything using twrp...
Then restore my backup..
in restoring option I had two bootloaders I removed first bootloader and used the second bootloader..
Also I removed data backup...
Then it start to load only bios screen
Click to expand...
Click to collapse
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
maybe it's 'flash_factory_update_pos_bootloader' - my guess it only updates the bootloader partitions...if it works and you have a bootloader again you could probably load recovery again and restore your system / data.
(you might use 'flash factory 1st stage' and ' flash factory 2nd stage' as well (i think those flash the whole system again, but I'm not sure. it's just a guess.)
hope you will manage it
look at the flash_guide.docx, it's in chinese but with google translator you can get some information about it.
to use the flash tool i think you must boot into dnx fastboot mode...hold 'volume up' + 'volume down' + 'power' to get into dnx mode (yes, pressing vol up and vol down at the same time works!)
maybe
Hi
danjac said:
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
maybe it's 'flash_factory_update_pos_bootloader' - my guess it only updates the bootloader partitions...if it works and you have a bootloader again you could probably load recovery again and restore your system / data.
(you might use 'flash factory 1st stage' and ' flash factory 2nd stage' as well (i think those flash the whole system again, but I'm not sure. it's just a guess.)
hope you will manage it
look at the flash_guide.docx, it's in chinese but with google translator you can get some information about it.
to use the flash tool i think you must boot into dnx fastboot mode...hold 'volume up' + 'volume down' + 'power' to get into dnx mode (yes, pressing vol up and vol down at the same time works!)
maybe
Click to expand...
Click to collapse
Thanks hope it will work.
if you have an alternative download link as this link is really slow...
mmusaad said:
Thanks hope it will work.
if you have an alternative download link as this link is really slow...
Click to expand...
Click to collapse
not at the moment...
can you once more explain in detail what you did and how you ended up having no bootloader anymore.
i'm still trying to figure out how you were left with no bootloader (can you post a picture of that ?bios?).
i just want to know whether this is somehow related to the ported twrp. from my knowledge there's no way to wipe the bootloader or whatever.
thx in advance
Hi
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
mmusaad said:
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
Click to expand...
Click to collapse
if you can access twrp again, just restore your backup as it is...all partitions without changing anything.
good luck. hope it works.
now people know how to get to the bios/bootmanager (maybe it helps for dual boot)
do you know what options there were, something like boot from sdcard/otg (usb) etc...?
Hi
There where two options
Android IA
EFI Hard Disk
As for my issue I was able to boot twrp and restore my backup..
But it seems I played around bios screen which ended up not showing bootloader or recover option even bios....
It's feel like something running but not showing in the scteen. Is there any way to reset bios or a stock rom to restore the device like out-of-box status....
Hi
mmusaad said:
There where two options
Android IA
EFI Hard Disk
As for my issue I was able to boot twrp and restore my backup..
But it seems I played around bios screen which ended up not showing bootloader or recover option even bios....
It's feel like something running but not showing in the scteen. Is there any way to reset bios or a stock rom to restore the device like out-of-box status....
Click to expand...
Click to collapse
I found out that it was running through HDMI output in the initial boot and it will not show in the tablet screen..
I did it again with bootloader modification and got the BOIS mode and connecting my tablet to LED TV through HDMI output I managed to reset the bios and got it back to normal (know boot showing in my tablet screen...)
When i flash the file you share and used flash/blank setting it will reach 80 to 85% but fail in bootloader flashing. then i used DXN mode and fastboot flash twrp recovery it will bring the main service options where I did factory reset then it will start loading with little screen corruption. however it will load perfectly after couple of reboots but without the Halo Keyboard. i could not find out how to enable it...
Then i used my TWRP backup and restore it where everything working fine....
My request is it possible to modify the flash-able file you send to load a perfect stock rom. it will help many people as it will be easy to use with Intel android flash tool...???
Thanks mmusaad and danjac, glad that you unbricked it.
Can I ask how does one flash it with Platform Flash Tool Lite? I failed to infer the meaning of 'setup your board' from intel's description:
> You have already set up your board and connected the board to your host system. This includes assembling your board, installing the appropriate drivers, and flashing your firmware.
(I'm trying to run or install Linux on yogabook, which I feel may brick it a few times.)
Also, do you think one can enter the BIOS setting or boot device selection without bricking it first?
thanks
Hi
momocraft said:
Thanks mmusaad and danjac, glad that you unbricked it.
Can I ask how does one flash it with Platform Flash Tool Lite? I failed to infer the meaning of 'setup your board' from intel's description:
> You have already set up your board and connected the board to your host system. This includes assembling your board, installing the appropriate drivers, and flashing your firmware.
(I'm trying to run or install Linux on yogabook, which I feel may brick it a few times.)
Also, do you think one can enter the BIOS setting or boot device selection without bricking it first?
thanks
Click to expand...
Click to collapse
Try installing this file it suppose boot correctly...
https://software.intel.com/system/files/managed/1e/e8/IntelAndroidDrvSetup1.10.0.zip
mmusaad said:
Try installing this file it suppose boot correctly...
https://software.intel.com/system/files/managed/1e/e8/IntelAndroidDrvSetup1.10.0.zip
Click to expand...
Click to collapse
Thanks, I was able to flash with FlashToolLite (linux). The only problem is that my halo keyboard stopped working (maybe rom dismatch? My yogabook is from japan).
Anyway thanks /o\
momocraft said:
Thanks, I was able to flash with FlashToolLite (linux). The only problem is that my halo keyboard stopped working (maybe rom dismatch? My yogabook is from japan).
Anyway thanks /o\
Click to expand...
Click to collapse
Did you have any TWRP backup.?
I have faced the same issue the solution was to restore boot & country img. Or one of them....mmmm I forgot...
danjac said:
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
Click to expand...
Click to collapse
Greetings to all.
@danjac: Could you provide a link to a YB1-X90F ROM? I would like to try flashing it on a chinese version model. @mmusaad: please excuse my irrelevant to the subject request.
mmusaad said:
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
Click to expand...
Click to collapse
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
sagi232123 said:
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
Click to expand...
Click to collapse
What you ask for was only a few clicks away my friend:
https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
sagi232123 said:
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
Click to expand...
Click to collapse
Hi sagi232123,
I will explain it to you in detail.
I taken a full backup using twrp.
Then I notice two bootloaders.
First named bootloader. "note: I don't remember the full file name."
Second named bootloader1.
I removed bootloader.
Renamed bootloader1 to bootloader using my PC.
Then restored using twrp again, I restored it fully.
Here I was shocked when it load the bios.
Do it and it should do the same.
nan0s7 said:
What you ask for was only a few clicks away my friend:
https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
Click to expand...
Click to collapse
this is diffrent , running linux through android , i want to run from bios without android
https://forum.xda-developers.com/yoga-book/how-to/boot-bios-how-to-android-t3593340
this is the tut
Hello, I also had a brick problem. I managed to flash the firmware of 270916 then the OTAs until the last of April 28th. All works fine, Halo keyboard, wifi etc but the problem is that tablet no longer recognizes the sim card! Om settings the Sim option are greyed. Any help?