Related
Hello all,
I'm currently sat with my VF-UK HTC Magic and want to start pulling this thing apart a bit if it'll be of use to the more experienced on here, although I'm not 100% where to start.
Below is a breakdown of where I am at the moment, can people please post with further suggestions and what files/dumps from the device you'd like to see etc.
With adb loaded into root mode: (adb root)
Code:
C:\android-sdk-windows-1.5_r1\tools>adb shell
# ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.sapphire.rc
init.rc
init.goldfish.rc
init
default.prop
data
root
dev
I am in the process to pulling off these files to package up for others etc. however not having a great deal of experience I'm looking for some pointers as to which bits to pull off and upload?
I'm also in the process to playing with SQLite. Which I've successfully got into but my SQl experience is based on MS SQL so again getting my head around this with a view to locating and extracting the operator setting files etc.
Any tips, requests to try on the device (within reason) etc. please post
Thanks
I'm not sure if the forum rules would allow it, but you would get a million more page views (and therefore help) if you post this at the Dream section instead. The Dream and the Magic/Sapphire is basically the same phone anyways, except for the keyboard (or lack thereof) so I don't see the harm.
Jethro - Should Vodafone staff really be asking questions like this?
Tell'em armholes Jethro.
P.S keep the emails coming, We love you up at 2nd Line
Why not? This is an open source device, only the SIM belongs to VF. As I am not decompiling the SIM or even the radio stack at this point everything I'm accessing is within my rights - at least this is my grasp of the licensing side. The Linux kernel is obviously open source and Android itself is released using the Apache License.
"Like any free-software license, the Apache License allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software."
So as far as my understanding goes I'm not contravening any licensing or contract, if anyone can provide evidence otherwise then please post and I’ll stand corrected.
Otherwise I'm cracking on with more adb fun today!
@jbelman
source is free, but not compiled binaries, so you are not allowed to 'hack'.
Can anyone explain exactly why the actual compiled binary licensing model differs from the source code?
thevery said:
@jbelman
source is free, but not compiled binaries, so you are not allowed to 'hack'.
Click to expand...
Click to collapse
And who cares about this? It's my phone, so I can even throw it out of the window, if I want.
@jbelman
How did you get the root rights? If I run adb root, I get an error message, that the adbd daemon cannot run with root rights in production builds.
I did some research with adb shell before.
I haven't found any hole I could use to get root rights. Your shell runs with user and group "shell". All the data on the NAND-Flash (Apps and so on) are saved with the user and group "system" and you are not even allowed to enter this directory with another user.
The SD-Card is mounted nosuid and noexec. So we can't execute a local root exploit or something like this from here.
Breaking out of the Java VM is also not possible, because every Application runs with an own user. What would perhaps be possible is exploiting the VM (if there is a security vulnerability in it) and executing a local root exploit (if there is any available for this kernel) from there.
I'm currently waiting for the first update Vodafone delivers. I will sniff the download source of it and save it on my computer to have a backup if anything goes wrong when I'm playing with other firmware versions. I don't want to brick my phone.
@ Matschkeks1988
Are you using 1.1 or 1.5 SDK? I used 1.5.
I'm also a bit loath to really screw around until I've got a stable replacement image etc. should I brick it. Fingers crossed we can grab using update like you suggest.
By the way if anyone has any issues with adb giving: error: more than one device and emulator (I got this after using pull command). Disconnect your device and run: adb kill-server. This will remove all the devices, plug back in and away you go again.
I appear to have a different version baseband, kernel and build:
Baseband:
62.47S.20.17U_2.22.19.07I
Kernel version:
2.6.27-00342-g1936dcd
Build number:
CRA71C
What's everyone else on?
Version
Baseband version
62.50S.20.17U_2.22.19.261
Kernel version
2.6.27-00392-g8312baf
[email protected]) (gcc version 4.2.1) #72
Build Number
CRB17
Vodafone contract phone
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
andr[email protected] #72
Build number
CRB17
uk vodafone contract
Looks like Jethro's device is from a different pot.
Which hardware revision do you have? Do you have search button? Who much onboard storage? All of these things changed through the development process.....
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
Click to expand...
Click to collapse
Same here. SFR/Vodafone (France) contract. Search HW key variant.
Baseband version
62.50S.20.17U_2.22.19.26I
Kernel version
2.6.27-00392-g8312baf
[email protected] #72
Build number
CRB17
The same for VF Spain.
IseeBrickedPhones said:
Looks like Jethro's device is from a different pot.
Which hardware revision do you have? Do you have search button? Who much onboard storage? All of these things changed through the development process.....
Click to expand...
Click to collapse
The hardware is normal. The difference appears to be software only.
My info:
http://i42.tinypic.com/jf8acw.png
Vodafone Spain
jbelman said:
The hardware is normal. The difference appears to be software only.
Click to expand...
Click to collapse
Does this mean you do not have a retail Magic? Where did you buy it from?
Yes VF Retail.
I have spoken to VF about this today and they are looking into why it was shipped as the build is pre-release, as such I can't perform a wireless update.
VF won't release a update to flash over USB either, something to do with Google.
I'm going to have to get it exchanged. So will continue my research on this earlier build while I have it.
Hi,
Some people on the forum probably noticed it already before me, but tweets from Cyanogen and JBQ brought it to my attention that the official Android 1.6 system images for the ADP1 are now available for download from HTC:
http://developer.htc.com/adp.html
I haven't installed them yet because my unofficial Cyanogen build is probably better than those in a number of ways ;-) But I did download them.
Also, these are probably required to build a real & working Donut 1.6 build from the AOSP tree.
Cheers everyone, and enjoy!
--Tim
Just wondering couple things:
1. Does it have Google Apps?
2. Do you loose root if you install this?
3. Does it mess-up recovery image?
So did anyone try it yet?
Hi Karolis,
I haven't checked the contents of the images but I expect them to have the Google apps. The 1.5 images from the same site contained them, as far as I know.
Whether or not it messes up the recovery image depends on the method of installation you choose, but you can always put back the recovery image of your choice on your ADP1.
I don't know about losing root access or not. I've heard people claim that it depends on your recovery image used. It will not include the SuperUser application but you can install that manually.
Cheers,
--Tim
HTC is an authorized Google distributer I guess:
# Use of the Google Software by You
1. You agree to use the Google Software only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).
Click to expand...
Click to collapse
I'm going to flash just the system image and see how it goes...
Didn't wipe, going from CM 4.1.11.1 to 1.6 - boot looped.
Finally got back to recovery (Cyanogen Recovery gone!) and wiped cache + user data, and at least got it to boot. Phew!
Better get Cyanogen's recovery back pronto, so I can restore my nandroid backup.
/Mats
dude.... dont use the OTA, use fastboot and fastboot flash boot and system and reboot -w. The reason it requires a wipe is because of the differences in frameworks, apps, dependencies, ramdisks, etc.
I was waiting for this, this is going to be my default now. I don't like all the stuff Cyanogen does to builds, I preffer the official ADP builds 1000's times more.
---edit----
I flashed it right away and now I'm confused. It's 1.6 alright, but the build is different from previous ADP builds, no dev tools or spare parts or anything else. This is almost exactly what you'd probably get from a stock 1.6 build, weird...
BTW, you don't lose root with this, ADP builds are meant to be rooted, you know?
can someone confirm if you lose cyanogen's recovery image?
···
这个还不错··希望走点出update包····but··我最期待cm 4.2···
Agh someone plz post a 32a version
Gosh, what a mess. After finally getting CM recovery back in, I went for a nandroid restore, but instead made a nandroid backup, overwriting my precious backup of my phone as it was before embarking on this 1.6 adventure. Well, after reinstalling CM 4.1.11.1 (hush - I had a backup on my SD card!) at least I got all my apps back.
Why must I dive into stuff like this when I'm in a rush and really don't have the time for it?
/Mats
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
marty22877 said:
can someone confirm if you lose cyanogen's recovery image?
Click to expand...
Click to collapse
You wont loose it if your flash the new system and boot partitions via fastboot. Any of the Apps 2 SD stuff won't work though.
elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
????
Aaaanyway... I noticed this build doesn't let you su (wrong uid for the su binary), but that can be fixed easily, just pull su and Superuser.apk from another build, boot your phone into recovery, and push su to /system/bin and Superuser.apk to /system/app, then chmod 4755 /system/bin/su and reboot.
---edit--
you might also want to rm /system/xbin/su, but I don't know if it's really necessary or not. Gonna try it.
ok, removing xbin/su did nothing apparently, so it's safe. Keep in mind though that the stock boot.img is doesn't allow you to adb remount, but you can still adb shell, then su, and then remount manually (mount -o rw,remount /system). We just need to change ro.secure in it and we're good to go.
Using fastboot to only flash boot and system worked perfectly fine for me.
Very nice and clean.
Apps2sd can still be had if you want to, just do it the manual way (creating symlinks).
Pushing the xda versions of Launcher and Messaging makes the phone very, very nice - and the only things that I feel I'm missing is the userinit.sh and compcache really....I never really noticed/cared too much about the BFS.
Pretty nice build to be honest....
elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
Because the G1 and ADP1 are both identical Dream handsets? And people want an official donut, rather than 1.5 with many donut features hacked in?
just wondering, will this work with rooted Dream Phones???
bootloader
i'm getting error message updating from 1.5 adp crc1:
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: HT847GZ00498
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Click to expand...
Click to collapse
i have a adp phone.
tried to roll back to stock 1.5 img or ota, same issue, is someone had this issue?
@ anyone who tried this. Which build number is this? Is it newer than 1.6_r1 (DRC79) or should I keep building the experiemental tree?
well someone from goapk.com emailed me saying they like one of my apps, and they want to convert it to Chinese and upload on their website and android market.
anyone ever heard of this place b4? and is there any chance they can just rip off my app and copy the source code?
they are asking just for the data where i keep my text so they can convert it to chinese, then i make a new apk for that and email it to them.
I got an email from them and from others. Each time, I replied saying I wasn't looking to distribute outside of the Android Market. They can't rip off your source code from the strings file, but it's possible to find out how it works using tools like baksmali. They are probably legit since they wouldn't contact you first if they wanted to do that
haxxo said:
they are asking just for the data where i keep my text so they can convert it to chinese, then i make a new apk for that and email it to them.
Click to expand...
Click to collapse
I don't understand, why to email it to them and not just upload to Market by yourself? Then they will be able to install it normally and they will get it in their language.
haxxo said:
and is there any chance they can just rip off my app and copy the source code?
Click to expand...
Click to collapse
Even now they could download your app from Market and localize it by themselves very easily, really
I was helping Chinese people in fixing their issues in Google Maps. They are good guys mostly, they just have problems with English.
goapk
goapk is apparantly the build of my htc desire. as is whenever i turn it on it says HTC then goapk.com then something in chinese. i bought it in china...
It sucks. it has the chinese GoMarket, not the android market. cant download anything!
Please tell me if i can download an apk version of the real android market from anywhere..
goddlike said:
goapk is apparantly the build of my htc desire. as is whenever i turn it on it says HTC then goapk.com then something in chinese. i bought it in china...
It sucks. it has the chinese GoMarket, not the android market. cant download anything!
Please tell me if i can download an apk version of the real android market from anywhere..
Click to expand...
Click to collapse
I'm having the exact some issue! Just bought an HTC Desire in China, no Android market, just this terrible Chinese market called GoMarket by goapk. Super annoying. If anybody has a solution, please let me know!
Btw, I already tried rooting the phone using Unrevoked, but my phone has hboot 0.93 which seems to be impossible to root at this point in time.
Solution for goapk.com (or just rooting branded phones)
Ok, I've managed to solve the issue based on the information from this forum, so here's the solution (which is unfortunately quite long, but it works... at your own risk, of course):
The issue: A bought-in-China HTC Desire, branded by the horrible goapk.com with no Android market access. Could only access some Chinese market called GoMarket created by goapk.com. This could also apply to anyone with a branded phone (eg. branded by a carrier) that could not be rooted with UnrEVOked3.
Solution: Downgrade the OS to an unbranded HTC Sense Android 2.1 with a goldcard inserted in the phone. This makes it possible to root the phone using Unrevoked and then you can install any of the Android ROMs you like on it. Technically you could stop after downgrading to Android 2.1 and not bother rooting (since you'll already have Android Market access by then), but you'll probably want to continue so you can finish with Android 2.2 on your phone.
Method:
Step 1:
Get an extra MicroSD card (2gig or whatever) and create a goldcard. You need this because your phone is branded with goapk.com and this is part of getting rid of that. Find out how here: android.modaco.com/content/general-discussion/305672/creating-a-goldcard/#entry1233023
Tip: you don't need an microSD card reader. You can format the microSD card in your phone by connecting your phone as a USB drive, and right-clicking the drive and formating. It MUST be FAT32 format, NOT FAT, so do it from the computer controls, not on the phone itself (because the phone itself does it in FAT format)
Step 2:
With your goldcard in your phone, you can now downgrade to Android 2.1. This kills two birds with one stone. A. It removes the horrible goapk.com branding and B. Lowers your hboot from 0.93 to 0.83 which makes it possible to root your phone. Instructions here:
forum.xda-developers.com/showthread.php?t=768256
Tip: if it fails the first time (as mine did) and it can't find the zip file at the end, make sure your goldcard was FAT32.
Now your phone will be running HTC Sense 2.1 unbranded, with access to Android Market. The next two steps will allow you to put any of the Froyo versions (with Sense or without, your choice) on your phone.
Step 3:
Root your phone with UnrEVOked. Instructions here:
rootmydroid.co.uk/guides/general/howto-root-your-htc-desire-wildfire-evo-incredible-with-unrevoked/
Tip: His instructions are great. His download pages are horrible, but they work eventually, just keep clicking.
Step 4:
Install any of the custom Android ROMs available. Instructions are also found on the above link for rooting the phone.
You can choose from any of the ROMs listed here: forum.xda-developers.com/showthread.php?t=809328
I went with DeFroST, which is a nice Android ROM without Sense, since Android is better off on it's own, IMO.
Tip: If you don't have an MicroSD card reader, make sure you put the ROM's zip file on your MicroSD before you wipe your phone (Pt. 3, point 4 in the guide).
That's it! When you finish, you'll have rooted phone with full Android Market Access and any version of Android you want on it. Sorry I couldn't recommend an easier way. Now if I could just get my hands on this damn person at HTC who let goapk.com crap all over this phone to begin with (or Google for not putting any rules in place)...
wow thanks a bunch. I hope this will work...
need to get hands on an extra microSD card for the moment
idasein said:
That's it! When you finish, you'll have rooted phone with full Android Market Access and any version of Android you want on it. Sorry I couldn't recommend an easier way. Now if I could just get my hands on this damn person at HTC who let goapk.com crap all over this phone to begin with (or Google for not putting any rules in place)...
Click to expand...
Click to collapse
I just debranded my phone and holy crap its working! but i have a question:
Can i put initial sd card in it now? or do i have to use the goldcard forever??
Wow
Many thanks and 'holy crap' - this worked like a charm. My Android Desire is now fully functional!! FYI, if you have a Chinese simcard, you will still have restricted access to the Android Market but it will be much much better than goapk.com. However, if you insert a North American sim card, it works perfectly. Thanks again!
Robert to be able to gain full access to Market you can use something like MarketEnabler, which I'm sure you can find somewhere on the internet as .apk, since you won't be able to find it in the localized "chinese" Android Market..
getting rid of goapk
Have a Chinese HTC Legend, which came with goapk which was awful - slowed the phone down but also blocked the Android Market so that I should buy apps at the goapk market.
Thanks to Idasein, I got the idea of how to get rid of it, but had some problems with the files in the links mentioned (Kaspersky screamed that there was a trojan)
If anyone needs to get rid of goapk, then you can alternatively have a look at the easy instructions on Unlockr for how to downgrade a Legend - create goldcard, make the phone downgradeable, then downgrade. This leaves it with a clean Android 2.1 (minus goapk) which you can then root and do custom ROM or, as I did, then update to Froyo. Worked beautifully for me!
Search theunlockr.com for "how-to-downgrade-the-htc-legend-to-1-31-so-it-can-be-rooted"
thanks a bunch, idasein
finally got rid of the f***er, too, and installed leezoid instead.
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
Ive been folowing the tutorial for how to "dualboot" Android And Windows Phone and i use Haret linux loader to boot up to android.
but it doesn't boot up it give's me Kernel Panic And says something with Killing Process
I Tried GB With Raphel 100 (As that's the device i got acording to the reseller) also i dont know how to check it either =/ (When i have no manual or box)
but i still got the same problem and i have followed the tutorial
Edit. Solved Changed to tael rom and worked, EnergyROM has some kernel loading issue
Any Idea?
Can you run haret.exe from the microSD (without the dual boot option)?
R^7Z said:
Can you run haret.exe from the microSD (without the dual boot option)?
Click to expand...
Click to collapse
yes,
If this help's
I got WP 6.5 Energy.
or do i need a more proper tutorial?
I followed thedeadcpu's reake tutorial on youtube
What I'm attempting to troubleshoot is where the problem is by figuring out whether you can run XDAndroid properly without the dual boot option. Basically if it is the script used to run the dual boot program or if somehow you missed a step in setting up XDAndroid. So, what I need to know is if running haret.exe from your microSD on your TP actually works and if you are able to get to the Android home screen. If not and if you are unable to run Android properly, we might have to start from the setup process. I am currently running 29022.Sense2.5.Cookie.2.0.sencity.Jul.06 so I doubt it has much to do with the ROM but there is a possibility there might be an issue with the program itself. However, we need to tackle one thing at a time in order to confirm where the problem is.
R^7Z said:
What I'm attempting to troubleshoot is where the problem is by figuring out whether you can run XDAndroid properly without the dual boot option. Basically if it is the script used to run the dual boot program or if somehow you missed a step in setting up XDAndroid. So, what I need to know is if running haret.exe from your microSD on your TP actually works and if you are able to get to the Android home screen. If not and if you are unable to run Android properly, we might have to start from the setup process. I am currently running 29022.Sense2.5.Cookie.2.0.sencity.Jul.06 so I doubt it has much to do with the ROM but there is a possibility there might be an issue with the program itself. However, we need to tackle one thing at a time in order to confirm where the problem is.
Click to expand...
Click to collapse
well as far as i seen i can run haret but at haret.exe it give's me some end trace
and kernel panic problem, either it freeze or it reboots to windows (how to check exactly what device of raph i got)
EDIT. I got raph100 , i used the setup.txt once had same problem
So it's possible that you are having issues with setting up XDAndroid. My next question is to ensure you are running the most up-to-date bundle of XDAndroid and to find out which version you are running; Froyo or Gingerbread. This way I can direct you to the correct and current location of this bundle. I currently am running a version of Gingerbread and it seems to be all working and last time I checked, Froyo was working as well. The startup.txt file I am using is the one for the RAPH100 and comes from the bundle. Additionally, in order to ensure a good data.img file, I go a step further and leave out the media and Androidapps folders. I also include a ts-calibration file so I can by-pass the calibration step. Let me know if you'd like to know my process. It's simple but yet pretty much 100% effective.
R^7Z said:
So it's possible that you are having issues with setting up XDAndroid. My next question is to ensure you are running the most up-to-date bundle of XDAndroid and to find out which version you are running; Froyo or Gingerbread. This way I can direct you to the correct and current location of this bundle. I currently am running a version of Gingerbread and it seems to be all working and last time I checked, Froyo was working as well. The startup.txt file I am using is the one for the RAPH100 and comes from the bundle. Additionally, in order to ensure a good data.img file, I go a step further and leave out the media and Androidapps folders. I also include a ts-calibration file so I can by-pass the calibration step. Let me know if you'd like to know my process. It's simple but yet pretty much 100% effective.
Click to expand...
Click to collapse
Man youve been to a big help, i changed to TAEL rom, due to EnergyROM was slow, and guess what XDANDROID worked! so i guess it was my rom ^^