Related
Hi everyone!
Got this Miphone A3 yesterday, and I been searching like a fool after information about this damn phone but it ain't a easy thing to find.
But hey, what do you expect from a cloned iphone
So here's my question:
Anyone sitting on a Miphone and have you done anything with it, most imporant for everything, ROOTED?
Phone info on the phone:
Model number:
A8
Where I bought it, it said A3 on the site (mobino1), same on the battery.
But instead of the iPhone Ui it has the Android Ui pretty sweet that it didnt have the iPhone Ui.
Firmware:
1.5
Don't have Android Market app, but everything looks like Android, also works to install . apk apps tried to install apps from 1.6+ but doesn't work.
Kernel:
2.6.25
Build number:
Linkworld Project .0002_A.1_01r_100129
Been looking for that build number for a while now, don't have any info at all on that one.
Hope some1 here has some info, would be a blessing for me!
EDIT:
I found my way into what i think is the recovery mode, came up a where is said enter flash mode put in usb cable, with red background. Then when i did that, the screen turn blue saying "Enter Flash mode, Begin to flash image..."
Been reading a lot, and i never came up with that kind of "bootloader" just saying that
hope some1 could give me some tips
hi, one of the stores provided firmware from A3, I do not know how fresh. ussd queries are unsuccessful, after ussd calls to hang up. In flash mode turns pressing the upper side volume buttons and switch.
depositfilescom/files/0po3pwcu6 - miphone A3 rom
thanks for that one!
flashed my phone, worked! but it wasnt the same version. this one was with the iphone ui (using ahome)
Model number:
A3
Build number: A3 Project.0001_18r_100411
Seems like my 3G connection does not work with this version. ussd, unsuccessful on this version too, same with previous version.
I was wondering, tried to open the one.bin (flash image) but cannot extract it. Any way to extract the image and try to reconfigure the build?
the phone using "tavor platform" flashing software, anyone know anything about tavor platform?
still trying 2 modify the rom I have, no luck so far.
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
xift said:
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
Click to expand...
Click to collapse
I been trying to extract the .bin file MagicIso can read the file using it "missing files" but can't read the files when extracted. Trying to find a program that could read the rom file, have you done anything to update the phone? Do you have a rom file, if so could you upload it pls?
tried to get the firmware from mobino1 but they just ignore mig those bastards.
Ernest25
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
Click to expand...
Click to collapse
Do you want to flash your phone with the .bin file you already have or do you want to know how to update the phone to android 1.6+?
To flash your phone with tavor flashing software, you need to run the flash program in XP and press "volume up" and "power" on the phone to get to flash mode, then plug in the usb with the flash program open, and it automatically flash the phone.
About updating the phone to a newer version of android I have not a solution.
I been trying to, get info on the hardware so I could try to cook a own rom with at least android 2.0
Cheers
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
xift said:
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
Click to expand...
Click to collapse
Ernest25 said:
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
Click to expand...
Click to collapse
If they just told me straight up, we just sell the phone, we don't have any contact what so ever with the manufacture or developers I would accept it. But this just pissed me off.
I've been asking around on other sites that sells the phone, waiting on answers from them. Hopefully they are more friendly.
Don't downgrade, that was a mistake for me (the rom file azat182 nicely posted).
I tried something yesterday, made a own .bin file with android 2.1 but the flash program wouldn't start with it (parse ini error) so I tricked the flash program that it would flash the one.bin (azat182) rom file.
After it opened I replaced the .bin file with mine. Everything seems to work fine, did every step it should like, root system etc finished 100% when I tried to turn the phone on I couldn't, maybe it didn't know were the power "button" source came from.
The android source was made for an other phone, so I wasn't surprised.
Plugged the usb back in, and luckily the phone connected somehow with the computer so I flash it with the (azat182) rom and I'm back at square -1
but now I think, if I could find out the hardware/drivers on this damn phone it would work to cook a own rom using that method.
Cheers
Oh hey, someone else with one of these phones. I've been messing with mine for a while, started out with the A8 rom (from fastcardtech), and have flashed the A3 rom to the device. I've noticed that the gps works a lot better in the A3 rom than the A8, so it's not much of a downgrade, imo. Recently I've made some headway with an android 2.1 port to the device.
Anyway, this device isn't hard to root. If you adb into it, you can get root from the device by remounting /system as RW and pushing a fixed su binary to /system/bin, or wherever it goes, it's been a while
The MTD partitioning in the Miphone's rom is a big giant mess. The rom is split into 25 partitions, the kernel isn't in boot.img like it's supposed to be, neither are the kernel parameters.
The bootloader is dumb, it doesn't check for signed images. The A3 image and A8 image are both engineering builds.
wow you seem to know a lot about it...
does 3g work for you in the a3 rom? also gps doesn't work for me in a8... so a3 could be a possibility if 3g worked.
how did you adb your phone? I could not connect... the driver just didn't show a phone. although I changed the vendor ids etc...
could you write a short tutorial of some sort? would be nice!
if you are root, couldn't you make a backup of your firmware?
is there a downloadable a8 rom at fastcardtech?
regards, xift
I haven't been able to get 3g working, just edge. I don't think the 3g will work in the US, as none of the carriers will work with just wcdma2100, but I'm no expert on the subject. I've had reasonably good luck with the gps with an app called Maverick, but I don't have a data plan currently, so no agps. With gps alone, it takes about a minute or so in an open area to acquire a lock.
For ADB, there's a driver in the android sdk, but don't bother with it. Instead, the phone's going to show up as a rndis/ethernet gadget. For windows, drivers for this can be found at webos-internals.org/wiki/USBnet_networking_setup, just the .inf is all you'll need; MacOS and Linux will just see the ethernet gadget. Once that's installed, the phone will show up on the PC side as a network interface that will need an IP address; I've been using 169.254.231.10 and subnet 255.255.255.0. Once your network interface is configured, you should be able to run adb connect 169.254.231.168:5555, assuming you've got your android sdk tool set up already. From there, you can adb shell in and poke around. Once you get an adb shell, you'll have a root prompt, but to get 'rooted' so that other android apps can make use of it, you'll want to run adb remount to remount /system as RW, then copy a working version of su over to the phone. I think superuser whitelist comes with one.
I don't usually go to that much trouble, as I end up cycling between the A3 firmware and my Eclair build a lot, and the A3 rom is jacked up to where it's a pain to get a terminal emulator running on it. Adb from my desktop seems to get the most mileage.
Fastcardtech didn't have any useful information about recovery firmware that they had, a release date for an android 2.1 rom, information on the manufacturer, anything.
Wow thanks a lot... I tried with the sdk driver.
port 5555 seemed blocked there although it was obviously responding (took much longer than other ports). Thanks for your help - I'll try that one.
Could you upload your eclaire build?
I don't have much time at the moment because of my bachelor's thesis. But I'd like to see that and maybe I could help a bit. Although I do not have any experience with mobile devices etc.
You may need to mess with the usb debugging option. After flashing to the a3 rom, it's enabled. I remember it being the same between the a8 and a3 roms.
At some point, yeah, I'll my eclair build up. I'd like to at least get bluetooth, gsm and wifi going again before I do. I don't have a rom that you'd be able to flash currently; more like a big pile of build scripts, and install scripts for the android system and ramdisk.
yeah I understand that. You could open a google code project or something.
nice to know that there is somebody working on this.
usb debugging is enabled by default. I'll just have to try again.
thanks for your help so far.
file inf
I not have disk only cd and dvd when I will install the drive without the disk says no drive found I save the file as usbnet-pre.inf
if anyone can help me pls
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
xift said:
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
Click to expand...
Click to collapse
linux complicated for me but thank you I hope good news from you about how root this bastard mobile
I have the A3 if you're interested I can pass to you
As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance
EDIT: Found it - I was looking at BT 5 R1 instead of just version 5, which has a release for 'arm'. Inside, there is a magical README file... finally!
-----
I apologize in advance for the rookie question but: I'm trying to follow the simple instructions from this link: http://forum.xda-developers.com/showthread.php?t=1074723 in order to install BT5 on my rooted Xoom. However, I'm stuck at two very basic steps:
- Backtrack 5 for ARM with Gnome downloaded and setup (check the README file, and follow the instructions.)
Click to expand...
Click to collapse
From the given link (http://www.backtrack-linux.org/downloads/) you are presented with 2 versions for the GNOME flavor: ISO and VM - which one is the correct one?
Also, where exactly is this elusive README file that should tell me how to set everything up?? I don't see anything on the BT website to do specifically with the XOOM and the downloaded files (ISO or VM image) don't have any README file to go with them either...
Such simple thing... I'm sure it's just staring me in the face but it's driving me crazy! Thanks in advance...
I just bought my first tablet. An acer Iconia a1 830. rooted it the first day, got some chroot linuxes going, ssh into some other boxes. awesome.
so my googles have come up short looking for people who are running (or trying to run) x86 linux on x86 tablets. Ive been building and breaking linux for about ten years now and i think i could help this effort. everything i have found is for arm ports and stuff. I know i am not the only one who is looking at his x86 tablet wondering how to get some dual boot action out of this.
send me a link to the place i need to go, to find the people who are thinking about this.
acer iconia a1 830
htc desire hd running some cyanogenmod
danharris said:
I just bought my first tablet. An acer Iconia a1 830. rooted it the first day, got some chroot linuxes going, ssh into some other boxes. awesome.
so my googles have come up short looking for people who are running (or trying to run) x86 linux on x86 tablets. Ive been building and breaking linux for about ten years now and i think i could help this effort. everything i have found is for arm ports and stuff. I know i am not the only one who is looking at his x86 tablet wondering how to get some dual boot action out of this.
send me a link to the place i need to go, to find the people who are thinking about this.
acer iconia a1 830
htc desire hd running some cyanogenmod
Click to expand...
Click to collapse
Hi,
I have an 830 and a Razr i, I've tried to get chroot running on both when I first got each of them, but didn't finish the things. I'm pretty sure if I gave it a few more hours I'd be able to get it running, but as of now no luck.
I will tell you the progress I made though.
You've probably heard of linux on android or complete linux installer http://linuxonandroid.org/, and I'm sure you worked out pretty quickly the version of busybox they gave you, along with the images, where for arm.
It might pay to message, but let's be honest, in this case WE are the developers, and unless one of us is willing to send them one of our devices we'll have a hole lot more luck trying it ourselves.
Busybox x https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en can install an x86 binary, and it certainly runs, but I had some issues that may be related to how it was compiled, or just me being an idiot.
You say you've been playing with linux for 10 years, so I know you probably already know this, but just in case, and for others reading this, it's probably worth explaining. chroot isn't a VM nor is it a system for traditional duel booting. It will allow you to run a linux userland from the already running linux kernal on the device, alongside android. It works by specifying a directory or image with a linux install in it, then telling the kernal to start that **** up, as if it where the kernal in the instalation.
Now, onto my progress. I was able to run chroot, so it was obviously an x86 binary, I was also able to mount an image of an x86 debian install made with debootstrap (What linux on android uses to make their ARM images) on my SD card. The first problem I had was android doesn't give stuff on the SD card execute permissions, and stuff got messy, but I eventually got that working. Do as you see fit.
I had numerous other issues, but the one I finally got stuck on was chroot not being able to find /bin/bash in the debian install directory.
I played around with the boot scripts you get with linux on android, but I don't think chroot evern ever ran from there. Neither was I able to run a plain "chroot /mnt/debianimagemounted/", I kept getting the "can't find bash" thing. I'm guessing this could have been because the linux for android scrypts made aliases before running chroot. Read them for yourself to see what I mean.
This all could be as simple as redirecting the linuxonandroid program from the arm version of chroot it uses to an x86 copy, or it could be more difficult.
Actually, I'll email them now, I'll post any response I get here.
I don't think there really are many people talking about this, I mean your post was the first google hit for "x86 android chroot", so this is probably gonna take some effort on our part.
I'm pretty busy with study right now, but in 2 weeks or so I'll dedicate a few solid days to getting this running.
As far as I can tell all we need is some good hard trial and error.
Can't wait to hear from you.
One other thing, I forget where but heard that you should try to stick to i386 binaries only, and that i686 ect could cause problems, but I don't know this for sure. Again, use your own discretion.
---------- Post added at 05:12 AM ---------- Previous post was at 04:15 AM ----------
Sorry, last time I post, but I found this, you might want to check it out:
http://sven-ola.dyndns.org/repo/debian-kit-en.html
Yup, from what I've found, Debian-kit seems like the most promising project. Heres a link with a little more insight.
wdowiak.me/debian-kit/index.html
For anyone else who gets here... this is what I used to root the 830
androidfilehost.com/?fid=23578570567714700
then I got Debian-kit from fdroid because it has a newer version, but the one from google play works fine too. get your connect bot and RDP client and ur off to the races.
***sorry for the non linked links, Im not allowed to post real links yet
Dan, I think wdowiaks kit in your link is newer than the fdroid version and installs Wheezy. It definitely has good install info. I rooted my new a1-830 yesterday and installed the wdowiak version in the initial install version (not the one on the external sdcard). I had a little problem with the Iconia not mounting the external card formatted to two ext2 partitions, so the install was to internal memory aas a first try.
But today I removed the deb installation and reformatted the external card to 3 partitions with vfat on the first, and ext2 on the other two, and Android mounted the first partition where the deb script was located. So I'm hoping to install tonight. I was surprised the ext2s werent mounted automatically. But this might be a gtood thing, since there are warnngs not to let Android apps write data to them anyway.
Anyway, wanted to thank you for the above Debian info.:good:
Some notes as I'm installing the wdowiak debian-kit-1-6.shar:
I'm installing to the third partition on the sdcard (which shows up as /dev/block/vold/179:53)
At first I had trouble using the command:
mk-debian -i /dev/block/vold/179:53
I had to issue it as:
/data/local/deb/mk-debian -i /dev/block/vold/179:53
but even then it threw an error saying it couldn't fdisk 179:48 .
That seemed odd. But it didn't stop there and went on to query if I wanted to format 179:53 or " (A)bort " I decided to go ahead and typed a "Y" and was brought back to a prompt.
That didn't seem to work, so I tried again by just hitting <ENTER> . But that had the same result. Finally I figured out that the response it wanted to proceed was lowercase "e". That worked and the partition was formatted -- the install is going on now.
One other note -- though I originally partitioned as ext 2, the mk-debian command seems to be re-formatting to ext 3. There is a suggestion earlier that if it is to be a journaling format, rather than ext2, to turn journaling off. This reduces the number of writes and therefore extends the life of the sdcard.
---------- Post added at 10:52 PM ---------- Previous post was at 10:05 PM ----------
More notes:
I got a lot of error messages from debconf about needing a certain screen size during:
apt-get install andromize
Nevertheless it proceeded through. I'm now at the stage in connectbot where Ive logged into my user through ssh and am adding the lxde desktop via
apt-get install andromize-lxde
That's a pretty big chunk of realestate for a desktop -- almost a gig unpacked -- I'm used to Puppy Linux which is about 100 megs total for everything, including OS, desktop, and a full suite of apps!
I'm hoping that with some experience w/Wheezy on the a1-830 I can try getting an Intel Atom optimized version of Puppy linux on board.
danharris said:
so my googles have come up short looking for people who are running (or trying to run) x86 linux on x86 tablets...send me a link to the place i need to go, to find the people who are thinking about this.
Click to expand...
Click to collapse
Hi...I don't know much about this at all to be honest, but its an interesting thread and I found some links which will hopefully help you a little bit, though you may already be aware of them:
http://www.android-x86.org/
http://www.in.techradar.com/news/so...stros-to-choose-from/articleshow/38781789.cms
https://community.kde.org/Plasma/Active
All the best!
Thanks ishaang.
The middle link was pretty interesting, though I wish they had elaborated on their installation method:
We're fairly sure you don't need to be told how to install a Linux distro - most now use an identifiable and easy-to-navigate installer - but we thought it would be interesting to see how well they coped, first as a live image, via a bootable USB, then secondly as a fully installed OS.
Click to expand...
Click to collapse
My own interest is in Puppy Linux, which is generally accomplished from an ISO live CD session running in memory (on most computers). You run the CD then install to HD or USB stick.
For a so-called "frugal install" (the kind I use) there's another option besides making and running the LiveCD, You can just extract three files from the ISO, place them in a folder on the HD and point a stanza of GRUB's menu.lst to them. Typically the files are:
initrd.gz
vmlinuz
puppyversion.sfs
and an example GRUB menu.lst boot stanza for the Racy 5.5 version of Linux located on sda5 of a hard drive would look like this:
title Racy 5.5
kernel (hd0,4)/Racy55/vmlinuz PDEV1=sda5 ro
initrd (hd0,4)/Racy55/initrd.gz
boot
So I'm wondering how this translates to an alternative OS boot on the Iconia tablet? -- I could easily put those three files on an external sdcard, but how do we point the boot process to it on the a1-830?
Any update to this since 2014, I know i'm resurrecting a old thread. Hoping to breath new life into an x86 android 4.2 device.
Hi all I am using the Google Pixel 2XL and it is rooted running the Stock ROM. I tried for a while to get Kali Nethunter on my device with no luck until I found this video (which is old, 2017) and made a little change. I downloaded the latest version of kaliNethunter.apk (which I have attached) and placed it in the folder: Nethunter/data/app.
So, once you follow the instructions in the video, right at 2:40 into the video you'll receive instructions to start installing apk files. The first will be the KaliNethunter apk. Instead of installing THE VERSION THAT CAME WITH THE ZIP FILE you need to replace it with the apk I provided here which is the latest version 2019.1. This will most likely save you a major headache as I wasn't able to get terminal to load kali Shell at all until I switched this out.
Hope I've helped!
https://www.youtube.com/watch?v=vKRJ85LvGiI thanks to Tech-X for making this video!
Mine
Is this Kernel also function for Nethunter files from Magsik?
Interesting...