{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By George I've got it! Not really actually but I do have a pre-alpha release of kubuntu mobile edition running on my gen 8 tablet
check it out here: http://forum.xda-developers.com/showthread.php?t=1052697
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
BabelOued said:
Hi,
You have prebuilt image for n900 there http://cdimage.ubuntu.com/kubuntu-mobile/daily-preinstalled/current/
As it is same processor, you can try, i m doing the test right now.
Babelo
Click to expand...
Click to collapse
Yes I saw that but the touchscreen doesn't work. I've actually managed to compile it (you can find my new thread in the developer forum section) I'll add the download link on the new thread in a few hours. The major problem is that my current "build" takes my to the login screen but because there is no virtual keyboard, I can't log in
http://forum.xda-developers.com/showthread.php?t=1052697
It seems workable, but how about 70?
LeoNg628 said:
It seems workable, but how about 70?
Click to expand...
Click to collapse
I have an archos 70, that's what I'm testing it on.
shrewdlove said:
I have an archos 70, that's what I'm testing it on.
Click to expand...
Click to collapse
but he said virtual keyboard is not working and the touch screen is not response sometime.
LeoNg628 said:
but he said virtual keyboard is not working and the touch screen is not response sometime.
Click to expand...
Click to collapse
I use the word "test" loosely, I mean the archos 70 is the device I am testing the .img's I am compiling. I now can log in but the touch screen is still acting weird. You will be able to test it out in a few hours when the .img finished uploading.
This thread is pretty much dead so I suggest you check out my other developer thread, which is the one will be on mainly
http://forum.xda-developers.com/showthread.php?p=13243471#post13243471
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
The modifications made on Angström to make it work on Archos are all told on the Archos website, (on the same page where you download the SDE, the button under the "Download AOS" one)
Well... Yes and No
Angstrom is built using a system called OpenEmbedded (OE). OE works much like rootstock but is a little bit more advanced. It not only allows you to build a .img from a certain distro (in this case Angstrom) but also allows you to build for specific embedded devices. Right now though the newest Archos devices aren't located in the OE repo yet, so what's on the site that your seeing is actually an overlay that goes over what you download from OE that has the configs to tell OE how to built for the Archos Gen 8 architecture. It doesn't actually contain any changes to the scripts or files.
Very interesting guys, thanks a lot.
MysticMgcn said:
I know I should post this to the new thread in the Gen8 Android Development section, but I'm new to the forums and can't post there yet. We know the kernel is fine since we get the kernel and modules from Angstrom. The major issue I see is that Angstrom has some highly customized init.d and rc.* scripts, as well as a ton of udev and xmod files not found in kubuntu by default. The Angstrom xorg.conf doesn't even include this line:
"Option "Device" "/dev/input/by-id/usb-UNITEC_USB_Touch__Win7_-event-if00"
So I'm sure if we traverse through what's in the Angstrom rootfs.img we should find our answer to at least the touchscreen.
Try taking a look at the archos-init.sh script in the /etc folder of Angstrom.
Click to expand...
Click to collapse
Do you have any idea if I could build an ubuntu or kubuntu .img with openembedded and then apply archos's changes to that. I've been looking for some documentation but all I have found so far is documentation relating to angstrom.
While it should be possible, as you've seen documentation is lacking for OE and I've personally had a lot of issues with it just from trying to create my own stock Angstrom .img to see how it worked. Plus it just seems like a lot of work as you have to create BitBake (.bb) files for the programs you want to install, compared to using rootstock and just being able to call out the programs you want installed by default with the --seed switch.
I think we're really a lot closer than we realize to start from scratch with OE. We have the kernel and drivers in place as well as the filesystem, we just don't have a way to tell the system to load the drivers the way they need to be loaded through either udev or init.d/rc.d*.
Well the problem was with udev and I've gotten the mouse to work without the need for an xorg.conf. I'll post more when I can but I may scrap this as everyone lost interest. I'm building a new image from Natty instead of Maverick anyway where udev isn't so flaky.
Sent from my PC36100 using XDA Premium App
ive actually been waiting on a work img, the last one i used just gave me an error msg. i'm not afraid to test anything out.
shrewdlove said:
Here are some semi-complicated instruction for creating a bootable KDE mobile install on Archos gen 8 devices for self.
https://wiki.kubuntu.org/ARM/Archos101it
Click to expand...
Click to collapse
I tried the instructions listed there and they DO NOT WORK. Here's what I did step by step. When I boot the device into developer mode, I get the boodting developer editon screen, but never any hits of kubuntu.
Interestingly, if I try to restore a backed up copy of the Linux Angstrom img it won't boot that either. I have to go back and re-install the SDE to get it to boot in developer mode again.
Related
Here I am uploading android partition dumps, you can use these files to fix your bricked devices. These images were rooted stock dumps of Indian version, build number is 13040. Use fastboot method to flash these images.
Warning: Please use them only if your device was bricked.
boot.img
recovery.img
recovery_bak.img
system.img
All those dumps were created using "yaffs" tool.
Now download the attached files below, extract fastboot+adb file and extact its contents to "c:\tools\", such that adb.exe and other files will be in c:\tools\ folder.
Now extract and install the second file (venue drivers windows 7).
Now go to command prompt and switch to "c:\tools" directory (cd c:\tools).
Now enter the following commands at c:\tools\>,
c:\tools\>fastboot flash system system.img (this command flashes system.img to system partition).
simillarly.
c:\tools\>fastboot flash boot boot.img
c:\tools\>fastboot flash recovery recovery.img
syntax:
\>fastboot flash []
Hope this guide helps...
Please let me know if you are successful...
Please click on THANKS if you find it useful.
Thank you...
If you have no idea on how to flash those dumps please let me know. I can post step by step procedure on how to flash them if you need.
After checking the contents, I reupload the set to match the set I already have.
Can you confirm that these images are clean, unmodified dumps? The ones I already have come from brand new devices and this was the first thing done to them. (they were used slightly by normal users, but that wont affect it, they didnt touch anything in /system beyond rooting it to dump the partitions)
Edit: I have downloaded them and compared them to the dumps I already have, 304 is slightly modified but I'm pretty sure I was able to fix it back to likely what it shipped with.
Now I was out of my wifi coverage area, ill test them when I go home.
Sent from my Dell Venue using XDA App
I mean ill test your build when i go home.
Sent from my Dell Venue using XDA App
rapol.goutham said:
If you have no idea on how to flash those dumps please let me know. I can post step by step procedure on how to flash them if you need.
Click to expand...
Click to collapse
thanx!!!!!!!
rapol.goutham said:
Here I was uploading android partition dumps, you can use these files to fix your bricked devices. These images were rooted stock dumps of Indian version, build number is 13040. Use fastboot method to flash these images.
boot.img
recovery.img
recovery_bak.img
system.img
All those dumps were created using "yaffs" tool.
Click to expand...
Click to collapse
how do I do it?!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow the above guide. And those drivers works with Windows 7 only, if you need drivers for windows xp plz let me know, ill upload them later, because i was running my internet on slower connection.
Dont mean to sound ungrateful,
but you should use the cleaned copy I posted on here.
The dump you posted was strangely missing a couple files and still had the dump tools. I cleaned it up and reincluded files that were missing.
It's only a couple files and doesnt really change how it works. But I only host as close to original copies that I can. The cleaned one should be virtually identical to a fresh install.
Just as much I actively maintain the fastboot+adb.zip package. The file name doesnt change as it's merely a copy of the latest one. You can check the folder it's in and older revs are there.
Hey manii, as you told me before that you don't have Dell Venue but Dell Streak, then how could you tell that those dumps are were missing some files? Those are the dumps that I was currently running on my Venue, and I haven't experienced any problem till now.
And i can't guarantee that the files you feel that were missing from Dell Venue when compared with Dell Streak works on Dell Venue.
If you want to share this builld in your forums leave the dumps as it is and share them, so that no bugs will arise.
The venue s5 s7 are all built off the same codebase.
I have ~90% of every known rom for those 3 devices
Doing a diff on yours vs the others reveals that some files are missing, such as /system/etc/hosts.
This is one of the files that is universally existant. It's in every rom on all 3 devices. There's some more that are missing, and clearly shouldnt be. But I cant recall off the top of my head.
You can do a diff vs the filesystem of 307 and that reveals most of it. There is the highly unlikely event that it was missing at the source. It's always possible but for the example of hosts I dont believe it's this case.
None of the missing files will cause run issues, just merely missing. The majority are in app\ and i believe there was only 1 that isnt bundleware in that case (ie it's a stock android app) but I cant recall for the moment which one that was.
For the moment I am the most knowledgable person on the s5/s7/venue filesystem layout. Though not so much on what each specific file does (as I dont code dev, but it's not difficult to look it up on google for specific files).
One thing i can say is it's unlikely that 304 ever existed as an update.pkg as system/etc/install-recovery.sh is missing. If it's missing by default that is essentially the definition of this, unless you removed it yourself (which I dont believe is the case)
yes you are right, I have modified host file to remove adds in applications but the file exists and install recovery.sh file also existed and every thing works fine but try those dumps only in case of emergency.
can you try those images on your streak.? If it works fine plz let me know, then ill try streak roms on my Venue.
And install_recovery.sh was also modified to support 2nd partition on sdcard.
It should load fine with the SD kernel, it will run but it's not useful beyond deving.
If you try and load a venue rom on a streak, the screen will be upside down and wifi doesnt work. There might be more but I havnt done any extensive testing on it
How could you boot through sdcard.
Sent from my Dell Venue using XDA App
You cant, not until someone makes a new bootloader.
With the popularity of the venue this is likely to be never
how do connect the dell venue for the command prompt to see the phone
thanx!
nexio said:
how do connect the dell venue for the command prompt to see the phone
thanx!
Click to expand...
Click to collapse
go to this link and download ADB Easy, install then connect your phone
Please be post "step by step" how to do it. Thanks
I have already posted step by step guide, please read the thread completely, this thread includes how to flash guide also. If there were any doubts plz ask me.
Sent from my Dell Venue using XDA App
I try to run ubuntu on my machine.
I did root and unlocking the bootloader and superuser + busybox I try to start ubuntu after I installed everything according to instructions in this link: http://forum.xda-developers.com/showthread.php?t=962023
In "terminal monitor" that:
su <return>
cd / sdcard / external_sd / ubuntu <return>
sh ubuntu.sh <return>
He writes that he claims the UBUNTU but he just does not respond.
From what I gather I need to file "ubuntu.sh" fit to AMAZE
i am sorry about my English.
somebody know somthing? plz?
chai058 said:
somebody know somthing? plz?
Click to expand...
Click to collapse
Did you post your question in THAT thread?
get Linux Installer from the market.
after you study. then use it;
after a couple builds, you will have a better idea about why you couldn't get the ubuntu.sh to work.
Linux Installer and tutorials and (and I kid you not) GOOGLE is your best friend.
the above formula worked for me. after a couple months of research and trial and errors, I have a functional and built from scratch Natty build.
one more thing- aptitude is your friend -install it with apt-get first and switch to it from apt-get soonest.
I could talk for hours, but I would hazzard a guess, as pointed out in the post above, that others , in the very forum you linked, as well as others on this very site, that these others have already talked about this for hours and you have a vast array of knowledge at your fingertips, or is it mouse pointer, either way..good luck
really just meant to say that Linux Installer from the market worked for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tnx very match i hop is gonna work!
Daddyroot said:
get Linux Installer from the market.
after you study. then use it;
after a couple builds, you will have a better idea about why you couldn't get the ubuntu.sh to work.
Linux Installer and tutorials and (and I kid you not) GOOGLE is your best friend.
the above formula worked for me. after a couple months of research and trial and errors, I have a functional and built from scratch Natty build.
one more thing- aptitude is your friend -install it with apt-get first and switch to it from apt-get soonest.
I could talk for hours, but I would hazzard a guess, as pointed out in the post above, that others , in the very forum you linked, as well as others on this very site, that these others have already talked about this for hours and you have a vast array of knowledge at your fingertips, or is it mouse pointer, either way..good luck
really just meant to say that Linux Installer from the market worked for me.
Click to expand...
Click to collapse
So you got ubuntu installed on your Amaze 4g? I'm using the stock kernel and it doesn't look like it has loop device support. What Rom/Kernel are you using?
Yeah I was about to say, hold on a minute, when did someone get Ubuntu running on the Amaze? I must've missed that announcement. I mean I know they got it running on a select few other phones (like the N1), but never heard anything about it running on the Amaze.
Ok so I was just able to boot ubuntu successfully. I can confirm this works using Energy Rom with stock Kernel. The problem was I was trying to install from my external SDCard not the internal. Followed the instructions here: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Only issue I am having is with apt repo's but otherwise looks good!
Bling_Diggity said:
Yeah I was about to say, hold on a minute, when did someone get Ubuntu running on the Amaze? I must've missed that announcement. I mean I know they got it running on a select few other phones (like the N1), but never heard anything about it running on the Amaze.
Click to expand...
Click to collapse
Yea I am with you all this one I am calling BS. I would be nice to have it thought
Apt-get is more suited when installing a large amount of packages as it works out the depends faster. Otherwise Aptitude should be used. That's direct from experienced Debian developers.
Ruby running CM 1O - using XDA Developer app
I used the Ubuntu.sh method at first and for it working. Then I found out about the complete Linux installer app and have successfully ran Ubuntu 12.04, backtrack and debian.
Sent from my HTC Ruby using xda app-developers app
jared407 said:
Yea I am with you all this one I am calling BS. I would be nice to have it thought
Click to expand...
Click to collapse
There's an app that makes it easy to get ubuntu on Android. It's called Complete Linux Installer, search it up in the Play Store. It works for me. I actually used it so I could get hamachi running. It connects but doesn't work with it tries to connect with other devices
Sent from my HTC Ruby using xda app-developers app
Been a long time since I've done much with phones honestly. Looking for someone who can help me setup my netbook basically to purely be for Android development and hacking. Any and all help would be appreciated, mostly looking to update to ICS and see what its all about.
Thanks to everyone
Cheers
d0ppler302 said:
Been a long time since I've done much with phones honestly. Looking for someone who can help me setup my netbook basically to purely be for Android development and hacking. Any and all help would be appreciated, mostly looking to update to ICS and see what its all about.
Thanks to everyone
Cheers
Click to expand...
Click to collapse
1. AndroidSDK
2. Java
3. APKTool
4. Virtuos ten Studio
5. photoshop
6. Winrar & 7zip.. and probably more but nun come to mind... oh and a folder called "workdir" or whatever name you want to create flashable zips with --> http://forum.xda-developers.com/showthread.php?t=732957 <--
funnyangrykid said:
1. AndroidSDK
2. Java
3. APKTool
4. Virtuos ten Studio
5. photoshop
6. Winrar & 7zip.. and probably more but nun come to mind... oh and a folder called "workdir" or whatever name you want to create flashable zips with --> http://forum.xda-developers.com/showthread.php?t=732957 <--
Click to expand...
Click to collapse
thank you. also if you happen to be local I'd like someone who would be able to meet somewhere possibly and walk me through some of the basic things to get me moving along. Like I said its been a long time since I've even flashed a ROM onto a phone and with this Rezound and all the ICS needing special procedures to install kernels and everything I'm completely lost. So I'm still stuck on 2.3.4. I bought the phone from a guy I used to work with and he used to be helpful but since he got tired of trying to keep up with it all and that was the reason for selling it to me he couldn't teach it. He deleted every single file from his computer related to Android and removed it all from his Pulse account and any other news feed like Google Reader and such. That's my whole predicament
d0ppler302 said:
thank you. also if you happen to be local I'd like someone who would be able to meet somewhere possibly and walk me through some of the basic things to get me moving along. Like I said its been a long time since I've even flashed a ROM onto a phone and with this Rezound and all the ICS needing special procedures to install kernels and everything I'm completely lost. So I'm still stuck on 2.3.4. I bought the phone from a guy I used to work with and he used to be helpful but since he got tired of trying to keep up with it all and that was the reason for selling it to me he couldn't teach it. He deleted every single file from his computer related to Android and removed it all from his Pulse account and any other news feed like Google Reader and such. That's my whole predicament
Click to expand...
Click to collapse
Everything is all pretty simple and easy on this phone. they say its a hard phone to brick.. but honestly, im nowhere NEAR on knowing how to fully build a rom (Im still learning) but flashing them on thee other hand i know well..if you are located in texas im sure we could work something out. i am currently 21 yrs old so dont let my username fool you lol.
Do I need S-Off to go up to ICS and what does it mean to install kernels in HBoot and all that mess? Like I try to read all the things the developers say but I want to learn the basic way to do things, not the "download my toolkit and it does it all for you"
First, get rid of windows. Throw the disc in a fire, or destroy it somehow.
You need linux, Ubuntu is the most user friendly.
Also, I wouldn't use a netbook for development. You need a powerful CPU and most netbooks cant do much. Most netbooks come with windows starter because they can't handle the Aero UI.
But, I move on. Android SDK, java, and some more stuff in an earlier post is what you need. Also, set up a virtual device in Eclipse to make apps easier to test without having to download to phone.
But, eclipse has this handy feature that you can enable USB debugging and connect to your computer. When you finish a build of an app, you press the button at the top and the app automatically compiles and goes to your phone. You can go from editing and building to testing on the actual device in 5 seconds with one button click. It is awesome.
d0ppler302 said:
Do I need S-Off to go up to ICS and what does it mean to install kernels in HBoot and all that mess? Like I try to read all the things the developers say but I want to learn the basic way to do things, not the "download my toolkit and it does it all for you"
Click to expand...
Click to collapse
K.. first off.. you can upgrade to ICS from GB if you're S-on.. but if you're S-on, you can't downgrade I.e: (S-on example) if you're on V2.11.605.10, you can upgrade to a version higher than that like v3.14.605.10.. but once and if you upgrade to v3.14, you can't go back to ANY version below it.... If you're S-off, you could.
Sent from my Incredible, very Vivid, One X'strordinary S-off HTC Rezound
http://www.speedtest.net/android/216418366.png
GrayTheWolf said:
First, get rid of windows. Throw the disc in a fire, or destroy it somehow.
Click to expand...
Click to collapse
Or you can just dual-boot .
carngeX said:
Or you can just dual-boot .
Click to expand...
Click to collapse
or triple boot.
got that Windows 7 as my primary c
windows8 and Ubuntu as my secondary...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
funnyangrykid said:
or triple boot.
got that Windows 7 as my primary c
windows8 and Ubuntu as my secondary...
Click to expand...
Click to collapse
I'm quad-booting on my laptop, technically. Two drives, 2 OS's each. Win7 + Ubuntu, Win7 (alternate install) + Backtrack 5 R2.
carngeX said:
I'm quad-booting on my laptop, technically. Two drives, 2 OS's each. Win7 + Ubuntu, Win7 (alternate install) + Backtrack 5 R2.
Click to expand...
Click to collapse
awww MAAAAN!,, i was gonna try and replace windows 8 with backtrack but i couldnt FOR THE LIFE of me get it installed lol.. any tips?
Hi Folks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you may or may not be aware, I have been working on get CWM Recovery working on the Gen9's and basically make the layout of the Filesystems etc reflect some sort of Android Standard, In SDE mode at least. This is coming along nicely and I should be ready to kick out a Early Beta in the Next Couple of Weeks.
I would like to gather some input on any additional options people who like to see in CWM, Basically CWM Recovery Comes with a standard set of features but they maybe options that you have found useful on Device's you have had in the past etc.
I already plan to make it possible to boot into all modes on the device, that Archos Recovery, Archos Android, SDE Android and SDE CWM Recovery.
So Yeah, Give me Ideas and I'll seen If I can accomadate them
NOTE: Obviously We are just getting started on this and alternative recoveries will come in time, TWRP for example but one thing at a time eh :good:
Okay, Here's a currently "wishlist" of feature I think would be quite useful
Archos Specific Features
Include Stock Repair and Recovery Options
Include Stock Developer Edition Options
Reboot to Stock Recovery Option as a Fail Safe.
Reboot Stock Android
Flash Archos aos update
Upgrade Existing SDE Images to new structure
An the list goes on.....
Print system Properties
Print dmesg
Resize Partitions
Manage FS Image Location ( mainly nice to have on HDD Version I suppose )
Backup to Sparse Image ( I'm sure CWM5 Nandroid did this with ext4 partitions, god knows why they changed to a default choice between tar archives or dup differential blobs, What If I just a single portable file for my data partition backup!! )
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Power Off ( Suprisingly not include by default )
Full Touch Support with on screen keyboard and command line
I think those features will do nicely but If anyone has anymore then get involved!
The nandroid backup interests me a lot... its always nice to be able to "return" to when it was working if anything breaks.
Im watching this thread with interest good luck!!
TrOjAn
Maybe an ability to mount the whole system through usb? So one could DD clone the whole memory chip to PC. That could recover some bricks.
trevd said:
Resize Partitions
Click to expand...
Click to collapse
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
trevd said:
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Click to expand...
Click to collapse
But fastboot works on the bootloader level
gen_scheisskopf said:
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
But fastboot works on the bootloader level
Click to expand...
Click to collapse
Hi There,
I think, You've got your wires crossed None of this is related to letama CWM Recovery./ If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
I well aware of how fastboot works but to supporting the fastboot protovol allows the same workflow when it come to work with the AOSP source as any over device. which is
Build Rom
Flash the Partitions with fastboot
Reboot Into Rom.
???
Profit
When you control both ends of the conversation, We are free to do as we please.
Any news ... are there any files to do some testing?
shalkam said:
Any news ... are there any files to do some testing?
Click to expand...
Click to collapse
Would you mind reading... ???
trevd said:
If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
Click to expand...
Click to collapse
Follow the link and you are there.
Regards,
scholbert
Flash splash screen?
Swiped from my Galaxy Nexus using Tapatalk 2
Hello, first of all please do apologize for my English (i´m portuguese) , and an actual yogabook android version user.
We (the android users ) are having some hard times trying to boot windows on our tablet (it makes sense because it´s the same machine) therefore, what we need right now, is for someone who could acess his bios (there´s a thread here explainning the process, its actually quite simple) and, tell us how the windows bios is configurated, to allow us do a "copy/paste" of the configuration.
would you guys be so kind and help us out? :crying:
joao1979 said:
Hello, first of all please do apologize for my English (i´m portuguese) , and an actual yogabook android version user.
We (the android users ) are having some hard times trying to boot windows on our tablet (it makes sense because it´s the same machine) therefore, what we need right now, is for someone who could acess his bios (there´s a thread here explainning the process, its actually quite simple) and, tell us how the windows bios is configurated, to allow us do a "copy/paste" of the configuration.
would you guys be so kind and help us out? :crying:
Click to expand...
Click to collapse
I think its a very different bios on the windows version. Probably accessible upon keypress on boot but very different from android one.
Sent from my Nexus 6P using Tapatalk
i really hope you´re wrong lol let´s wait and see if anyone could help us out with this, because i can´t belive tha same hardware can only boot one OS
Dont think it's accessible on Keypress. That hasn't been a thing since Win7, I believe. Exactly what settings are you looking for? I could probably just share some pictures of mine, if thats easier.
sawyerbenjamin said:
Dont think it's accessible on Keypress. That hasn't been a thing since Win7, I believe. Exactly what settings are you looking for? I could probably just share some pictures of mine, if thats easier.
Click to expand...
Click to collapse
thank you for the reply, what we need is to see wich are the options on windows bios that are enabled, to try to boot a windows on our tablet, i belive if you try accessing the bios trough the steps that are on this forum it´s the easiest way. would you be so kind and show us how your bios is ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hopefully that shows up.
sawyerbenjamin said:
Hopefully that shows up.
Click to expand...
Click to collapse
Many thanks !
I just checked with mine, the bios is just completely different !
Do you have an option with ACPI enabled or disabled ?
That's what most of android users have after booting windows 10 on usb key.
Sent from my ONEPLUS A3003 using XDA Labs
Sweetgeex said:
Do you have an option with ACPI enabled or disabled ?
Click to expand...
Click to collapse
ACPI is branded in the bios and on by default as Windows has it under control.
Power, Device, Processor-States etc... all handled by Windows and not like older (very old) bios which had APM
That's why you need another bios if you ever want to dualboot.
I'm pretty sure you can download the BIOS from Lenovo. I couldnt help you install it from Android though. Seems like a very easy way to a bricked device.
sawyerbenjamin said:
I'm pretty sure you can download the BIOS from Lenovo. I couldnt help you install it from Android though. Seems like a very easy way to a bricked device.
Click to expand...
Click to collapse
Well... There is a tool from lenovo site, but it seems to update only if you already have windows 10 (exe file).
Vicious circle !
Sent from my ONEPLUS A3003 using XDA Labs
sawyerbenjamin said:
Seems like a very easy way to a bricked device.
Click to expand...
Click to collapse
You got it. Quite easy to brick it.
I am pretty sure Lenovo burned the BIOS in an EEPROM. Differently between Windows and Android models. Updates are just flashed in a CMOS, well rather NVRAM nowdays. That's why Windows and Android models have completely different approaches when it comes to update the BIOS. I doubt there will ever be a way to flash (supposed) "Windows" settings into a "Android" device, as the EEPROM was initially fixed differently, expecting specific store instructions for the NVRAM depending the OS model.