yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] heirenton:
For SDK Windows 7 didn't like the driver at all. I am done with both options to try your command.
[Upgrading, Modifying and Unlocking] crzyruski:
The command was just to see what is contained in your update folder and list permissions in order to diagnose the problem.

I suspect the image file you have is corrupted through download... this is why I wanted you to run the command so we could compare files sizes and etc.

Recovery for Donut should be 2,615,296 bytes and called DSTL1_donut_recovery.img (don't forget to rename)

If you stay with 1.5, might I suggest the rooted package for greater flexibility: http://xdaforums.com/showpost.php?p=4852440&postcount=41

The drivers have worked for me under XP 32 bit and XP 64 bit (with a little bit of persuasion)
[Upgrading, Modifying and Unlocking] heirenton:
I tried to open img files with different tools. None of them worked. I think something is corrupting them while download. I tried it several times no luck.
[Upgrading, Modifying and Unlocking] crzyruski:
I have uploaded the file all over again.

Please re-download and confirm the size is correct. Then proceed as before.

Although it is possible via Linux and Perl scripts, your intention is not to open the .img file, naturally you will fail to do so. The file is used to flash your recovery to a newer version - specifically one that will allow for 1.6 (donut).

Without root:

1. Rename to "recovery.img"

2. Mount SD card

3. Place in update folder of SD card

4. Unmount

5. Confirm the file is there with File Manager (app on your DSTL1)

6. Reboot DSTL1

With root (above should work too):

1. Mount SD card

2. Place file anywhere on SD card (remember location)

3. Unmount

4. ADB into Shell

5. Run command su (to gain root)

6. If this is your first time accessing root from ADB Shell the device will ask to Allow or Deny (i think you know what to choose)

7. Run command flash_image recovery /sdcard/DSTL1_donut_recovery.img (or whatever the correct path is)

8. Reboot DSTL1
[Upgrading, Modifying and Unlocking] taitai:
you cannot mount the boot.img or recovery img directly, since it is not a proper image

please see this

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[Upgrading, Modifying and Unlocking] heirenton:
Thanks for all help. I have done every step and it worked like a charm. Nice job... But in the meantime i dont know how but i lost external sound. There is no ring tone or any other sound coming from phone. I can talk vibration works but sounds died. Do you have any idea about it?
[Upgrading, Modifying and Unlocking] crzyruski:
I know that I have, on occasion, lost my ringtone settings and nothing would play on its own. In such a case I had to go in and choose a ringtone manually.

Please provide us with the steps you took, not everyone takes the same steps. For example, some omit the Google Patch.

It is possible for the Google Patch to be your issue as we have had problems with it in the past. Are you comfortable trying a factory reset from Recovery mode?
[Upgrading, Modifying and Unlocking] sfabris:
I'm with you, but I'm still waiting for my N21.

Maybe this week the postman will ring...

sfabris
[Upgrading, Modifying and Unlocking] heirenton:
I did all there steps. I have google patch in. I did a factory reset to be sure about any weird settings but still there is no sound. The problem is i have to identify its source. Because there is always a chance some hardware part got broken or something -although i haven't drop the phone for a while-. I wonder is there any application or other way to identify the main source of the problem either software or a stupid little cable inside the phone? :)
[Upgrading, Modifying and Unlocking] taitai:
have you tried installing the google patch with no factory reset?
[Upgrading, Modifying and Unlocking] crzyruski:
Recovery comes with board testing, it should run you through all the steps to allow you to identify if all hardware is working properly. I believe it is the last step that performs a microphone speaker loop - basically it will play whatever you speak into the microphone, kind of like a speaker phone. Try this and tell us what happens.
[Upgrading, Modifying and Unlocking] ryszon:
I have new N21 just came to me few days ago. I thought I will do backup of the original ROM first.

mtd0 - bootloader

mtd1 - boot

mtd2 - recovery

mtd3 - system

mtd4 - jffs

mtd5 - userdata

mtd6 - casche

mtd7 - bbt

so when I try to do the

cat /dev/mtd/mtd1 > /sdcard/mtd1.img (boot)

cat /dev/mtd/mtd3 > /sdcard/mtd3.img (system)

I'll get permission denied, event when I try to view mtd1 or read the file I got only permission denied. Anyway to get through this without make any modification on the phone?

Im using PTerminal.apk
[Upgrading, Modifying and Unlocking] crzyruski:
You are receiving "permission denied" because you need root access to use this method.

We cannot backup your original N21 ROM because we do not have a fully functional custom Recovery. At this point in time the custom Recovery I have cannot mount sdcard for some reason.

BUT all is not lost, your stock N21 Recovery (mtd2) could still be useful.

You can attain root access by flashing your ROM to my rooted DSTL1 package.

Please use cat to get mt0 (bootloader) and mt2 (recovery).

System and boot will be flashed by the rooted ROM so they will not be useful.

Please zip and post on http://hotfile.com/

Thanks for your efforts!
[Upgrading, Modifying and Unlocking] ryszon:
ok thank for clear instruction, I do that and let you know + send the copy files
[Upgrading, Modifying and Unlocking] crzyruski:
This is my official "call to arms" thread for development.

http://xdaforums.com/showthread.php?p=4925784
[Upgrading, Modifying and Unlocking] chrismotto:
BB Connect

Any luck with installing BB connect? I found a link to htc site but it wanted the phones serial number to download the software.
[Upgrading, Modifying and Unlocking] crzyruski:
Unlikely you will find one for the Android... unless some clever coder ports it on their own free time.

http://androidcommunity.com/forums/f41/blackberry-connect-client-for-hero-24804/

Usually only available for Windows Mobile...

Why do you feel you need it?

In other news: FML! the DSTL1 stylus broke. WTF? i barely tapped it on my screen and the tip cracked off.:mad:
[Upgrading, Modifying and Unlocking] pacoge:
Hi crzyruski, any success with your custom recovery?

Is the only problem the mounting of the sdcard?

Please share with us your progress with the recovery and give more detailed info, may be someone can help us with this.

Paco
[Upgrading, Modifying and Unlocking] ryszon:
I'm trying trying and nothing. I'm using pTerminal on phone typeing the

cat /dev/mtd/mtd0 > /sdcard/mtd0.img

and still get permission denied - looks like there is no chance to copy any of this file :/ or I don't know how to do this. Tryied in file manager to copy manually folder and files but its not working as well. Any ideas? as I would like to backup them up before I will root the phone
[Upgrading, Modifying and Unlocking] crzyruski:
BETA_recovery-RA-DSTL1-v1.2.3 courtesy of Amon_RA

HUGE thanks to Amon_RA for porting his custom Recovery Image for the DSTL1 / N21. Search XDA to learn more about his Recovery Image and how it works!

This is a BETA... almost an ALPHA. Means it does not work as it should, BUT it does provide VERY useful functionality for those that wish to use it.

NOTE: This was created for 1.5, but then 1.6 unofficial came on the scene - it has not been updated, except for the kernel.

Consider everything broken because interface does not yet work!

What DOES work: ADB SHELL ROOT!

Flashing recovery is as easy as renaming to "recovery.img" and placing in "update" folder on your SDCARD.

Rooted phones can use

flash_image

command.

THIS IS SPECIFICALLY FOR ORIGINAL DSTL1/N21. Please do not attempt to use this post 1.6 update, if you desire a version for post 1.6, please PM me.

Download here: BETA1.5_recovery-RA-DSTL1-v1.2.3.img

HAPPY ADB SHELL ROOT!
[Upgrading, Modifying and Unlocking] crzyruski:
backup instructions (TECHNICAL METHOD)

Thanks pacoge!!!

You jogged my brains and I came up with a solution :)

But don't get too excited, it requires technical work:

USB drivers installed for the DSTL1

SDK downloaded and unzipped (Windows users)

use ADB (found in tools folder of unzipped SDK)

use BETA_recovery-RA-DSTL1-v1.2.3

Boot into recovery mode of BETA1.5_recovery-RA-DSTL1-v1.2.3.img

Launch command line

Navigate into your "tools" folder on SDK location

Run adb devices to see that your device is in recovery mode and identified by adb

Run adb shell and you should see # (you are ROOT :))

Now you can look at your mount partitions using cat /proc/mtd

Choose which mount number you wish to backup (0-7?)

*If you want to backup directly to SDcard, MOUNT it first*

Backup via cat /dev/mtd/mtd1 > /sdcard/mtd1.img <-- this is an example, use the number you wish!

Repeat with as many numbers as necessary.

*If you DID NOT MOUNT then you should use ADB PULL to put the files on your PC, the device will only retain data on the SDCARD if you did MOUNT*

To do MOUNT:

Run command mount /dev/block/mmcblk0p1 /sdcard

Double check!:

Run command ls /sdcard and convince yourself that what is listed is actually what should be on your sdcard

I still want someone's N21 ORIGINAL boot and system...

cat /dev/mtd/mtd1 > /sdcard/mtd1.img (boot)

cat /dev/mtd/mtd3 > /sdcard/mtd3.img (system)

I already have bootloader...

cat /dev/mtd/mtd1 > /sdcard/mtd1.img (Bootloader)

I would like somone's N21 ORIGINAL recovery...

(this will require a different method)
[Upgrading, Modifying and Unlocking] antonymm:
N21 ORIGINAL boot and system

crzyruski,

I have a new N21 phone. If you can give me instructions for LINUX (Fedora 11 2.6.30.9-96.fc11.x86_64) then I can attempt to backup the boot and system and send you the files for your testing. Before I mess around with installing 1.6 :)

Thanks,

Antonymm
[Upgrading, Modifying and Unlocking] crzyruski:
Get Android SDK: http://developer.android.com/sdk/index.html

The folder "tools" will contain ADB program.

Run adb devices with the device connected to ensure adb program can see your device.

Read directions from post #120 and #121

Then follow them.

Linux instructions are not different, only thing different is SDK (follow link) and drivers (my linux distro never required any)
[Upgrading, Modifying and Unlocking] crzyruski:
AndroidSPIN centralized ROMs

FYI, AndroidSPIN centralizes ROM info and downloads from many developers.

They have been kind enough to host DSTL1 / N21 content.

I encourage you all to participate in this community, identify misinformation and report to webmaster.

My rooted ROMs can be found following the link:

http://db.androidspin.com/android_developer_display.asp?developerid=52
[Upgrading, Modifying and Unlocking] antonymm:
Success at getting N21 ORIGINAL boot and system

SUCCESS .....

After booting into recovery mode with BETA_recovery-RA-DSTL1-v1.2.3. I was able to get root adb shell, I did a cat proc/mtd and saw that bootloader was mtd0 and mtd2 was boot and mtd3 was recovery. I also grabbed mtd1 param table but not sure what this is as it does not appear when I do a standard boot and adb shell. Probably from the recovery.img (BETA_recovery-RA-DSTL1-v1.2.3).

I hope this is correct and helps.

http://hotfile.com/dl/17619020/b98f5d9/N21_mtd_0_1_2_3.zip.zip.html

/ # cat /dev/mtd/mtd0 > /sdcard/mtd0.img

/ # cat /dev/mtd/mtd1 > /sdcard/mtd1.img

/ # cat /dev/mtd/mtd3 > /sdcard/mtd3.img

/ # cat /dev/mtd/mtd2 > /sdcard/mtd2.img

/ # cat /proc/mtd

dev: size erasesize name

mtd0: 000e0000 00020000 "Bootloader"

mtd1: 00020000 00020000 "param_table"

mtd2: 00400000 00020000 "boot"

mtd3: 00400000 00020000 "recovery"

mtd4: 07000000 00020000 "system"

mtd5: 06000000 00020000 "userdata"

mtd6: 016a0000 00020000 "cache"

mtd7: 00080000 00020000 "BBT"

I am going to try and update to 1.6 now and see how it goes.

Thanks,

Antonymm :)
[Upgrading, Modifying and Unlocking] sshosunny:
Hi, I got a N21 yesterday and I'm reading the post now.

I'm a newbie for Android and really thanks to crzyruski and other experienced users. Hope I can have my customized N21 soon :)
[Upgrading, Modifying and Unlocking] crzyruski:
Hmmmm...

So you are saying that cat /proc/mtd gave you different results in BETA_recovery-RA-DSTL1-v1.2.3 and in original firmware?

All you did was boot into a custom Recovery I provided... am I correct?

I wonder if it has to do with kernel...

Your current cat /proc/mtd output is that of someone that upgraded to 1.6 unofficial... makes me wonder if your files will be original
[Upgrading, Modifying and Unlocking] antonymm:
crzyruski,

Ok not working as expected. So I have gone back to trying to apply your crzyruski-DSTL1_1.5_rooted-v1.00.zip and then getting a copy of mt0 (bootloader) and mt2 (recovery).

I do the following.

1. created an update folder on the sdcard

2. copy crzyruski-DSTL1_1.5_rooted-v1.00.zip to the update folder on sdcard

3- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.

When I start in rec mode I get an error message

beta

E:Cant't find MISC:

And my N21 just sits there with the buttons flashing on and off?

I tried to press HOME key to search and apply update but it does nothing :confused:

So I must be doing something incorrectly.

any help would be appreciated...

Thanks,

Antonymm
[Upgrading, Modifying and Unlocking] crzyruski:
It looks like you are still running the BETA_recovery-RA-DSTL1-v1.2.3

It is not functional and will not work.

What you shared with us will have to do because you have already flashed recovery using BETA_recovery-RA-DSTL1-v1.2.3, thus you no longer have your original.

At this point you have contributed all you could, Thank You!

Enjoy yourself and upgrade to 1.5 rooted or 1.6 unofficial rooted.

If you decide to do the 1.5 rooted ROM, you will need to use the DSTL1 Original Recovery found on this thread.
[Upgrading, Modifying and Unlocking] sshosunny:
Market Problem

Hi, I followed the steps mentioned in the thread

(http://xdaforums.com/showpost.php?p=4858841&postcount=47)

My N21 is DONUT now. After creating a new google account, I tried to use the Market. When I pressed the Market icon, the browser prompted and "Android Market Terms" was loaded.

However, I can't found any "Next" or "Accept" icons. I can't use the Market now...

Can anyone do me a favor?

Thanks in advance.
[Upgrading, Modifying and Unlocking] crzyruski:
ROM = System + Boot

Original N21 files:

I have Bootloader - THANKS ikarishinjisan and antonymm

I have Boot - THANKS ikarishinjisan and antonymm

I have Recovery - THANKS Slemmen

I have System - THANKS ryszon and pacoge
[Upgrading, Modifying and Unlocking] A n d r e:
I have an original Sciphone N21. All i have to do to get system is explained on post #121?

Another question, if I upgrade to 1.6 unofficial will I still have Dual SIM capabilities?

Thank you!
[Upgrading, Modifying and Unlocking] crzyruski:
Please read post #120 as well as post #121

Please only act once you have read. I thank you for your help and diligence :)

http://db.androidspin.com/android_developer_display.asp?developerid=52
[Upgrading, Modifying and Unlocking] jlcd:
I have problems with Bluetooth. I can't connect to any devices and the searching devices option doesn't nothing. I think this occurs since 1.6 update because with original version I could connect to my car's handsfree.

Anyone else have this problem?
[Upgrading, Modifying and Unlocking] jlcd:
Problem solved after I've unistalled some apps and a pair of reboots..., but now I have a new problem: can't connect to PC by usb (no usb logo on notifications bar) the only thing I can do is charging battery.

I'm thinking to do a factory reset. :confused:
[Upgrading, Modifying and Unlocking] crzyruski:
I have experienced this problem on occassion:

My Win XP 64 bit OS sometimes does not recognize my device via usb. It reports that it is unable to identify the device connected.

This has been frequent when connecting through a usb hub like the one integrated into my monitor. It has been better to avoid the hub. Also, I have noticed that the connection plug on the device is not the best quality because I have been able to break connection by wiggle cable when connected to device. Also possible to push mini usb too far into device causing connection difficulties.

Try messing with physical usb cable. Also see if usb debugging is enabled in settings - though this should not be necessary for mounting sdcard.

Does adb work in recovery?
[Upgrading, Modifying and Unlocking] jlcd:
I've tried in another usb port and another pc and usb simbol is missing. Must be a terminal problem.
[Upgrading, Modifying and Unlocking] crzyruski:
Hmmm... yes, I imagine it is device.What apps have you removed to achieve this functionality loss? Have you tried halfway (not fully) inserting mini usb plug into the phone?

Please try booting into recovery and connecting to PC. I have noticed in this situation no usb icon is displayed on PC and obviously device. But after a minute,the command 'adb devices' will identify that your phone is connected in recovery mode. This test should tell you if the problem is hardware or software (ROM).
[Upgrading, Modifying and Unlocking] jlcd:
The pc only shows a usb connection, but not identifies as Android Phone and I can't access to sd card.
[Upgrading, Modifying and Unlocking] crzyruski:
I do not mean to insult: Do have the correct drivers installed on all Windows PC that you try this on?

What does your PC show is connected at all? Something like what I have attached?

Have you tried Linux? or is this not easy?

I am out of ideas... I would hate to recommend a factory reset / system reflash :( But I don't know what else you can do.

If you are saying ADB does not detect your device in Windows nor Linux then it is safe to say this is a device problem and hopefully not hardware, hopefully software.
[Upgrading, Modifying and Unlocking] jlcd:
After a general backup and a factory reset I can connect to pc again. :)

crzyruski, thank you for yor interest.
[Upgrading, Modifying and Unlocking] pacoge:
about recovery

Hi crzyruski,

I suppose that you've got the recovery partition by flashing with your DSTL1_root_1.0.zip (replacing the original system and boot) and with root do:

cat /dev/mtd/mtd2 > /sdcard/mtd2.img (recovery)

I've not enough time at the moment to backup the system partition, but maybe the weekend I will.

In this case the process will be:

* Flash Recovery and reboot into recovery mode with BETA_recovery-RA-DSTL1-v1.2.3

* use adb root

* backup the partitions.

* flash Recovery and reboot with the original backup of N21 recovery that you now have (and share :) )

then we have the phone as original another time but with a full backup.

Please confirm.

Paco
[Upgrading, Modifying and Unlocking] blacline:
It is possible to connect a gps bluetooth on N21?

i try with a holux gr-230 but i have this message:

paired but not connected
[Upgrading, Modifying and Unlocking] pacoge:
Sorry, I have not tested it but the user manual says:

The phone supports only the headset and hands-free Bluetooth profiles, so if you try to connect to a device that is not a headset or hands-free car kit, then you will receive an “unable to connect” message.

Maybe others in the forum know if is enough with an update of the ROM or we need a new firmware. ( crzyruski :confused: )

Paco G.
[Upgrading, Modifying and Unlocking] crzyruski:
pacoge is correct.

Android 1.5 (cupcake) is shipped with original DSTL1 / N21.

Android 1.5

does not

have good BlueTooth support.

Android 1.6 *should* be our savior in this case.

Likewise the unofficial 1.6 upgrade should provide for us good BlueTooth support. I say should because I have not tested any of the BlueTooth functionality... I guess you will be the pioneer if you decide to do so :)

I am interested for you to test this for our community, particularly because I too have been thinking about an external BlueTooth GPS solution for my DSTL1.

My question to you:

do you have specific software (apk) to make your GPS work for the Android? Or do you expect the Android to somehow seemlessly integrate with an external BlueTooth GPS?

FYI:

In this case I believe you are talking about the same thing. I cannot make a distinction between firmware and ROM. Perhaps by firmware you mean kernel? If so, this would be part of the boot image and thus ROM.
[Upgrading, Modifying and Unlocking] crzyruski:
Yes, this is the way we were able to obtain a backup of the original N21 recovery. I will of course share it (currently I cannot due to development machine crash :()

Keep in mind that the original DSTL1 recovery image is already shared here. I make mention of it because I cannot imagine the two recovery images being much different (except maybe for kernel)...

As you may have noticed: DSTL1 and N21 is literally the same hardware and the software is barely with any difference. I agree that the N21 ships with more recent kernel build, but that is trivial and we know of few reasons why they needed to do this if not just to do it.

BETA1.5_recovery-RA-DSTL1-v1.2.3.img is the correct file to use. I make mention of this because my initial release used the kernel from the unofficial 1.6 - that is not right to do when dealing with a 1.5 system image.

I have since fixed it to use kernel from 1.5 Post #120 has all the details

Good luck!
[Upgrading, Modifying and Unlocking] blacline:
Thanks for answers!

I want to use copilot, but my version just working with android 1.5, i test with the sdk on 1.6 and 2.0 (don't works library problem).
[Upgrading, Modifying and Unlocking] crzyruski:
The latest version of copilot should work with 1.6 (donut), I have witnessed it.

There has been a few attempts with getting BlueTooth data functions onto 1.5 (cupcake).

You may want to explore these options on your own and hope to come across a feasible solution. Or you might as well get a new version of copilot so you can use 1.6... besides, 1.6 has TTS, what good is a navigation software that does not talk to you?

Whatever you decide to do, share with us your success and failure.

Best of Luck!
[Upgrading, Modifying and Unlocking] jlcd:
http://groups.google.com/group/andr...ad/c36409dd496a5e53/a2d9eb9929e1f3ef?lnk=raot
[Upgrading, Modifying and Unlocking] blacline:
thanks!

But i don't know how to...
[Upgrading, Modifying and Unlocking] chrismotto:
Can someone please tell me if they are able to use doc viewer to open any word or excell files? Thanks team.
[Upgrading, Modifying and Unlocking] jlcd:
http://www.androlib.com/android.application.com-dataviz-docstogo-qmBD.aspx
[Upgrading, Modifying and Unlocking] blacline:
I upgrade to 1.6 and i have the same message with my gps:

paired but not connected

I have an other problem it's impossible to launch recovery for install Google Apps PATCH.
[Upgrading, Modifying and Unlocking] crzyruski:
jlcd had alluded to this earlier: http://code.google.com/p/android-bluetooth/

impossible to launch recovery? what steps do you take?

1. You can turn off the phone. Take out the battery for a second and put it back in. Hold HOME and then press and hold POWER until you see Tux (linux logo) which should take approximately 5-10 sec.

2. In ADB, type reboot recovery
[Upgrading, Modifying and Unlocking] blacline:
Its ok for Google Apps PATCH, i use the first methode, before i try to do Factory reset...(i'm french not easy for me).

Now the market working fine!!!

Thank you!