Database Develop

biggest trouble ever installing 2.2

so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.

help please!

It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™

laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!

i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.

I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!

cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -

Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found

cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.

i dont have it plugged in when i use the terminal on the phone

cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.

It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App

yep make sure everything that has a capitals in it i capitalized in the terminal

this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.

i still can't figure out how to install a custom rom.

Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™

Upgrading from RA-heroc-v1.5.2 to v1.6.2

I'm running CM6 stable.
How would I go about upgrading to the new version of the recovery image? Is this pretty much it or is there something within the current recovery I can just click?
Amon_RA said:
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
Click to expand...
Click to collapse

clankfu said:
I'm running CM6 stable.
How would I go about upgrading to the new version of the recovery image? Is this pretty much it or is there something within the current recovery I can just click?
Click to expand...
Click to collapse
This is pretty much it It's the standard way to change recoveries, not another was as far as I know of.

Impaler to the rescue again
I've actually never accessed adb before. What do I have to do before typing "adb shell"? Is there something I have to do so that the cmd prompt recognizes or loads my phone?

You have the option to flash 1.6.2 via rom manager - im using clockwork mod - and decided, after trying darch's recovery that clockwork offers more - including being able to explore the entire sdcard -
is there anything special about 1.6.2 that would make it worth trying out as opposed to clockwork recovery ?

Vandelay007 said:
You have the option to flash 1.6.2 via rom manager - im using clockwork mod - and decided, after trying darch's recovery that clockwork offers more - including being able to explore the entire sdcard -
is there anything special about 1.6.2 that would make it worth trying out as opposed to clockwork recovery ?
Click to expand...
Click to collapse
I think some prefer clockword mod but not sure what the differences are. I just want to upgrade to 1.6.2 because it got rid of the some of the bugs.
Here's the thread for it:
http://forum.xda-developers.com/showthread.php?t=581521

clankfu said:
I think some prefer clockword mod but not sure what the differences are. I just want to upgrade to 1.6.2 because it got rid of the some of the bugs.
Here's the thread for it:
http://forum.xda-developers.com/showthread.php?t=581521
Click to expand...
Click to collapse
This is the easiest way in my opinion:
Download the RA image you want to flash
Put it on the base of your sd card
Open up terminal emulator on your phone
su
flash_image recovery /sdcard/name-of-recovery.img
reboot recovery
You should see your new RA image Let me know how it goes!

Thank you sir

[Q] Install ROM without SD Card

Ok so the SD card slot on my phone is toast. Is it possible to install a rom thru the USB cable without using the SD card? =/

Hmm... Ok I have two ideas that i'll quickly check out. One of which will require you to wipe your data/factory reset in recovery, the other if I did get it to work wouldn't require any wiping unless you wanted to.
I'll try 'em both out and tell you if I have any luck doing so
Alright, so here we go..
Results
First idea without having to wipe: no go
Second idea with wiping: WORKS
After doing some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)​
How to Flash a ROM Without an SD Card
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "kyoukoROM.zip" with the name you're using)
Code:
adb push ./kyoukoROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
If someone thinks I should post this in the development section as a [GUIDE] let me know and I'll post it there too

Yup I think so marking as a fav this is good knowledge thanks for the post
Root-Hack-Mod-Always™

Post it! This would be a HUGE help to people
Sent from my HERO200 using XDA App

Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.

andythegreenguy said:
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
Click to expand...
Click to collapse
Good idea, hopefully it'll help a lot more people there. I'll post it there and change up a couple things (the darch recovery part)
And idk how to edit the wiki

Amazing response! I will have to give this a try thank you!!! I still have a month left before my upgrade and I wanted to be able to change my ROM. Thanks again!

FYI Rom Manager will not flash a clockwork recovery without an SD card, gives an error... looking into other ways to flash a recovery...

[Q] Wiping Differences between Amon_RA and Clockwork

This is a basic question that is annoying because it highlights how much I don't really understand.
What is actually wiped using the different recoveries and should I prefer one over the other?
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
My current root file structure looks like this (ND=not a directory):
acct
cache
config
d
data
default (ND)
dev
etc
init (ND)
init.goldfish (ND)
init.heroc (ND)
init (ND)
mnt
..../asec
..../sdcard
..../secure
proc
root
sbin
sd-ext
sdcard
sys
system
*I had been messing with Apps2SD though it is not currently used on this set up. Should explain the multiple SD card mnts.
Amon_RA 1.5.2 Wipe Menu
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Clockwork 2.5.0.7 Wipe Menu
wipe data/factory reset
wipe cache partition
Additional Clockwork 2.5.0.7 Mounts and Storage Menu
format boot
format system
format data
format cache
format sdcard
format sd-ext
Any clarification would be much appreciated by me, and I assume the community. Thanks.
--------------------------------------------------------------------
A different thread discussing general difference between Amon_RA and Clockwork

I can't provide much help technically, but I wanted to point out clockwork 2.5 also has a Wipe Dalvik Cache option under the Advanced menu.

I'd definitely like some more technical information too, but I can provide what I've read and observed.
Factory reset wipes data AND cache.
Wiping boot and system happen already when flashing a rom and wiping either will require you to nandroid or reflash the rom. Many roms seem to suppress the messages or something.
[dpeeps74]

mtnchkn said:
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
Click to expand...
Click to collapse
The radio itself, PRL, PRI, and profile, are all stored in a deeper part of the phone than recovery or bootloader, if I remember right it's hardcoded into the dialer function of the phone (NOT in the .apk or ROM), so they stick no matter what you wipe or flash. As for what's different between the 2 recoveries, they both do basically the same thing, but CWM has more wipe options and is newer code, also when flashing zips from CWM you can actually select them inside of folders from your sd, whereas with amon ra it must be on the root of your sd. Also, in amon ra there is an option to "fix UID mismatches" which could be helpful if your device goes crazy but I've never had to use it. CWM has a fix permissions option, but you can also do that from TE, so again, not much use to me personally. I use 2.5.0.1 because it will flash both amend and edify zips, it's green, and doesn't give me the error code that 2.5.0.7 did. I have used every recovery available for the heroc. Also, the 3x versions of CWM have even more options and wipe options. The other sucky thing about CWM is the fact that wipe sd is right next to wipe cache in mounts so people sometimes wipe the wrong one. That is why tte one in the main menu is the one to use for wiping cache. Also, wipe and format are the same thing, different words. Feel free to pick them both apart, I think clockwork has much better functionality, even though the UI kinda blows compared to amon ra. YMMV.

You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero

Wow, this is exactly what's been on my mind lately... I've been looking at the ClockworkMod thread in dev lol.
I just switched from Amon_RA 1.7 to CWM 3.0.2.4 last night. I decided that since I'm trying CM7 for the first time, I would also try a new recovery. Il Duce summed up the differences nicely. What I found comforting was that nandroid backups made in one recovery can be recovered in other recoveries, you just have to move your backups to the appropriate location on the SD card.
I think they're about equal. Amon_RA has a nice interface, and I much prefer the press Home to confirm instead of CWM's. With CWM, you could choose a "Format /system" or something and you are only presented with a "Yes - wipe" confirmation, which doesn't actually tell you what you're wiping. And like Il Duce said, that could easily wipe the sdcard instead of cache. But with CWM you can make your SD card less cluttered and put zips in different folders.
If you're not using Firerat's mod, there's no reason not to just try them all
If you are using Firerat's mod, it's just a bit more troublesome.

laie1472 said:
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Click to expand...
Click to collapse
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?

mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
darch-ra 1.7 is capped at 691.

mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
IIRC it is OC'ed to 768 MHz.

c00ller said:
IIRC it is OC'ed to 768 MHz.
Click to expand...
Click to collapse
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.

So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
il Duce said:
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
Click to expand...
Click to collapse

mtnchkn said:
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
Click to expand...
Click to collapse
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img

il Duce said:
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
Click to expand...
Click to collapse
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.

mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
I wonder if that means the command is "not found" or if it's saying the .img is not found. If it's the latter, make sure you put quotes around the file path if there are spaces, e.g,
flash_image recovery "C:\Android Folder\recovery.img"
If it's the first, then you're right, it should work in adb shell.

mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
Make sure the recover img. Is named.
recovery-heroc-RA-1.7.img
And make sure its not
img.img.
Sometimes the file is not named correctly. Also make sure the img. Is on the root of your sd/card and not in any folder. Good luck
Yea it's Me Again With The
Modified Hero

Turns out I was missing flash_image command. I am going to include the solution below for others, but bottom line, everything is fine now and am running 1.7. If someone has a download for CW 2.5.0.1 which someone mentioned, post it too. Also, here is 1.5 if anyone needs it
http://dl.dropbox.com/u/1759357/recovery-heroc-RA-1.5.zip
I came across this post, which pointed to a flash_image file here. So I copied that into my tools folder, then...
Code:
>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT041HF00432 device
C:\android-sdk-windows\tools>adb root
adbd is already running as root
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push flash_image /system/bin
851 KB/s (26172 bytes in 0.030s)
C:\android-sdk-windows\tools>adb shell chmod 0755 /system/bin/flash_image
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery-heroc-RA-1.7.img
C:\android-sdk-windows\tools>adb shell reboot recovery
So now I have a new recovery.

[Q] Flashing Custom Recovery

I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:

i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!

demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?

... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium

demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN

Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium

demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe

No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?

You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app

demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app

It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium

demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app

if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition

demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app

Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app

demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?

Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium

demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.