Related
Is there a good way to get the current version of Cyanogen up and running on the SDK emulator? I have several people that complain about my application widget closing when they open or close the keyboard. The logs show nothing pertaining to my application and the only thing they all have in common is a stock G1 with Cyanogen 4.2.6 and no home screen manager. Many others with non-modded G1's do not have this problem.
I'd like to test it out in the emulator since I now only have a Droid
I found some instructions with an image file to use for this, but it was for a very old version of Cyanogen.
do a nandroid backup and then copy the files from it in to the directory of a virtual device you have already created
then all shall be good
Is there a good source to snag a existing nandroid backup of 4.2.6? I don't have a G1 or any other device to run a nandroid backup on. Too bad too cause I just shipped out my old HTC Magic a few days ago. Now all I have is my Droid.
I'll search around for one and report back if I locate one.
just did a dump for you
http://code.google.com/p/cyanogen-updater/downloads/list
itl be up in a few minutes
You just need to make a yaffs2 image of the /system folder from cyan's update.zip. The boot.img is already in the zip.
Search for mkfs.yaffs2.
That nandroid backup works perfectly in my AVD 1.6 emulator. Thanks so much for building that for me. I can test all my apps against Cyan now
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?
pcm2a said:
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?
Click to expand...
Click to collapse
Yes, you can run anything on the emulator like that
I also found out that trick a few days ago. The only problem I have is that I do not get an Internet connection.
Does the SDK simulate wifi, 3G or is there just another fictive network device? I've got DroidWall and Y5 installed. Furthermore I've got sometimes problems to start my wifi after rebooting (problem by manual copied wpa_...cfg, I guess).
I am not really sure where to search. I will investigate the stuff in the paragraph above but perhaps you've got another few hints for me?
btw: I've got 4.2.13, but that shouldnt make a big difference, should it?
Anybody has found a fix for internet Issue for Cyanogen system.img file and Android SDK emulator?
Regards,
Oscar.
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Firstly it needs to have a recovery image installed I recommend Amon-Ra v 1.6.2.
Secondly you need to find the radio rom you wish to flash and put it onto the root of you phones sd card.
Thirdly enter the recovery image you have installed by holding power and home button from the phone being off.
Then select the radio.zip to flash.
Everything I have said here can easily be found how to do via searching this forum or its wiki.
also www.theunlockr.com will help with installing the recovery image.
lohtse said:
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Click to expand...
Click to collapse
First you will need to install the custom recovery console if you haven't done so already.
Then download your updated radio, put it on your SD, load into the recovery, then apply update. DONE!
If that is too brief,... let me know,...
EDIT... Ooops,... too late.
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Lennyuk said:
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Click to expand...
Click to collapse
I came from wimo to android, and as it is said, it's quite hard to catch the thing at the beginning, but after everything seems easier than in wimo !! and more reliable... you have almost no chance to brick your hero after you installed the recovery boot.
radio : boot in recovery then select the good option.
rom : nandroid backup / install whatever rom you want / if you don't like it go for nandroid restore ( all you need is two Sd card.. the good one and the one for the "tests" ).... etc....
But at the beginning i was totally out but with a little time.. reading some posts (here and on the web) ... one day everything was more clear !
Ciao
Fred
lohtse said:
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
Click to expand...
Click to collapse
Its not hard at all. You can have the recovery installed and the radio updated in 5 minutes.
For step by step instructions follow the "Installing a recovery image" section in BTDAG's guide linked in my signature.
Then further down the same post, in the second yellow box there are instructions on "Updating your Radio".
Guys, the OP said he was issued the Hero at work, then two hours later said he was going to ditch Android... so what then, he's quitting his job? Troll alert. Don't feed the troll.
As to troll comment(yes offence has been caused)....hmmmmm.... Am going back to the trusty Kaiser... WE DON'T HAVE TO USE THE HERO.... We live in free(ish) world.. And the Phones are issued as an update to our old duty phones... Also I'm not the only one who uses them that feels the same.
Now to updating being easy. Gulp I must be eeer dum!!! Du hu Du HU must be the TROLL in me!
I have tried to install recovery image thing and well just cant get it to work... And now I find I have to root the hero too so things will install to sd card!!!! WTF this should all be standard like winmo and symbian etc...
I have been using smart phones since the Ericsson r380 and so far Android has failed to impress to the degree I am beginning to hate it....
Am far to used to having simply andfull access to everything..
Android is a HUGE learning curve that I suspect I may not have the patience for..
regards The TROLL sorry I mean Lohtse
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
Click to expand...
Click to collapse
Wahey!!!! Good job man.
Ok,... So now you have the recovery image all you need to do is pick a custom ROM. Personally, I highly recommend MCR3.2 (link in signature at botom). It is an Android 1.5 ROM but is stable and fast, what more could you want for a work phone.This ROM is rooted and has apps2SD enabled. Once you have installed the ROM you will need to remember to create an ext2 partition on the SD card (easily done through the recovery). Then you are set to go!!!!
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL TROLL
Click to expand...
Click to collapse
You're welcome And what ddotpatel said. MCR is fast & clean. By installing a custom recovery you've already done the only tricky bit.
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
lohtse said:
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
Click to expand...
Click to collapse
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Someone with more knowhow than me correct me if I am wrong?... CAULI?,... LENNY?
Can someone who knows please answer this question:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Thanks!
ddotpatel said:
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Click to expand...
Click to collapse
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition. All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer, if you're curious. Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed. The saving you make just from shifting the apks to sd is more than enough for most people it seems.
cauli said:
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition.
All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer.
Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed.
Click to expand...
Click to collapse
hmmmm I certainly noticed a drop in available memory on the phone to the degree of only having 54 megs free...
SebHTCHero said:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Click to expand...
Click to collapse
what is rf calibration?
What is radio rom used for by phone?
kendong2 said:
what is rf calibration?
Click to expand...
Click to collapse
A set of tables usually stored in NVRAM that takes into account the slight differences in the components used to build your phone. Every single phone is calibrated during manufacturing.
If the calibration is erased, it will look like it works but you can have all sort of problems from poor battery life to random drop from the network or poor sensibility (not to mention the higher than expected radio levels you could be emitting right next to your brain )
So to get to the point... I bricked my friend's SGT after trying to put a dialer app onto it. A series of stupid moves leaves it at the Samsung logo on bootup and only able to access Download Mode (No recovery). He's getting a replacement through warranty (oops) but in the meantime I'd love to learn/experiment with building my own ROM.
I've been an avid Linux user for a couple years, learning more and more as time goes by. I've done extensive modding on the Motorola Droid and Droid 2 (modding, no programming, dev'ing or cooking). Basic familiarity with the Android system and how it works.
However, it's been a huge learning experience trying to build my own ROM from source. I downloaded the SGH-I800 VZW and also the GT-P1000 sources from opensource.samsung.com and also the android source from source.android.com
following the instructions from the README inside the I800 source .tar, I wrote the GT-P1000 files over the android source, then wrote the I800 files over the combined GT-P1000/android source. After some configuring to make this work on a 32-bit system with java1.6 lib's, I finally arrived with a working "make" command in my ~/bin folder (where repo stuck the android source). before running make I did run "make update-api" and it seemed to go off without a hitch.
It's currently running and has been for quite some time (around 45 mins or so, which is normal on my centrino 4 year old laptop. However, I'm seeing quite a few warnings about parenthesis and various other syntax-related issues.
Is this going to be a huge problem with the final .img files? I can't imagine it working perfectly... Is there any way to debug this compilation procedure? I'm just using terminal and obviously there are far too many to stay in the lines history of terminal app.
Thanks for the help guys, I'm hoping to at least get this tablet bootable so I can apply a more advanced rom or (depending on the difficulty) revise my own rom into a fully working one.
-Garrett
P.S.- If I understand this correctly, it will output a few .img files into the /out folder. How am i to flash these using ODIN? can I just put them into a .tar archive and select that under the PDA option of ODIN? I've already compiled the kernel for the SGT, it seemed very straightforward and I've got the zImage file. I also read somewhere that the kernel should be included in the main platform compilation. However, the zImage file is just thrown into one of the other .tar's downloaded for a different device (just to get a feel of what format files should be where). Some advice would be much appreciated! Thanks.
update:
it compiled and produced three files of standard format (*.img) which would be used to
a) extract the /system folder, etc. to produce a flashable update.zip in CWM or some other custom recovery.
or
b) flash directly using some other program, with target booted into the bootloader,
if I recall correctly. The problem with the former is that this tablet will not boot into recovery, and with the latter, no suitable program seemingly exists. There must be some method of converting or repackaging these *.img files into Samsung's proprietary *.rfs format, but extensive google searching has yielded nothing of value.
ok, update #2
flashed a zImage and factoryfs.rfs from a sprint ROM, and of course data doesn't work on this verizon tab (actually not a big deal since I'd be wifi tethering from my Droid 2 anyway) but it does have all the sprint applications and settings and all that.
I have a full /system dump from a completely stock verizon tablet, what is the most straightforward way of flashing this onto this frankenstein tablet?
I'd imagine it entails flashing clockworkmod recovery and flashing an update.zip that contains the entire /system folder, would this work?
I've tried simply
adb push ~/Galaxy/system /data/sysbackup
then
busybox cp -rf /data/sysbackup/* /system
however this just results in a lot of disk full errors and an unbootable tablet.
thanks for the tips guys, and wondering what's so bad about the vzw tablet? there seems to be a lot more threads/roms/support for (of course) the GSM tablets and even Sprint's but none for big red.
Not sure if this would work, but maybe creating a VFAT image in Linux and dumping the contents into it then saving the file as factoryfs.rfs and flashing it?
Or, mount a known good factoryfs.rfs, rip out the contents and replace it with the VZW stuff. (Since RFS images can be mounted as VFAT in Linux/Unix)
As far as getting data up and running, you would probably need a dump of a radio from another VZW Tab. (/dev/block/btl12 if it's anything like the GSM Tabs)
gfrancis306 said:
thanks for the tips guys, and wondering what's so bad about the vzw tablet? there seems to be a lot more threads/roms/support for (of course) the GSM tablets and even Sprint's but none for big red.
Click to expand...
Click to collapse
I can only answer for myself on this one, I always prefer the GSM devices because they often have Euro/Asian counterparts, thus bigger modding communities. The GSM models will definitely have more presence solely because the majority of markets for the device are GSM-based.
thanks guys, I definitely understand the GSM tabs getting more traffic but couldn't figure out why Sprint was attended to while VZW went overlooked.
Either way, I had a friend of mine .tar up a rotohammer backup from his VZW tablet and send it to me through dropbox. un-tar'd and flashed using heimdall and it booted right up with VZW service and everything. the only problem I notice is there are no google apps (Market, Gmail, Maps, etc.) I know there's a quick fix for most android phones by just flashing gapps.zip through CWM recovery, but since there's no way to fash CWM on the VZW tab, how would I go about getting my google apps back?
Thanks
Do a factory reset or try one of the market fixes in the main galaxy section. Should be fixable.
Does your GPS function?
gfrancis306 said:
thanks guys, I definitely understand the GSM tabs getting more traffic but couldn't figure out why Sprint was attended to while VZW went overlooked.
Either way, I had a friend of mine .tar up a rotohammer backup from his VZW tablet and send it to me through dropbox. un-tar'd and flashed using heimdall and it booted right up with VZW service and everything. the only problem I notice is there are no google apps (Market, Gmail, Maps, etc.) I know there's a quick fix for most android phones by just flashing gapps.zip through CWM recovery, but since there's no way to fash CWM on the VZW tab, how would I go about getting my google apps back?
Thanks
Click to expand...
Click to collapse
Did you get the dbdata.rfs or cache.rfs? I think they play a part into stuff like the market. Check for the apps in /system/app though.
Sent from my SGH-I987 using XDA App
I bricked VZW SGT by flashing another rom accidently and now it wont go further than the Samsung logo on bootup
is there any way to flash back the orginal rom?
On my sprint gt. I am able to get to clockwork mod recovery by doing
Code:
adb reboot recovery
as far as I can tell there is no way to get to recovery with the device off. But if it gets as far as the samsung screen you still might be able to use adb to reboot to recovery. I've been trying to build froyo myself and as a proof of concept compiled the stock kernel from samsung open source. Then put it in a modified update.zip from one of monks kernels and flashed it from clockwork recovery. The flash was a success and the device booted fine. I dont see why the same shouldnt work for the system folder. The boot.img would be more difficult cause I dont think the gt uses the same partition layout as other android phones.
Helo my name is robert an im new to this. Im looking for some roms for my vzw galaxy tab. Dose anyone have any suggestions ? An is there a stable gingerbread or honeycomb roms out there for the galaxy tab for vzw ? Thanks to all that can help me
Sent from my SCH-I800 using XDA App
basically my motorola atrix doesn't work any more!!
the bit of the screen which is meant to be used to access the buttons bellow, work as though you are pressing the bottom of the visible screen!!
EVERYTHING is shifted down! if i want to press something, i have to press the area 1cm bellow the location!
I suspect it is cause by me formatting every single folder on the internal storage using clockwork recovery...
i have tried installing the original Rom using RSD, i have tried everything!!!
ANY HELP PLEASE?
the device is a piece of garbage now!
i saw that NO ONE else has reported this issue anywhere on the net!!
it can't be a hardware problem cause it was working before i formatted all of those folders! including the ones with the 3 character names... can't remember the names... but basically i formatted everything...
this is a common problem when you format / partition the internal memory. it screws up your PDS partition, which i hope you backed up. search a little more, there are lots of topics on this in the dev forum and I believe there MAY be a solution but i don't remember.
Just found a couple of threads...
I didn't back it up... does this mean that my Motorola atrix is practically worthless now? :s
Solution
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!
benedict.s said:
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!
Click to expand...
Click to collapse
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?
dLo GSR said:
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?
Click to expand...
Click to collapse
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?
benedict.s said:
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?
Click to expand...
Click to collapse
well, that's a little over my head, but i know some of the devs would be able to help you if you PMed them maybe.
coolios...
know anyone in particular?
Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)
Hi!
When removing Bloatware with Titanium Backup a while ago, I accidentally missed a click (never used a touch screen...) and uninstalled MediaProvider, which I have not been able to recover since.
I tried putting the files back from a friend's HTC, which didn't work; after that I was told even the packages differ between manufacturers, so I tried getting them from a stock Bell Atrix .zip posted on these very forums, which didn't help either. Neither #android-root nor AndroidForums were able to help, thus I ask here: Can anyone tell me how to either make my system accept Bell's files, or where I can find a "vanilla" Motorola build?
(Problem is, the phone didn't come from a phone company, a friend of mine got it pre-release from his uncle who is with Motorola, so it may even be different from what hit the market later on...)
I guess the following information will help, it's a Titanium Backup info file for another componend I backupped shortly after:
#Titanium Backup
#Sat Feb 25 03:28:43 MEZ 2012
app_gui_icon=[...]
sys_ro.build.date.utc=1302536066
app_version_code=8
sys_ro.product.model=MB860
has_prefsdata_jpu=0
sys_ro.serialno=<xxx>
sys_ro.build.description=olympus-user 2.2.2 OLYEM_U4_0.44.0 578673 ota-rel-keys,release-keys
has_prefsdata=0
app_gui_label=com.android.providers.applications 2.2.2
sys_ro.build.version.release=2.2.2
app_apk_md5=1989ff2476ee73ad445760b9bef5f44e
has_dbdata=0
app_apk_codec=GZIP
app_is_forward_locked=0
app_is_system=1
app_label=com.android.providers.applications
app_version_name=2.2.2
generation=1
app_apk_location=internal
(Most of this is unnecessary, I guess, but I can't really be sure what you might need to judge what I would have to to...)
I would be very grateful for any help, it is extremely limiting not to be able to use any media capabilities.
So, thanks in advance,
David
maybe flash a new rom if your contacts are all backed up?
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Intelensprotient said:
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Click to expand...
Click to collapse
Yes, but you have to set the permissions same the other files in .system/app folder.
I have attached the missing files to this post. My gingerbread version is 2.3.4.
Good Luck!
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Intelensprotient said:
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Click to expand...
Click to collapse
I would hard reset too at this stage. I'm sorry it didn't work out.
Now, that's interesting. Factory reset didn't change anything.
Sorry for reply to self, but I was less than clear, so - help?
My next step would be to try to unlock the bootloader, then flash CWM and see if anything can be fixed that way; then, I would try flashing CM7 (or, more specifically, the Neutrino GT ROM) by CWM; then, I would try flashing it without. Is that a safe progression of attempts? Or have I possibly broken anything that would hard-brick it by any of these methods? And can you recommend any finer increments what I could do before / between / after those mentioned? I still have the option to apply an update in Recovery - is it possible, for instance, to put a .zip onto my SD that has 0 Byte MediaProvider files in it?
(I have thought about installing Neutrino for a while, and this seems to be a good time to flash it, as my data is cleared now anyways. To my understanding, this should not be any more dangerous than just re-flashing the Froyo that was there before, right?)
As an additional fact, ADB now doesn't detect any devices any more, even with Early USB. This could be because USB Debug is not a factory standard setting, though, as I reset it to factory defaults.
Also, the startup Moto screen behaves differently: It doesn't go to the point where the logo disappears in a flash, the background light switches off before that. As far as I can tell, the display still shows the animation, though, but it is not lit. Furthermore, the reboot seems to happen immediately after the animation has ended, and not 1-2 minutes later, like it was before the reset.
I would be grateful if anyone could explain what happened. To my understanding, a factory reset should clear /system, and the error started when I put some non-compatible .apks there, so I thought this would fix things. Is it possible something broke on the hardware side, when (for instance) 2.2.2 called a function that has had its parameters changes in 2.3.4?
[If a moderator reads this - does this qualify as a general Android question? I have no experience with different devices, so I'd be glad if you could decide if this thread has to stay here or if it can go to a sub-forum with a wider audience - General Android Q&A, for instance.]
Bump...
Success Neutrino up and running!