Tera Term for Windows XP? - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Tera Term for Windows XP? - 8125, K-JAM, P4300, MDA Vario Software Upgrading

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.

Related

Problem on rooting my G1- RC9

I bought it from Germany, and the verison is RC9
I had tried to follow the How to guide from this forum, but i receive the following message after enter to the rainbow screen
1. Serial0
2. 0020288 and Not allowed
I have also try to load in RC7, RC8, and even RC 29, same result. Is it the MicroSD card issue? i am using the one it bundled, formatted it as FAT32..but just by passed that grey screen
I appericated with any comments or suggestion from any of you
Thanks

sorry, i mean i could NOT by passed that grey screen...
please help...

jsonseven said:
sorry, i mean i could NOT by passed that grey screen...
please help...
Click to expand...
Click to collapse
2 things I would check. Make sure the files downloaded properly (check the md5) and double check that the card is formated to Fat32.

my card is formatted as Fat32, and the file Md5 is (2F02DD9A3B7C7F2FE058047B9C7A0245)
does it look ok to you
Thanks for you reply

More info: my G1 is
Firmware = 1.1
Baseband version = 1.22.14.11
Kernel version = 2.6.25-01845-g85d4f0d [email protected] #27
Build number = TMI-RC9 128600
Please help... thanks

jsonseven said:
my card is formatted as Fat32, and the file Md5 is (2F02DD9A3B7C7F2FE058047B9C7A0245)
does it look ok to you
Thanks for you reply
Click to expand...
Click to collapse
looks like your MD5 hash there is the leaked .nhb file used for the UK version to get root.
are you placing the WHOLE .zip on the memory card or just the .nhb file (which I belive it should just be the .nhb file like it is for the US version)
so you got the whole card set to FAT32 which is good
then you placed the .NHB file into the ROOT of the memory card (no folders)
You held down the camera + Power buttons and got into the bootloader
-Did you see the rainbow screen?
-Did you see the grey screen that said "press action key to start update" ( action key is the trackball)
and after it updates .. if it did or does go that far (it will say ok next to each line and completed) the you reboot the phone by pressing the Send + End + menu keys at the same time to reboot the phone from that grey screen.
NOTE: this is for the US version .. I am not really sure if this applies the same for the UK version ...
ALSO I found this for the UK version .. its a little different for the key presses .. not sure if they are right but here they are
1.Copy image file DREAIMG.nbh to the SD card
2.Turn the device power off and insert SD card
3.Hold Camera button, and press Power button to entry Boot loader mode
4.Press Power button to start upgrade procedure (the US version is the trackball as action key .. not sure if it makes a difference)
5.After it finishes, press the trackball and perform a soft reset by pressing "Call" + "Menu" + "End" to reboot. (not sure why you hit the trackball the US version doesnt require that .. just the Send+End+menu to reboot)
THEN the rest that you need to follow after it flashes (if you get that far) is all on this link here
http://android-dls.com/wiki/index.php?title=Rooting_Android
steps are from that site
1.Restart your phone
2.At your phones desktop hit the <enter> key twice and then type "telnetd" and press <enter> again
3.Download an Android Telnet client and connect to localhost. If you are unable to connect, try steps 1 and 2 over again until you can.
4.you now have root!
intersetingly ... this method there is no recovery image or spl to download anywhere in this like there is in the US version ... may just the differences between the two phones BUT if you really wanted to compare or take a look at the US version to decide for yourself then go here:
http://forum.xda-developers.com/showthread.php?t=442480
hope that something in here helps ya

<My answer in blanket>
are you placing the WHOLE .zip on the memory card or just the .nhb file
(I unzip it, and put the .nhb file into the ROOT of SD)
You held down the camera + Power buttons and got into the bootloader
-Did you see the rainbow screen?
(Yes)
-Did you see the grey screen
(Yes, but after "Checking", i received a error message say, "0200230 Not allowed" message)
Hope it help, Thanks brilliant

OOOOOOOH... try this: http://forum.xda-developers.com/showthread.php?t=485364

Thanks for your reply
I had tried that too, but stuck at 4. Select Dream from the list of devices, Click "Get SD Card Serial from WINCE Device"
the program close after i click on the "Get SD ..." button
I tried to do it inside G1, and also card reader..
by the way, my SD card is manufactured by Kingmax

jsonseven said:
Thanks for your reply
I had tried that too, but stuck at 4. Select Dream from the list of devices, Click "Get SD Card Serial from WINCE Device"
the program close after i click on the "Get SD ..." button
I tried to do it inside G1, and also card reader..
by the way, my SD card is manufactured by Kingmax
Click to expand...
Click to collapse
I'd love to help here, but I have no experience with that method. I would try searching that thread to see if anyone else has that same problem. If you can't find anything there, start a new thread here describing your problem in the title (it will attract people who have an idea or know the answer).

How to check my SD card's CID? i just cant run the Qmat...

Okay pardon the bad formatting, I copied this from a site I googled and saved it as a html file. Basically you get your device rooted without Qmat or any WinCE device:
1. insert Transcend 8GB sd card into G1 (sandisk may not work. Lower capacities will work and may even be better. Other makes will also work)
2. download Terminal Emulator from the market and open it on G1
3. type “cat /sys/class/mmc_host/mmc1/mmc1:*/cid” (without the quotes), and keep the code given (something like 1c5356555344202010041c71f0008c5e)
4. Reverse the code byte-wise ( my 1c 53 56 55 53 44 20 20 10 04 1c 71 f0 00 8c 5e became 5e8c00f0711c0410202044535556531c)
5. Overwrite first two digits with 00s: 008c00f0711c0410202044535556531c
6. On your pc browser, go to http://revskills.de/pages/goldcard.html, paste your code and email address and hit continue (while thinking “thank you viperbjk” or donating some money)
7. format sd card to fat32 (may be good to rewrite partition table)
8. download RC7 from http://koushikdutta.blurryfox.com/G1/DREAMIMG-RC7.zip and extract
9. download goldcard from your email address (goldcard.img, less than 440 bytes)
10. copy DREAIMG.nbh to SD card (CASE sensitive! Filename very important)
11. unmount /dev/sdb1
12. type in terminal: “sudo dd if=goldcard.img of=/dev/sdd” (result: 0+1 records in, 0+1 records out, 384 bytes (384 B) copied) (assuming your sd is in /dev/sdd)
13. pull out sd card (now goldcard!) and insert into g1
14. hold camera button and press power button once
15. wait until the bootloader finds the rom and push power button when prompted. (if you do not see this instruction, you have done something wrong)
16. Continue with flashing recovery, HardSPL, RC8 etc...
If you do it exactly according to the steps listed, you should get your device rooted. I know mine worked
EDIT: Bleh, formatting was so bad, I had to fix it. Anyway, once you've done rooting, you should look for ways to change your keyboard layout. The German QWERTZ drove me nuts so I remapped mine to good ol' QWERTY
EDIT2:
How to write the raw sectors without having Cygwin or a Linux device:
- download HxD Hex Editor and install
- open program and go to "extra" and then "open disk"
- choose physical disk and then the removable disk. that is the same as your memory card. I've you don`t know with one it is. just remove the card and restart the program and you will see witch one is disappeared.
- uncheck open as readonly !!!!!!!
- go to "extra" again and the open disk image.
- open the goldcard.img witch you have created from Viper BJK website.
- press ok (512 is fine) en then "select all" and "copy"
- go to the removable disk tab and select offset 00000000 till offset 00000170 go to "edit" and then past write.
- save it

You can't create the HTC GoldCard with your G1 or with a card reader. You need a phone running Windows Mobile (WindowsCE). It's the only thing (that I know of) that can write the goldcard.img to the correct RAW sectors.

torturedsoul802 said:
You can't create the HTC GoldCard with your G1 or with a card reader. You need a phone running Windows Mobile (WindowsCE). It's the only thing (that I know of) that can write the goldcard.img to the correct RAW sectors.
Click to expand...
Click to collapse
You can actually. The process has been documented on the forums but it's in the middle of one of the threads linked earlier. Or you can just follow the guide I posted above. That'll guide you through the entire goldcard creation process.
It works, I did it for my German continental G1. Though there are reports that some Sandisk cards report wrong CID numbers. Mine gave the right one
EDIT: There's a way to write the raw sectors without using Cygwin (for sudo if you don't have a Linux box). If I recall correctly, I used HxD to perform that process. Might be wrong, I'll have to check when I get back home.

Thank you all contributor,, finally i am in RC 7 now.. Thanks soooo much

jsonseven said:
Thank you all contributor,, finally i am in RC 7 now.. Thanks soooo much
Click to expand...
Click to collapse
so after all this help ... you could at least tell us what you did to root it... so others can find the answer if they have your problem

sure, will do it after home, thanks all.

Upgrading Treo 750 to WM 6.1

I am having problems upgrading my Treo 750 from Windows Mobile 6.0 to 6.1 standard. I have run the Cheetah unlocker program. I formatted the card and put the radio program on it. Inserted and ran bootloader mode. The screen turns red, green, white and stays that way permanently. I eventually have to pull the card and reset the device. It comes up and works as usual with wm 6.0.
Is my phone not unlocked?
Is the radio program no good?
Any ideas?

Hard to say, but I suspect you either haven't successfully run the unlocker program, or have not formatted the SD card correctly.
BTW - Upgrading a radio would not get you from 6.0 to 6.1 it would only upgrade the radio, so make sure you have downloaded the proper file.

Understood. I have tried both the radio and the cheeimg.nbh file. Both have the same problem. How long should the upgrade take once the bootloader reads the card (so I know how long to wait until I try something else)?

I figured it out....here is the answer from this website. Thanks
originally Posted by dubLeE
With this method I have successfully unbranded, unlocked, and updated 2 Treo 750s that were originally AT&T/Cingular branded.
I spent hours running through multiple threads reading and searching to finally find a solution that worked flawlessly. These steps have been compiled from multiple threads:
http://forum.xda-developers.com/showthread.php?t=428048
http://forum.xda-developers.com/showthread.php?t=412999
http://forum.xda-developers.com/showthread.php?t=334100
Big thanks to Olipro, konker, and jcrompton!!!
Download the following:
Magic Unlocker from http://forum.xda-developers.com/show...21&postcount=2
CheetahUnlocker from http://forum.xda-developers.com/show...68&postcount=1
1_CHEE_MountExtROM.cab and 2_Chee_Extrom_rename.cab from http://forum.xda-developers.com/show...&postcount=374
Treo750_OS5_2_19199WWE_STD.rar from http://omnifusionhosting.net/treo750/
(I couldn't find the original posts for Treo750_OS5_2_19199WWE_STD.rar so I uploaded to my own site for now)
1. Download, extract, and run MAGIC_UNLOCKER on your phone.
2. Select both options in MAGIC_UNLOCKER and click unlock. This will unlock your phone.
3. Format your SD card to FAT32.
4. Extract Treo750_OS5_2_19199WWE_STD.rar and copy/paste CHEEIMG.nbh to the formatted SD card.
5. Transfer 1_CHEE_MountExtROM.cab and 2_Chee_Extrom_rename.cab to your Treo 750.
5. Run/Install 1_CHEE_MountExtROM.cab and then soft reset the phone.
7. Run/Install 2_Chee_Extrom_rename.cab and then soft reset the phone.
8. Click and run Start>Programs>Chee_Extrom_Unlocker. Run it about 3 or 4 time and you should some type of error messages. Just OK or X them and soft reset the phone again.
9. Open File Explorer and click the drop down arrow, in which you will now see ExtendROM. Open it and delete the 2 files in the partition folder.
10. Download, extract, and run CheetahUnlocker on your computer. For this part make sure you have an ActiveSync (XP) or WMDC (Vista) connection to your phone. Click Flash SPL and go through the steps for CheetahUnlocker to Flash SPL. Don't worry about any of the other items in the menu.
11. After going through the steps in CheetahUnlocker and the phone, the phone will enter into tri-color bootloader screen momentarily followed by Loading screen...
12. Next, you'll see a light blue screen with the heading CHEEIMG.nhb followed by a few other entries below it. At this point, it will tell you press the power button. Go ahead and press the End Call/Power button. This will begin the ROM flashing. The ROM flashing takes about 5 to 15 minutes.
13. When the flashing is completed, the bottom of the screen will say Update successful and the entries above with the OK seen at the end. Now reset the Treo 750 with the stylus and immediately (during the Palm Logo) perform a Hard Reset. This is accomplished by pressing and holding the End Call/Power button and simultaneously resetting the Treo 750.
14. You will now be prompted to Erase All Data. Press the Up key of the D-Pad to continue and erase the data. This will format the phone.
11. Upon completion, the Treo 750 will continue to boot-up and go through the initial start-up steps and wizard. Once completed, your phone will now be unlocked, unbranded, and updated to Windows Mobile 6.1.
I made this thread to help people unbrand, unlock, and update their Treo 750s without having to waste hours looking for solutions and how-to something. Basically, made it easier for the noobies and everyone else to find everything in one thread.

Mine goes to a gray screen immediately with an 'update in progress' bar ... takes about 2 minutes to flash the new ROM.

There doesn't appear to be a forum for the 700W/X. Where do I get information on these earlier Treos?

all ur links are not working please check again

HOWTO run ANDROID on X1

This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today

reserved for future updates

also reserved for future updates

and this, too

vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?

What the F?

♥♥♥
Good luck~♥

Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )

This is pretty consize. I hope it sums up all the main points of fatsal thread on android

With zImage_kovsky_20100313.zip system always lock up during shutdown

i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.

gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<

gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?

vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc

i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.

I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.

gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that

dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.

Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?

can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?

Yet another another WORKING How to root your Incredible

Thanks to everyone and all their post I was finally able to root my Incredible. Since I was having issues getting mine to root I tried pretty much everything that was said on these forums.
The secret to rooting is the timing of inserting your sdcard before the recovery screen is shown.
Here are the steps that I did to root 2 difficult incredibles.
1) Download the google SDK. You need the adb command for the rooting process.
2) Install HTC Sync or google SDK drivers. It doesn't matter which one you use. You just need the drivers installed and working.
3) Put your phone in USB Debugging mode under the applications config section.
4) Plug your usb in your phone while it is booted normally.
5) Select the disk drive option when prompted.
6) Make sure you can sucessfully connect to your phone using "adb shell" command. If this does not work you will not be able to go any further. This means drivers are not installed correctly.
7) Power off your phone. Doesn't matter how. Battery removal, press power off button etc...
8) Remove your SD card.
9) Press Volume down and power at the same time.
10) When the phone is at the Bootloader menu press Volume down and Highlight the Recovery option. Do not select it yet.
This is where the rooting process gets tricky.
11) Make sure your usb is plugged in.
12) Make sure you dont have your SD card in your phone.
You have to insert your SD card in your phone while the recovery mode is loading. There is a specific time window that you must do this. By using different SD cards they take certain time to initialize during the loading. This is why some SD cards work all the time and why others have to be inserted at a certain time
13) Go ahead and get your "adb shell" loop running. It should show "error: device not found"
14) Bring up a clock. You will need this to keep track of when you inserted your SD card during the recovery boot process.
15) Press the power button to select Recovery and start counting the second hand on the clock.
16) Start at 1 second and insert your SD card. You will wait until you hear windows beep when its loading the drivers for the USB device. After the 10 seconds your adb loop screen should show the following if it worked: "exec '/system/bin/sh' failed: No such file or directory (2)"
17) If it does NOT show this you will need to remove the battery and SD card and go back to step 14.
18) Increment your time by a second. So for the 2nd try insert the SD card after 2 seconds have past. So far on my walmart PNY 2gb SD card on 2 incredibles it takes around 5 to 6 seconds of waiting before I can insert my SD card. If you get to 10 seconds you need to restart and try again, but this time try half seconds increments.
When I select the Recovery option and the phone is loading I will see the white splash screen near the bottom kinda flicker a little bit and have a small horizontal line distort across the screen. That's about the same time I insert my SD card.
If you get the "exec '/system/bin/sh' failed: No such file or directory (2)" message looping in your shell prompt, Congrats you have access to the recovery shell. You will need to follow these steps to fully root your phone.
http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery
Thanks to everyone in these forums offering their input. Without your input I wouldn't be able to root my phone.

LOL
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.

At first I thought it was you reposting or someone poking fun at these types of threads.
You guys say like the same thing. Hopefully that means this is a good "update" to the process and people will have a slightly easier time.
I have Froyo on my Droid so am not too eager to get my Incredble rooted, but I have been following along.

I'm going to get my timings down tonight and post a 3rd thread on this!!!1

dreamersipaq said:
I guess great minds think alike:
http://forum.xda-developers.com/showthread.php?t=703589
^ I posted that this morning.
Click to expand...
Click to collapse
lol yeah, I guess the method works

seanmcd72 said:
I'm going to get my timings down tonight and post a 3rd thread on this!!!1
Click to expand...
Click to collapse
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.

rynosaur said:
I'm going to use an atomic clock to time and root my DI and report back on the decay rates of Polonium!
I appreciate users' attempts to refine this process, but I'm sticking with the old: insert the card right before white-switches-to-black . . . I tried timing and found myself slamming the sdcard card into the slot trying to make my targets, and that ain't not good for the DI.
Click to expand...
Click to collapse
LOL, well that's your own fault
Don't be so rough with her.... Abuser! Gentle, there is no reason to slam.
And it's still better then the click in and out method.

[Q] Can not ADB my device?!

I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.

By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.

The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back

Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.

If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.

priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?

I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.

So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!

the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?

priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.

By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!

Database Develop

welcome