I switched over exclusively to linux recently (Xubuntu 9.10 Karmic for those curious), and the only problem I've been having is a way to sync up my Tilt to my laptop which is running said linux. I don't particularly care for calendar/contact sync, just enough to access the flash programs here will be good enough. Any thoughts?
For a second I thought you had Ubuntu installed on your Tilt and got all excited.
There are two options I know of:
Use Pof's HTCFlasher, an open source linux RUU tool. It is supposedly compatible with all Kaiser bootloader versions.
Rename the ROM or radio you want to flash from RUU_Signed.nbh to KAISIMG.nbh. Place this on the root of your MicroSD card with a card reader, put the MicroSD back in the Kaiser, manually enter bootloader (hold camera and power buttons), and follow the instructions it presents you with.
Related
Do any of you have a program that I could use to sync my phone to my Computer via usb? I've tried several versions of Tera Term with no success. I reached the point where I was ready to pull all of my hair out and then I remembered... I don't have anyway. Oh well. Please help I really want to upgrade my rom but I want to back up the old first. Thanks, Vern.
i think i don't understand what you're trying to do!?
Don't you use ActiveSync for Syncing with your PC?
And wtf is Tera Term???
This is what I'm trying to do:
Originally Posted by kdenninger
To back up the firmware on the MDA to an SD card (a VERY GOOD IDEA if you intend to fool around with new firmware!)
1. Get a 128MB SD card. They're cheap - under $20.
2. Insert said card.
3. Go to http://forum.xda-developers.com/viewtopic.php?t=37386 and download the aWizard utility. CID-unlock your phone. (You only need to do this ONCE, even if reflash in the future.)
4. Get a terminal program that can speak over the USB port. There is a patched version of Terraterm out there, along with a few others. You need a way to connect to the device over the USB port as an ascii terminal.
5. Turn off the phone.
6. Holding the CAMERA key, press the power button for 2-3 seconds. Continue holding the CAMERA key until it comes up in the tri-color screen.
7. Connect the USB cable. Wait until ActiveSync tries to start. CTRL-ALT-DEL Windows and kill the process wcescomm.exe (ActiveSync's communication driver)
8. Now start your terminal program and point it at the USB port. Hit RETURN and you should get a command prompt. You are now talking to the phone's boot loader in terminal mode.
9. Type "r2sd all" and hit RETURN.
10. If you get a security level violation, you DID NOT CID-unlock the device. Go back to step #1.
11. The ROM image (all of it) will be written to the SD card. Several messages will be displayed while this is in progress. Note that this is NOT - I repeat - NOT - a filesystem-formatted dump - it is a RAW image of the ROM with some checksum information included. Anything on the SD card will be destroyed - don't do this with a card that has data on it you care about!
12. You can stick this card somewhere to be used for restoring. If you want to save the image off the card to your computer, stick the SD card in your computer and then dump 128MB of the card starting at the front (the actual dump is about 80mb but will always be less than 128MB, so that's "safe".) You will need a tool like "psdread" or any other tool that can do byte-level I/O to the SD card in your PC's reader for this.
To restore a SD-card image dump to the Wizard:
1. Write the image to the SD card. Again, this is NOT a filesystem - its a RAW image! Unless you saved the image to the card from the Wizard initially you will need a tool that can do a raw write to the SD card in your computer.
2. With the Wizard OFF, insert the card into the SD slot.
3. Hold BOTH the CAMERA and VOICE keys and press the power button for 3 seconds. Release POWER.
4. Look CAREFULLY at the Wizard screen. The backlight WILL NOT BE ON! It will tell you to press the VOICE button if you wish to restore the SD card image. This message only appears for a few seconds and the backlight is OFF! If you wait too long you will end up at the tri-color bootloader screen. Press the VOICE button (if you still have it down, let up on it then press again.)
5. The restore will run. Note that the backlight IS NOT ON during this process! You may need a flashlight (or very bright ambient light) to be able to read the progress meter.
6. When the process is complete it will tell you to press "any key". Do so and you're back in the tri-color bootloader screen.
7. Turn off the Wizard with the power button. When you turn it back on, it will hard reset just as if it was brand new off the firmware you just restored.
Note that this is the ONLY way to recover from a bricked phone if you try to load the wrong firmware file using one of the "forcible" methods (e.g. aWizard) on a non-CID-unlocked phone, and have bypassed the normal protection methods as ActiveSync cannot get back in there under these circumstances.
I strongly recommend that if you're going to futz with firmware, that you get yourself a 128MB card, make one of these dumps, and TEST the restore before you play around. This will recover from almost any botch - the only exception is loading a firmware file via some means (e.g. "aWizard") that the phone cannot execute at all.
Note that I do not know if this will get around the "boot loader version is too high" problem - I'm not willing to try it until I have an official T-Mobile update with a newer boot loader.
This same method for both dump and restore works on the SDA as well.
13. Overclocking the MDA (do so at your own risk!)
Quote:
Originally Posted by Scaw
Use Smartskey, read about it in this article on my HTC Wizard Blog. No specific ROM required, overclocking integrated. You need to download OMAP Clock seperately, it is available from the same article. A small tutorial in PDF format is included in the .zip with Smartskey. Don't forget to remove the ";" (without the quotes) at the beginning of the overclock settings in the configuration file!
How fast you can clock it depends on your device, it's just a matter of trial and error. 240 seems to be safe for the majority of HTC Wizard owners. No need for extra tools to wake overclocking up after a soft reset or standby. I haven't noticed severy battery drain, I can easily use my device a whole day and come home with the batterie well over 50% charged.
It's just a great little program. The integrated overclocking comes as a bonus to the tweak that the program was actualy made for, remapping buttons so you can open the start menu without using your stylus and close programs without using the stylus.
Have a look around on the HTC Wizard Blog, there is lots of other stuff that you may find useful.
And Number 4 is WTF Tera Term is. Thanks.
Hi,
Just got an Xperia, and I'd like to follow the tutorials on flashing the WM6.5 OS onto it.
My problem initially is that all my PCs run Mandriva Linux, not Windows, which means that the .exe files etc provided won't run on my machine.
Is there a solution for this problem? Obviously I have no ActiveSync etc and although I can still connect the phone via USB, I'm a little nervous about trying to work out how to do this off the cuff - don't want to end up with a brick after all!
Cheers
Dave
If you have just got it, then start searching and reading first !!!
sticky threads have the most information you need.
anyway, quick response, hardspl with no windows i don't think so, but rom flashes yes you can with the microsd method.... you'll find info everywhere....
I recommend you to use a xp boot cd or other windows boot cd that can mount the OS in your pc or to make a partition with windows...
Because to do a hard-spl you WILL NEED WINDOWS....Activsync from microsoft...Shuold by active and running conected to your xperia of course...
For roms flashing you can use MicroSd method so not problem with your pc OS...
READ and Study a lot after doing....ANYTHING
Wish you Luck
Thanks guys.
I had already seen and read through the points on using Micro SD cards for the ROMs, but hadn't been able to locate anything on doing the Hard SPL any way without using Windows. Thanks for clarifying what I thought was the likely answer.
Looks like I'll be spending my lunch hour productively at work next week...
the easiest way for you will propably be :
1. Go get Virtualbox (free!) or VMWare Workstation/Server
2. Setup a new virtual machine.
3. Install Windows XP in this machine.
4. Install virtualbox guest additions in virtual machine.
5. Install Activesync
6. Connect your X1 to the usb while virtual machine is on focus.
7. Put Hard SPL on that sucker.
That's how I did it and have done it for some friends.
Alternatively just do it on one of your buddie's pc who has got Win.
It takes only few minutes.
regards
(That should be DRC83, I *swore* I changed that)
I successfully rooted my phone following the tutorial, although at some points I took a vague leap of faith; there are some very minor things that are not included in the tutorial. I suspect part of this is to rule out people (like me) who have zero *nix experience, but it can be alarming.
I was unable to get the most recent (as of today) Cyanogen mod to work (1), so I downloaded DRC83. (I do still have root).
I *have* searched the forum, and I have searched Google. My problem is that a great deal of what I'm finding is dated, requires hardware I don't have (a machine running *nix) or software I don't have [Cyanogen, crutch lite (which is no longer on the market)].
When I try to get into console mode, it doesn't work. (2)
Is there any way for me to run my apps from my SD card using a Windows machine and DRC83? I've gotten to the point now where I no longer trust my searching abilities.
I have:
T-mobile G1 bronze
A new 8 GB class 6 MicroSD card
AppManager (not Apps2SD? Where is this program?)
Build DRC83
sdparted.txt (on the MicroSD)
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Windows OSs on desktops
A MicroSD reader (so I can theoretically do anything except booting the phone from the PC)
(1) - When I downloaded/installed this build, it would just stay on the G1 screen.
(2) - I can successfully power on the phone holding the home and power, but then I just get the exclamation point. Holding alt-x or tapping them and hitting return isn't doing anything.
The guide here http://forum.xda-developers.com/showthread.php?t=535232 references Cyanogen 4.0.2 which isn't even at that link.
I apologize, I know y'all go over this all the time, but I really did search and my google-fu is failing me.
not sure i fully understand ur problem but if u have cm 1.4 recovery or amon ra recovery (do u?) u should just follow this guide http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
u shud be good to go afterwards. hope this helps at all
Depending on what guide you followed it should be step by step. This is the best guide out. http://androidoverdrive.com/viewtopic.php?f=11&t=7. And as long as your card is partitioned then apps2sd is automatic and you don't have to do anything.
I tried that, and it worked really well, but I just can't get Cyanogen to run on my phone for some reason.
I got all the way through flashing that image, but all that happens after that is the screen goes black.
Thanks, though.
:-/
Anyone else have any ideas how I can run my apps from my SD without running a ROM that just won't run on my phone for some reason?
Hate to break it to you, but Cyanogen's ROM is *not* the only ROM that supports Apps2SD. Almost all the ROMs you'll find the in the development section support loading apps from the ext partition by default. If Cyan's ROM doesn't work, have a look at Dwangs or Enomthers.
The ext partition can be created any way you like, using Amon RA's recovery, or on your PC using Paragon Partition Manager (although I'd highly recommend gparted from a live Ubuntu CD).
AdrianK: thank you; I will try that!
Everyone else: I did eventually get Cyanogen's newest mod to work. I swear I ran through the set-up like six times. >.<
I have definitely got the blue angel. It is an O2 Xda 11s.
I have downloaded the how to flash your BA pdf by D-Two, and followed the instructions. It gets through to the stage where it's about load the software onto the phone, and then it quits saying that he phone is not the appropriate model.
device information
Operator version: PDAViet.net
ROM version: 6.01.10 VH
ROM date: 07/08/08
Radio version: 1.06.00
ExtROM: diamond (01)
RAM size: 128 MB
Flashing eyes: 32 MB
Storage size: 60.3 MB
At present I have windows mobile 6.1.
And suggestions please?
for upgrading, you use the MAupgradeut_noID.
that program avoids country id errors but it was originally made for the magician, hence MA, whereas the original BA upgrade utility is called BAupgradeut.
that is why you get that error. you have to put the device into bootloader mode before connecting it to the pc and before starting maupgradeut_noid, that way, you avoid the device id check.
make sure to follow the correct upgrade procedure, found here: http://forum.xda-developers.com/showthread.php?t=630416
These are the instructions I used;
Temporarily remove your SD Card (it may work for you with the SD card still in your BA, but you may not be able to enter USB mode when cradled).
Put your device into Bootloader mode by pressing and holding the "Power" & "Record" buttons, and then press the Reset Button. Help me with this step
Connect the phone to the sync cable/cradle. sarcasm ahead Note: Did you see a sign out in front of this point that said: "You can flash using BlueTooth connection?" You know why you didn't see that sign? Because you can NOT FLASH using BlueTooth!
Now you can execute the installer file. (something like "MaUpgradeUt_noID")<--------------- Used This
Here is the screen just before boarding the software.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba1.png
And here is the error message.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba2.png
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Chef_Tony said:
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Click to expand...
Click to collapse
yep, you were right,,,,,,, BUT same error message;
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/xda4.png
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Chef_Tony said:
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Click to expand...
Click to collapse
Okay yes, I should have said this. I am using windows seven on a Lenovo N500 4233 32g. The problem is, trying to get hold of an XP machine. Have you tried running this programme in compatibility mode? I will have a look at your instructions and see where I get to.
Thanks for your help,
Is d-two's manual, the HTC service manual in you sig?
no, it is to be found here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
compatibility has nothing to do with it, neither has the xp mode or any virtual machine, because there must be suitable windows 7 drivers present. but i cannot help you with his tutorial, since i use windows xp for flashing and have never successfully used windows 7 for flashing.
the htc service manual in my sig is the official htc manual for hardware repairs, you can learn to disassemble the device there and have a list of spare parts
My kids received Nook Color readers for Christmas, and like everything, they look to Dad to optimize them.
I was going to try rooting, but a couple of things remain unclear:
- Do I have to 'auto-noot' to root the Noot, or are there other options (other tools, manual rooting, etc.)
- Should I upgrade the software to 1.0.1 prior to rooting or not?
I tried to give auto-noot for 1.0.0 a quick run, but I couldn't get the SD card to boot (and a check revealed that I had two FAT16 partitions, one with the appropriate images and the other with the files needed). I'm assuming it's because the card I have might be too slow (portal recommends Class 6 or greater, and the card I'm using is a cheapo card I got with an earlier phone that I'm not too sure of).
Thoughts? Tips?
I upgraded mine to 1.0.1 first then rooted.
What OS is on your PC?
If Windows, did you use Win32DiskImager to write the image to microSD card?
Take a look at here for different ways of rooting here http://www.nookdevs.com/Portal:NookColor#Rooting
The easiest and the way I rooted is below which I borrowed from http://blogkindle.com/2010/12/read-kindle-books-on-nook-color/
Here’s what you need to do:
1. Before rooting make sure that you’ve registered the device with B&N as it might not work after rooting.
2. Download nooter that corresponds to you Nook version. You can check your Nook version by pressing Nook button, selecting “Settings” >> “Device Info” >> “About your NOOKcolor” >> Software version:
--- for 1.0.0 – GabrialDestruir’s auto nooter 2.12.15 file 15 Dec 2010
--- for 1.0.1 – GabrialDestruir’s auto nooter 2.12.25 file 25 Dec 2010
3. Unpack the file
4. On Windows use Win32DiskImager to write the image to microSD card (please note that all data on the card will be lost). For Linux or Mac, check out NookDevs.com for detailed microSD imaging instructions.
5. Completely power off NOOKcolor by holding the power button until the screen blurs and “Power off NOOKColor” dialog appears. Select “Power Off” and wait for the device to shut down completely.
6. Turn device face down and open the microSD card container in the lower right corner. Push the card in with metal contacts facing down.
7. Connect the device to your computer via USB cable. The device will power up and book from the SD card but the screen will not turn on. This is normal.
8. After about a minute your computer show detect the new device. This means that the rooting is complete. Your Windows computer will complain about missing drivers. This is normal.
9. Disconnect the USB cable and remove the card from the reader.
10. Power cycle it by holding the power button for 20 seconds and then releasing it. The press the power button briefly to power the reader on.
11. As the reader boots you will see a red splash screen.
12. Once the reader boots, you will be prompted for you Gmail account (as usually with Android) and some initial settings. This will only happen once.
13. As you open the extras folder you will see that it now contains Android market icon and some extras (Youtube, Gmail, etc)
14. You can now start the market app and download other apps that you like. You will need to reboot the device for apps to appear on the extras page. The apps themselves can be used right away just as with usual Android apps.
I would look for the thread in the android development section for auto nook 1.01. Update the OS to 1.01, then do the nook-ing process. Its all laid out there in the opening post.
I would definitely root your nooks to get the most out of them.
I'm guessing he meant Auto-Nooter 2.12.25 (1.0.1 Only), which the thread can be found here
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
giantcrazy said:
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
Click to expand...
Click to collapse
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
clockcycle said:
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
Click to expand...
Click to collapse
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
giantcrazy said:
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
Click to expand...
Click to collapse
Ah, totally forgot about that.. Well glad you got it sorted.
-CC