Android on the HD2 - is it just run from the microSD card or an actual "ROM" ?
I'm not new to ROMs (been mucking around with cell phones and PocketPCs for many many years now) but I'm a bit confused about the Android situation with respect to the HD2 (just found one, literally found one, and if I can get it functional I'm keeping it).
I see all these "ROMs" here and I have to ask the question:
Are they actually ROMs that I'd be using to replace the Windows Mobile stock factory ROM, or all these just "ROMs" that exist in a folder on the microSD card and I simply run some executable that fires up Android as though it were just another application running on top of Windows Mobile?
Trying to make the question simple so I hope that's enough. Wasn't sure exactly where to put it so Q&A seemed the best choice.
Thanks for any information anyone can provide.
br0adband said:
...Are they actually ROMs that I'd be using to replace the Windows Mobile stock factory ROM, or all these just "ROMs" that exist in a folder on the microSD card and I simply run some executable that fires up Android as though it were just another application running on top of Windows Mobile?...
Click to expand...
Click to collapse
the latter...you fire up haret which shuts down windows and loads android. android does not / cannot (for the time being) exist without windows. if you remove the sd card, android ceases to exist on your phone; windows cannot be removed.
hope that answers your question.
Ok, so when you say that one app "shuts down windows" does that mean that Android fires up and is in complete control of the device as though it had actually booted off it directly from ROM, or is it running as an application on top of Windows Mobile, that's where I get confused.
I saw a reference that some Android builds on the HD2 actually run faster or at least they benchmark higher than a real Android device like the Nexus One. I find that tough to believe but hey, if the HD2 can do it, awesome...
br0adband said:
Ok, so when you say that one app "shuts down windows" does that mean that Android fires up and is in complete control of the device as though it had actually booted off it directly from ROM, or is it running as an application on top of Windows Mobile, that's where I get confused.
I saw a reference that some Android builds on the HD2 actually run faster or at least they benchmark higher than a real Android device like the Nexus One. I find that tough to believe but hey, if the HD2 can do it, awesome...
Click to expand...
Click to collapse
my understanding is it shuts windows down - it is not running as an app on top of windows, though uses the hardware to fire android. when android runs it is in control of the device. you cannot have windows and android running at the same time.
"But Maaaaaaa" (ala Eric Cartman, South Park)
Ok, so we can only run Android from the SD card. But this begs the question....WHY? What is it about the HD2 that precludes the ability to remove Winjunk altogether?
To be able to run android directly from ROM, Android needs to use NAND.
AFAIK NAND is available, but noone knows how to use it directly.
Developpers are busy trying [thread], but until now without success, however signs are it is nearly completed.
As far as I understand, NAND preloads some drivers needed for Android. (like CLRCAD which is needed for sound)
Someone knows answer to folowing:
If NAND is possible/available, will booting Android be faster? Will the "Linux boot output" disappear or not.
Until now I think Android is booting (very) slow, partially due to the "Linux boot output" (scrolling lines)
Hi everyone
I have the following tablet made by Mach Speed Technologies:
Trio Stealth G2 7" display
1GB RAM
CPU: Dual Cortex-A9 Dual 1.5GHz Multi-Core (its a dual core with a total of 1.5GHz)
its not rooted yet, I don't know how. If it needs to be rooted for this can someone quick explain that?
It came with Android 4.0 and has never updated through the settings, and the factories website does not even mention this tablet. The guy at Radioshack said I could install the update myself so here I am trying to figure out how.
If possible my original plan was to just instal the newest Android release. But today I just found out about ROM's.
So how do I install the newest Android release or if that's not possible a very secure custom ROM?
On one website it just said to put the rom image on a sd card (or in my case a microsd card) and put it in the tablet, then the tablet would use it as an update after asking you with a pop up. Is that true?
I have a bit of experience with Linux and coding but none with Android
with that update through sd card is true but most of times you need to have specific app or recovery as it may be treated as a rom and in that case you need to be rooted and have recovery. if you have experience u good with android as it is based on unix core
Well, I guess the first step is to be rooted then? How do I go about doing that?
I have the "Root with Restore by Bin4ry" downloaded on my computer and the usb driver installed from the google sdk manager.
But my computer does not see my tablet at all.
I have the same tab I have got adb to somewhat pick it up an it has aml flashtool and safe mode this shows u how to get into all those all but for safe mode copy this an past after youtube.com
/watch?v=TVQS9s3UqRg&feature=plcp
Sent from my G2 using xda premium
Hi,
I wonder if someone can help.
I have a Pioneer Dreambook, i dont know the model number. It is similar in appearance to the Dreambook F10 but has different specs and hard buttons.
If you need the specs i can give them to you, but it currently runs windows 7.
I have been able install android on to it using andoid - x86, and tried multiple versions of the x86s, but all seem to unstable, the OS doen't control the hardware buttons correctly and doesn't rotate the screen unless an app forces it to rotate. Also I cannot put the tablet into "sleep" mode, only use a software option to turn the device off.
Once the device is off it is virtually impossible to restart the device and load android without using the x86 debugger.
I have seen on the web that devices like the hp tablet running web os is possible it install android effectively and that it is possible to install android onto a windows device, but surely there must be a better solution than what i currently have.
I tried to install Cyanogen but the windows installer wouldn't detect the tablet, presumably because it is not a support device, but i did read that it is possible to install Cyanogen on an non supported device.
If there is anymore information i can give please let me know, and any help or advice you can give me would be greatly appreciated.
Thanks,
Sam
Hi guys,
After reading very helpful post about how to write good posts/questions I realise that my issue maybe too specific.
I understand that with android the os needs to have some sort of tailoring to different devices.
But there are examples out there of similar applications of android on non android devices.
As I said earlier I already have installed android using android x86.
Let me then rephrase my question...
The issues described earlier, are they a result of the x86 method of installing android or are they the device simply incompatible with android (which I find hard to believe)?
Thank you to all the people who took the time to read my post and once again, any help would be invaluable.
Thanks,
Sam
Sent from my HTC_0P6B6 using XDA Free mobile app
Q&A for Intel Android Devices Root / Temp CWM Session
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Intel Android Devices Root / Temp CWM Session. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will this root method work with ASUS devices?
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
usenametaken said:
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
Click to expand...
Click to collapse
It should work I've tested it on Medfield, Clovertrail, and Baytrail devices, from the Asus fastboot.imgs I've looked at trigger 2 and 3 should work.
the apk you refer to i believe actually uses a function Asus only seems to of built into thier droidboot binary on the Asus when you start droidboot it looks at /factory for a file called .addon and then triggers it Asus uses it for automating things under droidboot I believe and several recoverys have been built to take advantage of it.
As for the exploit the exploit is the the script the binarys are nothing really special just responsible for setting up and starting the recovery session. recovery.trigger is a simple daemon to launch recovery.launcher and recovery.launcher is basically a small subset of cwm recovery its self.
Sent from my XT907 using XDA Free mobile app
Hi,
this worked on an odys intellitab 7, now i got finnaly root . BIG THX!
Btw I trird trigger 2 and 3 and both worked for me
How can i see if the bootloader is locked on my device?
Another possible device
Hello,
in Czech forum where I compiled a native-language short guide how to use your tethered CWM recovery to root Op3n Dott (I see that somebody confirmed that both T2 and T3 triggers work] one Slovak user reported that he was able to use the tool to root Prestigio MultiPad Thunder 7.0i http://www.prestigio.sk/catalogue/M...NDER_7.0i#/product-specs?article=PMT3377_WI_C. I sent him a question concerning which trigger did he use so if he replies I will send more info. Sorry for the Q&A thread, but I got kicked here because of the low post count.
Succesfully rooted Tesla L7 Tablet
Using the method described successfully rooted Tesla L7 tablet. The method used is T3 and supersu used is UPDATE-SuperSU-v2.40
Is the recovery built from source?
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
pm-cz said:
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
Click to expand...
Click to collapse
The actual recovery is built by @vampirefo but i am very interested in adding that feature in and was actually going to ask you about that.
Also have you looked at any of the older update_osip source?
Can you please tell me an easier to understand method.
Because even though i understand what you're talking about, i don't know where to put the files. I understand flashing the session and all but coukd you pleeease explain how to root. Because this the first time i'm rooting a device
Thanks
rooting without voiding warranty
Can you please tell me how to root my dwll venue 8 3830 without voiding the warranty?
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/android/software-hacking/mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Getting Windows 7/8 to Recognize Dell Venue 3740
Fajfie said:
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Click to expand...
Click to collapse
Thanks to Social Design Concepts for the great work. It is appreciated!
Fajfie, thanks for posting. That's awesome. If you used Windows, how did you get Device Manager to identify the Dell Venue 3740? I've downloaded all recommended driver files in this and the previous thread and I can't get Windows to identify the device. When I run launcher.bat I get DEVICE: UNKNOWN.
Any ideas?
Another rooted
Great work, this worked to gain root on Medion (Lenovo) Lifetab S10346 tablet.
Intel Z3735F cpu
2GB ram, 32 GB storage.
I used trigger T3 and it went through smoothly, a Great bit of work.
Works perfectly on the Asus Padfone X Mini. I referenced this thread over in the device specific forum. I used the T3 command in step 3.
Thanks!!!
Worked on my ASUS Padfone X mini (TOOS) used T3 option.
Thanks!
Thanks you. The procedure works with method 3 to GoClever Insignia 700 PRO , Android 4.4.2.
I just installed IntelAndroidDrvSetup 1.5.0 with the drivers for my pc.
hi im having the same problem as GeeKerGurL
" Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help! "
i have a Acer Iconia A1830
Problems with the update surpeuser zip
I followed your guide to rooting Acer iconia tab 8 A1-840FHD with intel chip, (Wich is great by the way thanks) and evrything goes to plan until, i get to Install Zip. I get, E:Can't mount /sdcard/ Update-superSu-v2.40(1).zip Installation aborted. I've downloaded the zip from your link by desk top (windows 7) and transferred it over. Also downloaded from the tablet and just used a file manager to move it over to sd. Same msg for each. I used the T3 option. any ideas how to get the zip to install?
Zip copy to folder on your tablet (download,...) and install from recovery install. zip.
Send from my Samsung Galaxy S2 - RR Lollipop v. 5.2.7
Verified with Acer Iconia A1-830
Firstly, big thanks to the dev, social-design-concepts for making this thing work on Intel device. Thumb up~
It works wonders with my Acer Iconia A1-830 android 4.4.2.
I used option T1 and it works without any problem.
Thanks again.
P/s: Hope this will work on the latest Intel devices like Asus Zenfone 2 ;p
Hello and thanks for reading / helping if you can.
In brief, I have a Samsung Tab 2 GT-P3110 tablet which was running android 4.2.2. It's main use was as a controller for my sonos sound system which no longer supports my device. I thought I'd try and update it rather than simply chuck it into landfill for no good reason other than it was old like me! I know almost nothing about what I am doing, sorry!
So far I have I think 'rooted' the device using something called odin, and installed the clockwork recovery mod. I have also installed the Samsung drivers onto my PC and I have on my pc a zipped file which I believe will install a newer version of android (perhaps some guidance might be required for best file to go for). Unfortunately I am unable to see my tablet's sd card (or anything to do with the tablet) when connected to my pc via USB in order to copy it. Moreover I have copied the same file to a micro sd card but when I put this directly into the tablet and try and boot off the external card I get an access error and the card is not read.
I am out of ideas now and wonder if one of you clever people might be able to help me? I think I read somewhere about having to switch on USB debugging and USB sharing or the like BEFORE rooting. The instructions I used only mentioned the former and so that's all I did. Maybe I've locked myself out for good.
Thanks again, Pezos
Blimey, I really must have killed it! Surely someone out there can help me fix it?