Related
Looked through the rooting guide and I have a question revolving around some testing I need to do. Please bear with me and I appreciate any assitance or advice.
Here is the issue:
When running both the Incredible and the Evo, Exchange 2007 will sync natively when encryption of the device is required. On other 2.1 devices, such as the Moto Droid, and the virtual devices, native sync will fail as it can't support encryption requirement. This is the same with 2.2 virtual devices.
Since the Evo or Incredilbe sync via ActiveSync and don't toss an error, I need to know if the mail database is actually being encrypted. I know that Android does not support full device encryption like the iphone or winmo devices.
I currenlty have a Sprint Evo for testing this. I want to keep the OS as close as stock as possible, so I can see what will happen with our users that purchase these.
1. If I root only, will I still have basically the stock image running, or does it load a custom ROM?
2. If it is replaced, can I put the stock ROM on the phone while still retaining root access.
3. I'll look around with a file explorer, but does anyone know offhand where the mail database are kept. This is the key as I need to know if this database is encrypted.
If anyone has other advice for me, I'm all ears. Thanks in advance.
GiantSloar said:
Looked through the rooting guide and I have a question revolving around some testing I need to do. Please bear with me and I appreciate any assitance or advice.
Here is the issue:
When running both the Incredible and the Evo, Exchange 2007 will sync natively when encryption of the device is required. On other 2.1 devices, such as the Moto Droid, and the virtual devices, native sync will fail as it can't support encryption requirement. This is the same with 2.2 virtual devices.
Since the Evo or Incredilbe sync via ActiveSync and don't toss an error, I need to know if the mail database is actually being encrypted. I know that Android does not support full device encryption like the iphone or winmo devices.
I currenlty have a Sprint Evo for testing this. I want to keep the OS as close as stock as possible, so I can see what will happen with our users that purchase these.
1. If I root only, will I still have basically the stock image running, or does it load a custom ROM?
2. If it is replaced, can I put the stock ROM on the phone while still retaining root access.
3. I'll look around with a file explorer, but does anyone know offhand where the mail database are kept. This is the key as I need to know if this database is encrypted.
If anyone has other advice for me, I'm all ears. Thanks in advance.
Click to expand...
Click to collapse
You can root without a custom ROM.
EVO does support EAS policies.
I am not able to answer #3 at this time, I am sure I will find out while exploring the EAS components.
GiantSloar said:
Looked through the rooting guide and I have a question revolving around some testing I need to do. Please bear with me and I appreciate any assitance or advice.
Here is the issue:
When running both the Incredible and the Evo, Exchange 2007 will sync natively when encryption of the device is required. On other 2.1 devices, such as the Moto Droid, and the virtual devices, native sync will fail as it can't support encryption requirement. This is the same with 2.2 virtual devices.
Since the Evo or Incredilbe sync via ActiveSync and don't toss an error, I need to know if the mail database is actually being encrypted. I know that Android does not support full device encryption like the iphone or winmo devices.
I currenlty have a Sprint Evo for testing this. I want to keep the OS as close as stock as possible, so I can see what will happen with our users that purchase these.
1. If I root only, will I still have basically the stock image running, or does it load a custom ROM?
2. If it is replaced, can I put the stock ROM on the phone while still retaining root access.
3. I'll look around with a file explorer, but does anyone know offhand where the mail database are kept. This is the key as I need to know if this database is encrypted.
If anyone has other advice for me, I'm all ears. Thanks in advance.
Click to expand...
Click to collapse
After following almost all rooting methods you should have a stock rooted ROM. After rooting you can flash a new stock rooted ROM anytime you want, the links are in the wiki that is stickied on the Android Dev thread. Also there is more info in the guide in my sig.
As far as encryption of mail files goes I have no idea, but would be interested to know this... Let us know if you find anything in your testing.
The phone I got for test had the OTA updates applied. Looks like no root for me now.
As soon as I find out anything, I'll post it around.
GiantSloar said:
The phone I got for test had the OTA updates applied. Looks like no root for me now.
As soon as I find out anything, I'll post it around.
Click to expand...
Click to collapse
Unfortunately for anyone that applied the OTAs before rooting, they now have to wait for the un-fix. There is a thread devoted to this in android dev. I don't have a link cause I'm on my phone ATM, but it should be on page 1.
webs05 said:
Unfortunately for anyone that applied the OTAs before rooting, they now have to wait for the un-fix. There is a thread devoted to this in android dev. I don't have a link cause I'm on my phone ATM, but it should be on page 1.
Click to expand...
Click to collapse
Right, saw that earlier when I was trying to figure out why the simple root didn't work.
forum.xda-developers.com/showthread.php?t=714157
Would link it, but guess I need a few more posts to prove I'm not a bot or spammer.
Hi,
I know there was done some work on dualbooting the HTC Dream, enabling you to launch a different OS of the SD card.
What exactly is needed to accomplish this? And was the methods used able to load a different kernel alltogether, or just lanch another useland using the kernel from your current ROM?
I have both a Dream and a Desire, and would like to try and get Meego running on one of them. (Maybe finding my way on the Dream, which is not my primary phone anymore, and then on the Desire when I have figured it a bit more out.)
MeGo uses the 2.6.34 kernel, which I believe several Froyo ROMS use too.
The first thing I will do, is to try to run it with minimal modification to the kernel found in an existing Dream ROM, o avoid adapting the Meego kernel to support the neccessary hardware, as the ARM-release is made especially for the N900, and probably doesn't have that wide a hardware support.
But where would I change the kernel to boot? I guess it is not really possible to modiy the bootloader in the device directly (uboot sure would be nice ), so I guess it has to be done in initramfs or similar? Not really familiar with how phones do this.
thats wt i wanted to try on my cliq too! Do u have the rom for meego?
There is no ROM of MeeGo, which is why i need to load kernel/userland from SD card. I have asked for the ARM-release of MeeGo here, but the reply wanæt very helpfull.
I'm sorry if this has been asked before, I've done a search and can't find anything.
I know there's a few dumps of WP7 roms on the forum. But my understanding is that these have been from the rom files rather than from a phone. My question is is there a way to get a copy of EVERYTHING in the rom/nand from a working WP7 phone onto a computer/drive? I know there's tools on this forum for editing WP7 roms, but again, my understanding is that those roms weren't ripped from a working phone, rather from the rom file.
I know someone has used a HTC TyTn and has terminaled into the bootloader to send commands to dump the rom. Is this possible with a WP7 deivce? Say the HD7?
Any advice would be appreciated.
Thanks
yes i believe ppl flash new roms to unbrand their devices, you should check the devices forum, bet ull find roms there..
puunda said:
I'm sorry if this has been asked before, I've done a search and can't find anything.
I know there's a few dumps of WP7 roms on the forum. But my understanding is that these have been from the rom files rather than from a phone. My question is is there a way to get a copy of EVERYTHING in the rom/nand from a working WP7 phone onto a computer/drive? I know there's tools on this forum for editing WP7 roms, but again, my understanding is that those roms weren't ripped from a working phone, rather from the rom file.
I know someone has used a HTC TyTn and has terminaled into the bootloader to send commands to dump the rom. Is this possible with a WP7 deivce? Say the HD7?
Any advice would be appreciated.
Thanks
Click to expand...
Click to collapse
the rom's here on the forum(except the one's for the hd2) are original stock rom's for wp7 phones that can be flashed on real wp7 phones (with the same vendor ID)
you can't dump the actual rom from your phone right now (maybe later,but it will def take some time)
ceesheim said:
the rom's here on the forum(except the one's for the hd2) are original stock rom's for wp7 phones that can be flashed on real wp7 phones (with the same vendor ID)
you can't dump the actual rom from your phone right now (maybe later,but it will def take some time)
Click to expand...
Click to collapse
What phone(s) can you actually do a dump of the actual rom from the phone right now?
I understand some phones have things like clockwork recovery or magldr installed and use that to write new roms to the phone. Can the same programs not read (or backup) the current rom?
puunda said:
What phone(s) can you actually do a dump of the actual rom from the phone right now?
I understand some phones have things like clockwork recovery or magldr installed and use that to write new roms to the phone. Can the same programs not read (or backup) the current rom?
Click to expand...
Click to collapse
I can only talk for wm/wp and only from wm (6.*) you can dump the rom using a tool that is installed on the phone .
if you had a jtag or something like that you could dump (read the ROM/NAND and copy it) almost any phone.
but a jtag is hardware and it cost money (lots of it) and you need to know exactly how to work with it and you would need to open your phone (till the last screw)
I don't know clockwork .
magldr is something like a second bios (not right , but for you to understand) that help to start the os (normally the spl/hspl will do that )
magldr is used only for playing tetris and to load android/wp7 to a phone that isn't build to run that kind of os
it can only load something , it can't dump a rom.
ceesheim said:
I can only talk for wm/wp and only from wm (6.*) you can dump the rom using a tool that is installed on the phone .
if you had a jtag or something like that you could dump (read the ROM/NAND and copy it) almost any phone.
but a jtag is hardware and it cost money (lots of it) and you need to know exactly how to work with it and you would need to open your phone (till the last screw)
I don't know clockwork .
magldr is something like a second bios (not right , but for you to understand) that help to start the os (normally the spl/hspl will do that )
magldr is used only for playing tetris and to load android/wp7 to a phone that isn't build to run that kind of os
it can only load something , it can't dump a rom.
Click to expand...
Click to collapse
What tools can you use in WM6.* to dump the rom? I've read an article where someone used terminal commands and did a dump through the bootloader. Is there another way to do it?
I know about JTags, and am not touching them!
My point with clockwork and magldr is that if you can write (load) android/wp7 to the rom/nand, surely you should be able to get it to read from it?
It seems like either there's no way to do it with wp7 yet, or at least I've not found a way. But I was thinking if you can't do it with a real wp7 device since there's no clockwork/magldr, then can you take a dump of an HD2 with wp7 loaded into the rom/nand?
I have searched for a samsung focus stock rom in the past but I couldn't find it anywhere? have you seen any one?
ceesheim said:
I can only talk for wm/wp and only from wm (6.*) you can dump the rom using a tool that is installed on the phone .
if you had a jtag or something like that you could dump (read the ROM/NAND and copy it) almost any phone.
but a jtag is hardware and it cost money (lots of it) and you need to know exactly how to work with it and you would need to open your phone (till the last screw)
I don't know clockwork .
magldr is something like a second bios (not right , but for you to understand) that help to start the os (normally the spl/hspl will do that )
magldr is used only for playing tetris and to load android/wp7 to a phone that isn't build to run that kind of os
it can only load something , it can't dump a rom.
Click to expand...
Click to collapse
Excuse me newbieness but if I'm getting you correctly, you're saying that it is possible for my to extract the ROM from a working Samsung Focus and then write it to my bricked Samsung Focus using a JTag?
Totally possible, theoretically.
The WM/WP OS image is only a piece of data saved in a flash partition, bootloader can read the content from the flash partition out and transfer bytes to PC (no need to care about the file system, just perform flash chip level read), but the question is you must know how to communicate with the bootloader and send proper command to it. And as I know in the shipped device, the ability usually will be removed from bootloader for security reasons (e.g. eboot is useful in development phase, but it must be removed from shipped device).
Yes, you also could use JTAG to read content out but due to the same reason, the debug port on the SoC usually also be disabled in shipped device (like Tegra, it has internal fuses to enable/permanently disable the JTAG).
UzEE said:
Excuse me newbieness but if I'm getting you correctly, you're saying that it is possible for my to extract the ROM from a working Samsung Focus and then write it to my bricked Samsung Focus using a JTag?
Click to expand...
Click to collapse
I think reading the OS partition when OS is running is impossible (frankly, I never verified it). Two reasons, first the OS partition should be locked by last phase bootloader or some early bootup codes in OS (just set the NAND controller in SOC), and since OS is running, many system files are in memory so the corresponding files should also be locked by OS.
It is safe to dump whole OS image in bootloader, or so-called recovery mode.
So someone basically has to install a custom bootloader on the device. Then again, if the NAND is locked, that wont be possible.
QPST and Memory Debug allow to download raw NAND and radio copy. i've succesfully one it (even found private info like passwords and contacts), but i don't know how to split it into partitions. Mb anyone will help?
Maybe starting a new topic about it here would help. Might attract the attention of some other devs.
Useless guy said:
QPST and Memory Debug allow to download raw NAND and radio copy. i've succesfully one it (even found private info like passwords and contacts), but i don't know how to split it into partitions. Mb anyone will help?
Click to expand...
Click to collapse
Could you describe how you do that?!
How to do this?..
Hi Fellow old and New Devs,
The title suggests it all. I have four questions that I think ALL newbies want to understand. I would try and explain them, but as I am just coming out of the newbie stage, I'm sure people would prefer an answer from a experianced Dev.
When answering a question please put the Question Number. Feel free to answer only one or two of the questions, I'm sure other people will cover your missing fields of knowledge.
Here they are:
1. What is rooting? Can I root my device (HTC Buzz Wildfire) and keep the stock interface? Will I loose my data?
2. What do all these Dev's mean by Recovery? What are they, why are they needed?
3. What is a ROM? Do I need to be rooted for a custom ROM? How can you trust them? Will I loose my data when installing a custom ROM?
4. What is a Kernal? How are they Different to ROM's? Should I change from the stock Kernal?
I know this is a tall order and you could write a book on the topic, but please could you write a short (a couple of sentaces will do) paragraph on each question you choose to do.
When we get enough understandable answers I will edit this post publish the Final answers for other newbies in the future.
Also feel free to enter the poll! As this is a Dev site I presume one of the options will have the most votes but we will see....
Cheers for any contribution in advanced.
th3ant
th3ant said:
Hi Fellow old and New Devs,
The title suggests it all. I have four questions that I think ALL newbies want to understand. I would try and explain them, but as I am just coming out of the newbie stage, I'm sure people would prefer an answer from a experianced Dev.
When answering a question please put the Question Number. Feel free to answer only one or two of the questions, I'm sure other people will cover your missing fields of knowledge.
Here they are:
1. What is rooting? Can I root my device (HTC Buzz Wildfire) and keep the stock interface? Will I loose my data?
2. What do all these Dev's mean by Recovery? What are they, why are they needed?
3. What is a ROM? Do I need to be rooted for a custom ROM? How can you trust them? Will I loose my data when installing a custom ROM?
4. What is a Kernal? How are they Different to ROM's? Should I change from the stock Kernal?
I know this is a tall order and you could write a book on the topic, but please could you write a short (a couple of sentaces will do) paragraph on each question you choose to do.
When we get enough understandable answers I will edit this post publish the Final answers for other newbies in the future.
Also feel free to enter the poll! As this is a Dev site I presume one of the options will have the most votes but we will see....
Cheers for any contribution in advanced.
th3ant
Click to expand...
Click to collapse
Okay, from the best of my understanding, here we go:
1: Rooting. To understand this, we must consider a computer, running linux, windows, or mac. In windows, the "Administrator" account is similar to the root account in linux and mac. Basically if you have root privileges in a system, you can modify every part of the filesystem, as well as perform any tasks the system is equipped to handle. Basically achieving root on an android device means that you can unlock the ability to flash roms, mod, and otherwise hack your device any which way you like. Nearly every model of android device has been rooted, so in most cases, yes you can root XXXXX phone. Also, since you're just gaining privileges, you can root without losing any data, apps, or settings.
2: Recovery. This is a long standing concept in SoC/Embedded device hacking. Basically it is a minimal operating system that performs some very basic, but very important tasks. The reason for it is so that you can write to the necessary areas on the NAND, which would be "busy" while android is booted. This offers a way to access the necessary partitions and write data to them while the data is not being accessed. It's also useful for backing up your NAND. Hence the name "nandroid."
3: ROM. By definition, it means "Read Only Memory." This is a chip on the board. ROM has evolved over the years. It started out as a chip that was sensitive to UV light. The earliest ROMs were "flashed" to a device by stenciling out the pathways and exposing the chip to UV radiation. Nowadays, we have fancy EEPROMs instead, which stands for Electronically Erasable Programmable Read Only Memory. This means that you can "flash" the chip by means of software, namely via Recovery mode in our case. Different ROMs have different features. They are all variations on source code made available by AOSP, or the android open source project. Some projects have their own code tracking, such as CyanogenMod. In most devices, you must be rooted to be able to install a ROM, however it is not explicitly necessary. A bit vague, I suppose. Specifically the tablet I own, the WITS a81e, you can flash a ROM to it just by putting the correct files on the TF card. This is not very common with phones, however. Flashing any rom that is not just a newer version of your current ROM will require a full format. For instance, if you have cyanogenmod and switch to a Sense or Blur ROM, you must format, but if you update from CM6 to CM6.1 you will not need to wipe. How can you trust ROM's? Well the best way to know is to either roll your own, or go with CyanogenMod, as their source is freely and easily available for scrutiny and improvement, along with a nice changelog tracker.
4. Kernels. A kernel is basically the most low level part of an operating system. It interfaces directly with the processor and provides all instruction for operation. Linux is technically not an operating system, it's a Kernel. The different distributions have the Linux kernel, and use their own different User Interfaces. Different kernels in android devices can allow you to overclock. There are many choices in kernels, and the features they offer. Some features are BFS/CFS which is the priority scheduling of processes. Some kernels allow you to charge your battery differently and conserve life. These are often called battery kernels. Also, some kernels unlock extra multitouch points in certain devices. There are different versions of the linux kernel, with many improvements with each iteration. Currently, the latest kernel available that I know of for android devices is 2.6.37. The froyo default kernel was a 2.6.32. I wish I knew a bit more about kernels, however this is about all I know. Perhaps someone could help us out and expand on this a bit?
Brilliant answer not too complicated... let's see what others say....
Sent from my HTC Wildfire using XDA App
What he said...
Pyroboy1080 well said...
That pretty much covers it.
thx for the infos..
Agreed. Thanks for using the poll!
nothing to add on that, as we used to say "merci beaucoup"
Can't ROM
Gotta be something stupid......
Can't install 2.2 or 2.3. Tried two different ODIN flashers. When I do the reset I do not get the triangel with downloading in the center. I'm rooted, Have ROM Manager, Superuser, Root Explorer, Super Manager, I'm unlocked.
I have Android SDK, Congnitive 4.1, NPS, Samsung Kies,SGH I897 USB Drivers, What else? I think I have it covered. In any case I never get the download . Even if I do a "ROM Manager Install fron SD Card, the result is a screen, blue at top and yellow at bottom with the last line saying "Installing Multi- CSC. I can let it run all night, no change in ROM. Does the Captivate sold by ATT have some kind of block or filter keeping me from updating?
Current firmware is 2.1 update 1, baseband I897UCJH7, Kernel 2.6.29 [email protected] #2, Build ECLAIR.UCJH7
Thanks
To better answer your question, I first need to know what type of device you're using...
fxstsb said:
Gotta be something stupid......
Can't install 2.2 or 2.3. Tried two different ODIN flashers. When I do the reset I do not get the triangel with downloading in the center. I'm rooted, Have ROM Manager, Superuser, Root Explorer, Super Manager, I'm unlocked.
I have Android SDK, Congnitive 4.1, NPS, Samsung Kies,SGH I897 USB Drivers, What else? I think I have it covered. In any case I never get the download . Even if I do a "ROM Manager Install fron SD Card, the result is a screen, blue at top and yellow at bottom with the last line saying "Installing Multi- CSC. I can let it run all night, no change in ROM. Does the Captivate sold by ATT have some kind of block or filter keeping me from updating?
Current firmware is 2.1 update 1, baseband I897UCJH7, Kernel 2.6.29 [email protected] #2, Build ECLAIR.UCJH7
Thanks
Click to expand...
Click to collapse
didn't know where to ask this?
hello, everyone..
i have some questions, i'm hoping some of you can anwser.
I used unrevoked to root my htc desire. after that, I used alpharev to gain s-off.
everything went fine, i got the joker, the white screen that lets me pick different options..
now Í tried all those options, nothing works.
I've been searching all night for a solution, and it seems my recovery boot and rom are missing? and what I came across is installing ANDROID SDK tools, and then run fastboot to recover an image. So I installed SDK tools, but fastboot doesn't run, it says some .dll driver is missing. in the platform-tools map is that .dll driver, should i move it?
Can someone get me a step by step tutorial on how to make my desire work again? Im kind of a noob, all I needed was to make a screenshot..
Thanks in advance, it would be appreciated so much..
Pyroboy, I'm using a Samsung Captivate. In another thread someone lead me to "All in One Toolbox". The other stuff is just stuff. That allowed me to install my ROM.
Crash course about root and roms:
I keep seeing a lot of people make comments like "I flashed xboarders rom so I could have root and then flashed CM7. Everything working great." That's not really the way it works. It doesn't hurt to do that, but you're adding an uneceasary step. Lets say you use Superoneclick, what that does is roots the stock rom you have in place. For now it works with our phones on Froyo and not on GB. So what are our options to "gain root" with GB? We have to flash an already-rooted rom. But understand that the root privileges are built in to the rom. Flashing xboarders rom or any other rom doesn't "give you root" for the other roms you might flash, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you flash CM7 (another rom that provides root access to its system files) then you have a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Root doesn't "stick" between roms, so flashing one rom to "gain root" before flashing another doesn't really help all that much. Root privileges are built in to the rom.
If you want to unroot GB, then browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And just a friendly reminder to PLEASE remember when flashing from one rom to a different rom: WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7
Nice buddy
I've asked a couple of n00b technical questions that nobody would answer. Like, "does the 'ROM" image contain the linux portion of the run-time?". Since "root" apparently means obtaining unix root privilege at the linux layer (again another question I've asked that nobody answered), and root follows the ROM, then I will add 1+1 and say the ROM contains the linux layer.
As a side note, a ROM is a piece of silicon (where I used to put my embedded code) that hasn't been manufactured for over a decade, so the overloading of that term is still tripping me up.
Nobody on this forum is responsible for technical training. I've looked at some android books on Safari, and all I find is UI stuff. I can't seem to find driver and IOS level stuff. Anyone know of a book about that stuff? It appears Android mostly goes thru JNI, so maybe I need to get on a JNI forum to understand how JNI connects to the linux drivers?
I could care less about app dev - I want to figure why my phone crashes.
Thanks,
-BobK
What most people mean nowadays when they refer to a ROM is a ROM image, flashable or otherwise copyable into the partitions that are set up in the phone's non-volatile RAM.
Yes, the ROM image contains Linux -- bootloader, kernel, drivers and a bunch of binaries like "busybox", dalvikvm (the dalvik virtual machine), dexopt, dhcpd, vold and so on.
EDIT: namklak: since it sounds like you know something about Linux already, you really should learn about ADB so you can login to your phone and look around. You should probably make sure you have a rooted ROM so you can run as superuser and look through / and /system/etc and /dev and /sys.
namklak said:
I've asked a couple of n00b technical questions that nobody would answer. Like, "does the 'ROM" image contain the linux portion of the run-time?". Since "root" apparently means obtaining unix root privilege at the linux layer (again another question I've asked that nobody answered), and root follows the ROM, then I will add 1+1 and say the ROM contains the linux layer.
As a side note, a ROM is a piece of silicon (where I used to put my embedded code) that hasn't been manufactured for over a decade, so the overloading of that term is still tripping me up.
Nobody on this forum is responsible for technical training. I've looked at some android books on Safari, and all I find is UI stuff. I can't seem to find driver and IOS level stuff. Anyone know of a book about that stuff? It appears Android mostly goes thru JNI, so maybe I need to get on a JNI forum to understand how JNI connects to the linux drivers?
I could care less about app dev - I want to figure why my phone crashes.
Thanks,
-BobK
Click to expand...
Click to collapse
If you're familiar with Linux then an Android ROM is basically the equivalent of a Linux distro. Its a customized version of Android that contains the Linux-based OS along with whatever modifications and default apps the developer wants to include to give it its own flavor. The name "ROM" is a bit of a misnomer since most all custom android ROMs give the user root access to the system partition. Its no longer "read-only memory" if you have read/write access. The first time I heard the term ROM used this way was in reference to copies of old Nintendo games ROM cartridges that could be run in an emulator on my computer.
Not sure about books to direct you to.
G2X CM7
Most "so-called" doesn't read. Maybe it's easier for them to post/start new thread rather than reading. They don't even care where they pot as long as they can ask, and sadly, it's the same question over and over again.
If you check Q & A (even General and sometimes Development), there are more than 2 root questions in the first and/or second pages.