• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[TUTORIAL] Replace Windows Mobile with Android NAND ROMs

Search This thread

kerfooly

Senior Member
Apr 28, 2009
99
205
27
Vancouver
www.facebook.com
It is possible to flash a ROM without an SD card, but not through the Xperoid Toolbox utility. It only uses "adb push" to transfer the ROM into the sdcard partition. I read something while ago that might help this sort of thing:


Source: http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android

I'm planning on implementing this in the future if I have time. My Linux machine's acting a bit weird so I'm using my shared desktop temporarily. My dad pretty much ruined the Windows 7 partition with his random bloatware.

Hey brian, my device and me could be your rat as my SIM and SD card slots are gone and im Free till may, I can help in the development too but first you got to help me here

I cant manage to list my device through ADB shell, it keeps saying Error:no device found, but the fastboot and fastboot commands work perfectly, like fastboot devices shows me ? fastboot, but ADB commands don't work as ADB cant list my device, what am I doing wrong?
 

BrianXP7

Senior Member
Nov 16, 2011
729
279
Hey brian, my device and me could be your rat as my SIM and SD card slots are gone and im Free till may, I can help in the development too but first you got to help me here

I cant manage to list my device through ADB shell, it keeps saying Error:no device found, but the fastboot and fastboot commands work perfectly, like fastboot devices shows me ? fastboot, but ADB commands don't work as ADB cant list my device, what am I doing wrong?

This one really stumped me. Usually I always use "sudo" in front of Fastboot and ADB, but that's for Mac and Linux. In the case with Windows, I would try running the command line as an administrator or there would be missing or incorrect drivers. I don't have much experience with Windows as much as Linux so it troubles me. Linux seems easier to learn for development. (Or in my case, modding and hacking.) I don't know why but "sudo" does it for me. Hope this helps.

Also, what happened to CyanogenMod 7.1 by Sun Dream? It's mentioned in this post. That link leads to this thread. I'm not really much of a "veteran" here. :p
 
Last edited:

kerfooly

Senior Member
Apr 28, 2009
99
205
27
Vancouver
www.facebook.com
This one really stumped me. Usually I always use "sudo" in front of Fastboot and ADB, but that's for Mac and Linux. In the case with Windows, I would try running the command line as an administrator or there would be missing or incorrect drivers. I don't have much experience with Windows as much as Linux so it troubles me. Linux seems easier to learn for development. (Or in my case, modding and hacking.) I don't know why but "sudo" does it for me. Hope this helps.

Also, what happened to CyanogenMod 7.1 by Sun Dream? It's mentioned in this post. That link leads to this thread.

I searched a bit more and apparently bootloader can perform Fastboot only, unless you flash a boot.img, but CWM recovery should always do ADB,

anyhow I tried flashing a boot.img and after that I couldnt go to bootloader as the kernel doesnt let me, its recovery or its android kernel and booting the system which I dont have

from other side, i tried connecting the device in CWM recovery, the PC detects it as XDA instead of the bootloader's XPERIA X1 name tag, and ADB shell still gives me error saying no device found, I even tried the intial V4.x recovery and even flashing a boot.img and then recovery but no hope,

is there anyway you could dump your ROM as system.img for me and upload it, you can do that by this tool

Or use a kitchen and repack the ROM in system.img form
 

BrianXP7

Senior Member
Nov 16, 2011
729
279
I searched a bit more and apparently bootloader can perform Fastboot only, unless you flash a boot.img, but CWM recovery should always do ADB,

anyhow I tried flashing a boot.img and after that I couldnt go to bootloader as the kernel doesnt let me, its recovery or its android kernel and booting the system which I dont have

from other side, i tried connecting the device in CWM recovery, the PC detects it as XDA instead of the bootloader's XPERIA X1 name tag, and ADB shell still gives me error saying no device found, I even tried the intial V4.x recovery and even flashing a boot.img and then recovery but no hope,

is there anyway you could dump your ROM as system.img for me and upload it, you can do that by this tool

Or use a kitchen and repack the ROM in system.img form

Just to clarify, Fastboot is only for Bootloader Mode (making the Reboot to Bootloader in the power menu useful) and ADB only works with ClockworkMod Recovery and in the firmware itself. Did I get it right?

I'm working on a ROM dump right now. I may consider making it an alternate flashing method for Code Butter and the backup option for the Xperoid Toolbox. Just to make sure, what build do you want? I'll dump both for now.

UPDATE: I'm having trouble dumping it. This is the result:
Code:
[email protected]:~/Downloads$ adb push romdump /data/local
1070 KB/s (1149900 bytes in 1.049s)
[email protected]:~/Downloads$ adb shell chmod 04755 /data/local/romdump
chmod: /data/local/romdump: Not a directory
[email protected]:~/Downloads$ adb shell /data/local/romdump
/sbin/sh: /data/local/romdump: not found
 
Last edited:

BrianXP7

Senior Member
Nov 16, 2011
729
279
I'm really having a hard time dumping. I tried backing up via ClockworkMod Recovery but my SD card is a bit damaged and has some write errors. You could try pushing the files using ADB. Example:

Extract ZIP:
Code:
cd '{DIRECTORY TO ROM}'
unzip {FILENAME_OF_ROM.ZIP} -d {DESIRED DIRECTORY NAME}
cd '{DIRECTORY OF EXTRACTED ROM}'

Flash Kernel:
Code:
fastboot flash boot boot.img
fastboot reboot
Reboot into ClockworkMod Recovery.

Push System Files:
Code:
cd '{DIRECTORY OF EXTRACTED ROM}'
adb push system/. /system

Push Data Files:
Code:
cd '{DIRECTORY OF EXTRACTED ROM}'
adb push data/. /data

This is what I would do in the Terminal with a VERY clean install. (Assuming you have the Android SDK setup with this tutorial.) If you're using Windows or Mac, try to rewrite and adapt the commands.
Code:
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase system
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase data
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase boot
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase recovery
[email protected]:~$ cd '~/Applications/Android/Images/Recovery'
[email protected]:~/Applications/Android/Images/Recovery$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot flash recovery recovery-20120726.img
[email protected]:~$ cd '~/Applications/Android/Images/Kernel'
[email protected]:~/Applications/Android/Images/Kernel$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot flash boot boot.img
[email protected]:~$ cd '~/Applications/Android/Firmware/Code Butter'
[email protected]:~/Applications/Android/Firmware/Code Butter$ unzip CodeButter-GB-20121203-KOVSKY.zip -d CodeButter-GB-20121203-KOVSKY
[email protected]:~/Applications/Android/Firmware/Code Butter$ cd 'CodeButter-GB-20121203-KOVSKY'
[email protected]:~/Applications/Android/Firmware/Code Butter/CodeButter-GB-20121203-KOVSKY$ adb push system/. /system
[email protected]:~/Applications/Android/Firmware/Code Butter/CodeButter-GB-20121203-KOVSKY$ adb push data/. /data
It doesn't seem to boot. I ran out of ideas... I can't even find something in the kitchen that can rebuild it into an image. Turns out there really is none. More info here.
 
Last edited:

kerfooly

Senior Member
Apr 28, 2009
99
205
27
Vancouver
www.facebook.com
I'm really having a hard time dumping. I tried backing up via ClockworkMod Recovery but my SD card is a bit damaged and has some write errors. You could try pushing the files using ADB. Example:

Extract ZIP:
Code:
cd '{DIRECTORY TO ROM}'
unzip {FILENAME_OF_ROM.ZIP} -d {DESIRED DIRECTORY NAME}
cd '{DIRECTORY OF EXTRACTED ROM}'

Flash Kernel:
Code:
fastboot flash boot boot.img
fastboot reboot
Reboot into ClockworkMod Recovery.

Push System Files:
Code:
cd '{DIRECTORY OF EXTRACTED ROM}'
adb push system/. /system

Push Data Files:
Code:
cd '{DIRECTORY OF EXTRACTED ROM}'
adb push data/. /data

This is what I would do in the Terminal with a VERY clean install. (Assuming you have the Android SDK setup with this tutorial.) If you're using Windows or Mac, try to rewrite and adapt the commands.
Code:
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase system
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase data
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase boot
[email protected]:~$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot erase recovery
[email protected]:~$ cd '~/Applications/Android/Images/Recovery'
[email protected]:~/Applications/Android/Images/Recovery$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot flash recovery recovery-20120726.img
[email protected]:~$ cd '~/Applications/Android/Images/Kernel'
[email protected]:~/Applications/Android/Images/Kernel$ sudo ~/Applications/Android/Tools/adt-bundle-linux-x86/sdk/platform-tools/fastboot flash boot boot.img
[email protected]:~$ cd '~/Applications/Android/Firmware/Code Butter'
[email protected]:~/Applications/Android/Firmware/Code Butter$ unzip CodeButter-GB-20121203-KOVSKY.zip -d CodeButter-GB-20121203-KOVSKY
[email protected]:~/Applications/Android/Firmware/Code Butter$ cd 'CodeButter-GB-20121203-KOVSKY'
[email protected]:~/Applications/Android/Firmware/Code Butter/CodeButter-GB-20121203-KOVSKY$ adb push system/. /system
[email protected]:~/Applications/Android/Firmware/Code Butter/CodeButter-GB-20121203-KOVSKY$ adb push data/. /data
It doesn't seem to boot. I ran out of ideas... I can't even find something in the kitchen that can rebuild it into an image. Turns out there really is none. More info here.

yes, you got the fastboot and ADB difference correctly

Damn I was really looking forward to contribute, the ROMDUMP app can work trough terminal emulator too, maybe that will help as USB ADB is buggy, here is the guide
 
  • Like
Reactions: BrianXP7

BrianXP7

Senior Member
Nov 16, 2011
729
279
yes, you got the fastboot and ADB difference correctly

Damn I was really looking forward to contribute, the ROMDUMP app can work trough terminal emulator too, maybe that will help as USB ADB is buggy, here is the guide

Works, but my SD card has I/O errors. Can it backup directly to my PC?
 

Alfieri21

Member
Feb 9, 2009
5
0
Thank you all for advices.
I disassembled the phone and I tried to find problem. I found out, that when I insert SD card I have to remove battery and push the card with stylus toward to the contacts and then phone recognize the card.

So I finaly flashed Android with SD card.

I would like to thank you for answering my problem.

Merry Christmas guys!

Alfieri
 

BrianXP7

Senior Member
Nov 16, 2011
729
279
I don't think this was posted in this forum before but I just want to mention maybe this would help Linux users flash LK Bootloader. (As mentioned in this thread, the Sony Ericsson XPERIA X1 uses a standard HTC SPL. This device was manufactured by HTC so it would make sense, no pun intended.) I haven't fully tested this yet but I will when I have time. Works like a charm! :)

http://code.google.com/p/htc-flasher/

I'm planning on implementing this feature in Xperoid Tool. I haven't updated that in a while so I think I'll need to rewrite everything.

Update: Yep, looks like it works! Here's the tool running in the Terminal under Ubuntu 12.10 x86 flashing Clean Revolution. I noticed it seemed to take a little while longer than usual to get into RUU mode. I still can't find something similar to Task 49 though.

attachment.php


Also, as a minor request, can anyone build AOSP from source for the HTC Kovsky? I can't do it myself because my PC sucks and doesn't have x64 support and I know it seems kind of redundant to CyanogenMod. It's mainly just for pure curiosity. :p
 

Attachments

  • Flash.jpg
    Flash.jpg
    37.7 KB · Views: 1,876
Last edited:

BrianXP7

Senior Member
Nov 16, 2011
729
279
Here's something that can help those without an SD card available.

Use in Terminal Emulator or ADB Shell:
Code:
su
mkdir /data/media
mount /data/media /sd-ext
chmod 777 /sd-ext/.

And use ADB to push and flash your desired custom ROM.
 
Last edited:

vbrookie

Senior Member
Jan 8, 2013
56
7
I need help. It seems like I can't flash any roms. I tried to fashboot boot.img but the message says the phone's memory is full. And I tried to flash a rom through recovery and it always stops on boot.img.

Please help.
 

manolog3

Member
Feb 24, 2010
9
0
Hi guys,
I need your help!!! I didn't put the recovery file on the fastboot (by mistake) and know after the restart, the phone stacks on the black screen with the white letters. Is there a way to put recovery at this point?
 

Aminlv

New member
Jul 22, 2008
4
0
thanks for the guide just 3 quick questions
1. how to use memorycard after everything is done or can't we!?
2. i tried to use WIFI but it keep switching like this disabled searching connected and recycle this every few seconds! how to fix this issue?!
3. how much last long with full battery charge? i tried dual boot method it drain full battery 1 glup! didnt even last half hour
compare to that how long last with this method a day or half a day?
 

Peter1961

Member
Jun 13, 2021
5
0
HTC Leo
Thank you for that , does that apply to the old Windows Mobile from about 15 years ago?
Used to be a green page called Windows Mobile device center , I think.
Really appreciate your help.
Peter
 

Top Liked Posts

  • There are no posts matching your filters.
  • 183
    About
    This thread contains all the Android NAND development that is going on in different websites like Github.com

    The developers are not responsible for any damages happened to your phone in any way so be aware of what you are doing

    Note that the development is still in "Beta" state and it has few issues which are still under development, the Android NAND ROMs are almost ready for day to day use

    you can always switch back to any windows mobile ROM by flashing the official or a custom windows mobile ROM just like when you had windows mobile using any Sony Ericsson Xperia X1 ROM Update utility or the SD Card (KOVSIMG.nbh) method, as the SPL or windows mobile's bootloader will not be effected

    there will be few random screen flashes when the device start even when you shift back to windows mobile but this does not effect the performance of the device in anyway

    Your SD Card Android ROMs are not going to be effected but you wont be able to run them unless you re-install Windows Mobile again

    below is the list of whats working and not working so far

    Working

    • Phone
    • SMS
    • Speaker
    • LEDs
    • Bluetooth (beta)
    • Headphone
    • Media Playback
    • Touch Pad
    • Data connection (GPRS/3G)
    • Main Camera (Beta)
    • Hardware acceleration (3D/OpenGL ES) (beta)
    • USB (beta)
    • Screen (beta)
    • Keyboard/Keypad
    • WiFi (Beta)
    • Battery Meter (beta)
    • Battery Charging
    • Battery Life (beta)
    • Camera Flash LED
    • GPS (beta)

    Not working

    • Light Sensor (Under development)
    • FM Radio
    • Hardware Acceleration bugs
      Flash Player support, YouTube HQ Mode support
    • Front Camera
    • Main Camera bugs (under development)
      focus function
    • WiFi bugs (under development)
      WEP connection support
    • GPS bugs (under development)
    • Bluetooth bugs (under development)
      once turned on, causes rapid battery drain and cant be turned off unless user restart the device
    • USB bugs
    • Battery Life (beta)
      still not same as Windows mobile
    • Screen auto rotation bug
      rotates to landscape every time user turns the screen off and on
    • Battery Meter (beta)
      inaccurate after certain percentage of battery

    Downloads
    below is the list of Files which are required

    • HSPL 0.78 (optional)
      Download it from here if you haven't install a Custom ROM before or you are on initial HSPL 0.72

    • A ROM update utility (optional)
      Kovsky Advance ROM update utility is recommended as Its easier to work with, but the official RUU and SD Card method will do the same

    • Latest Android bootloader
      Download the latest bootloader available here

    • Android Driver and Fastboot
      Xperoid installer is recommended as it contains the necessary files of Android SDK only and can do the job automatically,

    • Latest Android Recovery
      Download the latest recovery available here

    • Latest Android Kernel
      Download the latest Kernel available here

    • An Android ROM
      choose and download your favorite Android ROM from here or here

    Video

    Here is the video of how to install any NAND ROM, lots of steps have changed but the main procedure is the same

    PART 1
    PART 2



    1.HSPL

    If you have already installed a custom Windows Mobile ROM and have the 0.78 version skip this part, to know about your SPL version turn off your phone, hold Volume down button and while holding hold the power button till you see the Tri colour screen which is the SPL; If you have Olinex name on any line, you have HSPL,

    SPL is like your devices BIOS, and Hard SPL will unlock your devices bootloader to allow you to install any custom made Read only memory (ROM)

    to do a HSPL refer to THIS thread

    (if you had a problem in performing a HSPL, read the replies at the end of the above thread as there were some users not being able to HSPL the normal way and had to do few other steps)

    2.Android BootLoader

    Put the .zip ROM you have downloaded in the root of your SD Card before you do anything further; which means put the .Zip file in E:\ROM.zip if your SD Card drive letter is E

    HTC Linux LK bootloader allows the device to run the kernel directly after it got turned on

    Install it just like the way you install any other Windows Mobile ROM, which is using a RUU or the SD Card method

    It is always recommended to do a Task29 before you flash an Android Bootloader if you know how to.


    (Kovsky Advance RUU)

    3.Kernel
    Kernels are like drivers in PC, it connects and manage the hardware of the device
    they have to be installed using Fastboot. Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB.

    >For Windows users

    • Extract Xperoid Installer
    • Rename the Kernel you have downloaded to boot.img, then place it in the Xperoid fastboot folder
    • Rename the recovery you have downloaded to recovery.img, then place it in the Xperoid fastboot folder
    • connect your phone and install the drivers from Android USB driver folder
    • then simply run Xperoid Fastboot installer.bat from the Xperoid fastboot folder

    >For Linux based OS users

    follow the instruction on This page

    zr0xi.png


    5.Recovery

    ClockWorkMod Recovery is like the BIOS in PCs, which is the software that can install and manage the device's software

    image28.png



    To go into recovery turn on your device and as soon as the phone starts (Sony Ericsson logo stage) hold the Camera Focus button which is holding the Camera button half pressed till recovery starts, (it might take few seconds to load)
    once you are in recovery use the touch pad to go up and down, power button to go back and middle button to select trough the menu,

    1. Go to mounts and storage> Format Data
    2. Go to mounts and storage> Format Cache
    3. Go to mounts and storage> Format dalvik cache
    4. go back to main menu
    5. Go to install zip from SDcard
    6. select the file and install it
    7. after installation select restart system now
    8. Remove the SD Card and the battery, put the battery in, turn on the phone and wait till it completely start up
    9. Re enter recovery with SD Card inserted and install the GAPPS
    10. Load the system without SD Card and sync it with your accounts and open all the apps once and then restart again and once you are in android again insert your SD Card

    If you are updating your ROM from an earlier version of NAND Android ROM

    1. Download the full wipe script and put it in the root of SD Card
    2. Go to backup and restore
    3. select Backup
    4. go back to main menu
    5. Go to install zip from SDcard
    6. select the full wipe script.zip and install it
    7. go to main menu
    8. Go to install zip from SDcard
    9. select your new ROM and install it
    10. go back to main menu
    11. go to backup and restore
    12. go to Advanced restore
    13. select Restore data
    14. go back to main menu
    15. select restart system now

    Recommendations:

    Booting with SD Card inserted:
    • As you might have notice in the guide, the Kernels have a major bug of not being able to boot the ROM with a normally formatted SD Card inside the device. so we have to format the SD card in a special way to bypass this problem

      To do so follow this guide

    • You have to perform these recommended actions for better performance

    Back to Windows Mobile:

    In order to switch back to any windows mobile ROM, enter the Windows mobile bootloader (SPL) by turning the device on while holding Power and Volume down buttons together, and once you entered SPL simply flash the ROM as you did earlier
    It is always recommended again to do a Task29 before and a Hard reset after you installed a Windows Mobile ROM

    report back your issues and problems for faster and better ROMs in future.

    Special thanks goes to:
    SP3DEV
    Sun Dream
    XDAndroid team
    Neopeek
    Ady
    zargloub
    Jerrytan
    BrickPSP
    Elibl
    Im not asking for donation but press the thanks button , Please Vote for this thread too
    5
    Hi, very good guide... but

    What features are working/not working on the NAND build?

    updated :)
    5
    It would be awesome if someone could modify the bootloader so that it can start up without having to remove the microSD card.

    Is there any particular reason why this has not been implemented?

    The reason is that it "works for me". My phone boots regardless of microSD being inserted or not. If anyone wants, go ahead and try to figure out what causes problems. If you want to compile .NBH from lk, use my tinboot-for-lk project at gitorious, there's an old branch which contains scripts for building images for X1
    3
    I'm back into the game boys!!!! Look at my sig!!!

    Regards!!!
    3
    I don't use my X1 as a phone anymore, so I use it as a remote for my pc.
    I've had very few issues when trying this rom, no reboots, no keys freeze, etc.
    But battery charging (& usage) is a big issue for me, I couldn't get it to charge past 34% after flashing, but I didn't really try either.
    Nonetheless thanks to all involved for bringing it this far already!
    I really hope the last bugs get worked out (I should really learn to program and help you guys..).