Database Develop

[SOLVED]I can't root RC29

Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.

Sounds like you didn't flash the recovery image... Are you sure you placed it on your phone and followed the instructions to flash it? the flash_image recovery recovery.img command. Anyways, I have to run to work, I"ll help you more when I get back if you haven't figured it out by then. good luck.

http://www.youtube.com/watch?v=GgJ2VtSqtJY&feature=channel
this viedo help me with my rooting since i learn better thru visual =)
this is part 1 of 3. this dudes videos helped me from stock to root. to another cupcake rom. to jachero rom. it toook me like abt a day to do everything. but then after that it shouldnt take long to start uploading various roms =)

Knightsofwar210 said:
Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.
Click to expand...
Click to collapse
Well I've had my Original (incorrect radio flash method), 1st Warranty replacement (keyboard too lose for my liking), 2nd Warranty replacement (sending back due to 'ASDF' keys stick), all flashed in past 2 weeks. I've almost memorized the stupid commands. The "flash_image recovery /sdcard/recovery_testkeys.img" had me puzzled on this one. But I've figured it out as the short method vs changing directory.
I think your issue is the last part of copying the recovery image to the phone. I've always used the following:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd sdcard
# flash_image recovery recovery.img
# cat recovery.img > /system/recovery.img
seems Like you're instructions kind of combine the 3rd and 4th and skips the cat command, so i have no ideal how yours is getting the file to the actual phone. I may be wrong, but just looks half done. It may be as simple as copying the image to the /system path with the 'cat' command. Good luck with it tho.
Link: http://forum.xda-developers.com/showthread.php?t=442480

It just won't copy that img file, because I still get the old color boot menu. Nothing I do works.

Oh and I read somewhere I have to upgrade to the latest radio too, where do I get it and install it?

I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?

Knightsofwar210 said:
I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?
Click to expand...
Click to collapse
Well, that's your choice
JF 1.51 is just a plain cupcake rom with root
Haykuro's 6.0 sapphire port is very nice, like JF 1.5 but with HTC Dialer, Camera ect
Cyanogen's build is like JF but more heavily modded, has auto Apps2SD and a few other modifications.
Then there's the Hero builds if you want to be adventurous.
Just have a look in the development section and see which best suits your needs
Be aware the Haykuro's ports, Rogers and Hero all require haykuro's SPL (which needs the new radio or you will brick).

Okay well I downloaded Cyanogen's build, so what are the features and how to use them?

Just read through the thread. Most are automatic optimization mods (CPU scaling, audio mods) which just make for a nicer experience. There are also others like the HTC Camera app which is a vast improvement over the stock camera app. APPS2SD is also atomatic so all you need is a second partition on your card formatted to ext3, so you will have much more room for market apps.
* Based on AOSP 1.5r2, various collected patches, and some help from JF-1.51-ADP
* Enhanced ramdisk which uses optimal mount options and smart startup
* Includes E2FSProgs for checking and converting Ext filesystems
* Apps2SD is automatic! All you need is a second partition (ext).
* Includes script to upgrade to ext3 (from recovery mode, see FAQ)
* Supports ext2/ext3/ext4 for Apps2SD
* Includes HTC Framework and various applications
* Includes latest HTC_IME with long-press, calibration, and compact QWERTY.
* Launcher with 5 screens and auto-orientation and compact drawer layout
* Sexy pattern-lock from Sapphire and Stericson's lock screen
* Clean filesystem shutdown at poweroff/reboot, and fsck at boot (no FS corruption!)
* Includes T-Mobile IM application, Amazon MP3 (with Stericson's hack), and updated Google Maps
* Does not require "DangerSPL"
* Highly optimized kernel with many extra modules
* Includes Haykuro's APN list
* Tweaked frequency scaling options to be more responsive
* Maximum CPU scaling frequency set to 528MHz (3.3)
* Various enhancements to the Settings app including extra partition space
* Runs /system/sd/userinit.sh after A2SD setup and before starting the runtime for user scripts
* Microsoft Exchange support (Work Email from myTouch)
* Includes Compcache modules
* Linux cgroups for better app prioritization
Click to expand...
Click to collapse

Knightsofwar210 said:
Okay well I downloaded Cyanogen's build, so what are the features and how to use them?
Click to expand...
Click to collapse
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything

How do I partition my 8GB Micro SDHC with one that is 500mb and is ext3? Thanks.
EDIT - Saw your post above.

B-man007 said:
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything
Click to expand...
Click to collapse
Experience? Ha, this is just like custom firmware for the Playstation Portable. Custom firmware is the equivalent of a rooted build so I do have experience with this type of thing.

I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.

I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917

Knightsofwar210 said:
I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
What your going through is experience.....this isn't just flashing psp roms xD
Custom firmware flashing is extremely simple on the g1..... this is like going into the ROM and changing things up. The mods im talking about involve lots of terminal and adb commands and you really shouldnt be using them unless you understand what its doing. If you have plenty of experience in linux,then you should be able to find lots of interesting things to do in the development section.

Knightsofwar210 said:
I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917
Click to expand...
Click to collapse
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago

B-man007 said:
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago
Click to expand...
Click to collapse
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.

Knightsofwar210 said:
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work

B-man007 said:
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work
Click to expand...
Click to collapse
Yes I have cyan running with a new theme I installed, and yes I do have a secondary system storage, I'm stuck here - http://forum.xda-developers.com/showthread.php?t=531988
B-man007 said:
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
I'll try this.

NAND flash help

--Formality of newness here--
I'm a noob to flashing my Vogue, so maybe I'm just ignorant of something important, but I'm a programmer, been using linux for a decade, and comfortable hacking devices, so don't spare me any gory details.
Also, many thanks to everyone who has made this possible. The haret bootloader version is amazing, and I'm sure a nand version is even nicer.
--My problem--
I've never tried to flash my Vogue, so as of a few hours ago, it was a vanilla, but updated Sprint Vogue with a type 3 display panel. It has the latest official Sprint radio (3.42.30?).
I started with tatnai's recently stickied FAQ thread in this forum (I can't link it due to being a new member). I followed the steps linked to unlock my phone. I installed 2.31 CoKe and verified it in my bootloader. So far so good.
I then used RUU and VOGUIMGx320.NBH from the 2010-02-04 dated version of vogueeclairnbh.zip file. It succeeded. Resetting the device loads the Android linux kernel. All is well.
Now for my failure. I load a FAT32 formatted SD card with, say, myn's WarmDonut androidinstall.tar file under /sdcard/andboot/. [ignorethis]and copy in the latest zImageEclair (renamed to zImage of course) and the latest initrd.gz, [/ignorethis] hold the center button down through a hardware reset, it boots into the replimenu like this (minus whitespace and some truncation):
Code:
Android Installer
Choose options for installation or choose defaults
(*) Sys on NAND
( ) Sys on SDCard [...]
( ) Sys on Ext [...]
(*) Data on NAND
( ) Data on SDCard[...]
( ) Data on Ext [...]
[B]1. Fix Permissions[/B]
2. Clear Dalvik Cache
3. Backup /data
3. Restore /data
4. Wipe /data
5. Start Recovery Mode
6. Quit
For more info [...]
Notice that option #1 is not an install option. Running #1, I get errors from umount saying it can't mount /system or /data, which I assume is because it's not installed yet. Same with options 2 through 4. Recovery mode does allow me to mount the SD card as a block device, and quit leaves the installer menu.
Intution is telling me that it's not unlocked correctly and that the Android Installer can't write to nand, but without sourcecode for it, I'm kind of at a dead end of my knowledge, and I can't find a similar issue posted here or at PPCgeeks.
What am I missing? Let me know if I need to provide any more information.

If you're flashing to nand, you don't need a(n additional) zImage or initrd. maybe they're throwing the installer off.

I've removed them from my andboot folder, so that androidinstall.tar is the only file in there and retried. The same menu is presented without an install option. I also just reflashed the phone with the non-eclair nbh and got the same results.
I've used this andboot no-rootfs method with haret before, so I've got a pretty clear idea of what should happen, I just don't know what's gone wrong.

Ok, silly question re: folder structure - you should have just /andboot on the root of your sdcard, not /sdcard/andboot. I can't tell from your post.

burrgrinder said:
--Formality of newness here--
I'm a noob to flashing my Vogue, so maybe I'm just ignorant of something important, but I'm a programmer, been using linux for a decade, and comfortable hacking devices, so don't spare me any gory details.
Also, many thanks to everyone who has made this possible. The haret bootloader version is amazing, and I'm sure a nand version is even nicer.
--My problem--
I've never tried to flash my Vogue, so as of a few hours ago, it was a vanilla, but updated Sprint Vogue with a type 3 display panel. It has the latest official Sprint radio (3.42.30?).
I started with tatnai's recently stickied FAQ thread in this forum (I can't link it due to being a new member). I followed the steps linked to unlock my phone. I installed 2.31 CoKe and verified it in my bootloader. So far so good.
I then used RUU and VOGUIMGx320.NBH from the 2010-02-04 dated version of vogueeclairnbh.zip file. It succeeded. Resetting the device loads the Android linux kernel. All is well.
Now for my failure. I load a FAT32 formatted SD card with, say, myn's WarmDonut androidinstall.tar file under /sdcard/andboot/. [ignorethis]and copy in the latest zImageEclair (renamed to zImage of course) and the latest initrd.gz, [/ignorethis] hold the center button down through a hardware reset, it boots into the replimenu like this (minus whitespace and some truncation):
Code:
Android Installer
Choose options for installation or choose defaults
(*) Sys on NAND
( ) Sys on SDCard [...]
( ) Sys on Ext [...]
(*) Data on NAND
( ) Data on SDCard[...]
( ) Data on Ext [...]
[B]1. Fix Permissions[/B]
2. Clear Dalvik Cache
3. Backup /data
3. Restore /data
4. Wipe /data
5. Start Recovery Mode
6. Quit
For more info [...]
Notice that option #1 is not an install option. Running #1, I get errors from umount saying it can't mount /system or /data, which I assume is because it's not installed yet. Same with options 2 through 4. Recovery mode does allow me to mount the SD card as a block device, and quit leaves the installer menu.
Intution is telling me that it's not unlocked correctly and that the Android Installer can't write to nand, but without sourcecode for it, I'm kind of at a dead end of my knowledge, and I can't find a similar issue posted here or at PPCgeeks.
What am I missing? Let me know if I need to provide any more information.
Click to expand...
Click to collapse
If you start recovery mode and plug your device into a linux box you should be able to connect to it using adb (http://cs-alb-pc3.massey.ac.nz/vogue/files/adb) use "adb shell" to get a shell and you will be able to see why it doesn't find the tar file. Look at /init, see how it mounts the sdcard and try the same commands.
Hope this helps.

agree with the comments above. your problem does not have to do with unlocking. it has to do with your file structure or formatting of the sdcard or something along those lines preventing it from seeing the file.
things that may be wrong:
1. the andboot folder is named incorrectly
2. the andboot folder is not in the root of the sdcard (as mentioned above)
3. your androidinstall.tar is not correctly named, or is still zipped, or something of that nature. make sure you look at that file from your computer with it set to NOT hide extensions, so that you aren't missing that it is actually called androidinstall.tar.zip.
as dzo said, from the install menu hit Start recovery mode, then you can hook it up to any computer (usb mass storage function will work) and check all of these out.

Sorry about all this fuss. I finally determined that this menu is caused by a bad/misformatted SD card. The device was seeing it as in the slot, and would even mount it correctly in recovery mode, but nothing could be read by the Vogue. After swapping out to a new one, all is well.
Thanks for everyone's quick replies and insight.

[HOWTO] Rooting, Installing - Android SDK, Custom Recovery, Custom ROM's

This thread is primarily intended for n00bs.​
I would like to say thanks to xda forum members: Noejn, Zecanilis, drellisdee, The_ERROR etc. Also thanks is due to Godlike! at tech-mania.com for his tutorials. Thanks is due especially to The_ERROR for proofreading the post and to other users for their suggestions written in the thread.[/SIZE]
---------------------------------------------------------------------------------------------
NEW - 3 May 2011 - Simplified Guide to Root & install version 1.2 of Custom Thunderg Recovery by AmonRa/modified by Drellisdee on LG P500
ALWAYS MAKE A BACKUP BEFORE CUSTOMISING YOUR PHONE.
[CUSTOMISING A PHONE USUALLY INVOLVES: ROOTING >>>> INSTALLING CUSTOM RECOVERY >>>> INSTALLING CUSTOM ROM]
The instructions written below have been tested by me using an Indian unbranded GSM model of LG P500 which came with stock Android 2.2.1 (V10C). The procedure to be followed for any LG P500 phone is the same.
This post is split into 4 major sections -
1. INSTRUCTIONS FOR ROOTING
2. INSTALLING ANDROID SDK ON A WINDOWS PC (This step is needed to install Custom Recovery on phone using adb from PC. Can be omitted if Recovery is installed from phone using Terminal Emulator)
3. INSTALLING A CUSTOM RECOVERY
4. INSTALLING CUSTOM ROMs
MUST READ: If you haven't read this thread already, please do read it - Dictionary for n00b - What is.../What does ...mean?
---------------------------------------------------------------------------------------------
1. INSTRUCTIONS FOR ROOTING
To know your present firmware version - Go to Settings/About Phone
Only phones which come with stock android 2.2 could be rooted till recently.
UPDATE - 24 April 2011 : A tool called 'GingerBreak APK' is able to root phones running stock android 2.2, 2.2.1 & 2.2.2. Read about it HERE. This tool enables rooting without the need for downgrading the firmware to 2.2. If 'GingerBreak APK' doesn't work out for you, continue reading to understand the procedure to root your phone after downgrading your firmware. Note: 'GingerBreak APK' permanently roots your phone. Also,GingerBreak might not install BusyBox and SuperUser apps properly on your phone. These apps are required by many rooted apps for their proper functioning. So, use Root Checker from android market to verify the proper installation of these 2 apps.
If your phone runs stock android 2.2, enable 'USB Debugging' on Phone (Settings/Applications/Development). Install z4root (copy the apk file to the sd card and open the file after browsing to the location using the phone's file manager), run it and root the phone. Find it HERE.
Choose the permanent root option as it is still possible to force unroot if needed.
Restart the phone and launch z4root to check the root status. A successful rooting should show 'Unroot' option when z4root app is opened.
{Note: z4root automatically installs Busybox and Superuser application(which appears as an icon in your app drawer) on the phone.}
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
For phones that came with stock 2.2.1 or 2.2.2 installed, rooting first involves downgrading the firmware to 2.2.
Downgrading the firmware can be done with KDZ-FW-UPD.exe (procedure outlined below)
(KDZ-FW-UPD.exe has been claimed to work best with windows xp 32bit.)
FIRST: DOWNLOAD THE Android 2.2 FIRMWARE FOR YOUR DEVICE. For this, go to: [ROMS] Original LG Firmware list and read about the procedure to download the original firmware.
{Tips: Use Ctrl+F in browser to search for Country name, Remember to change the alphabet in 2 places in the final link to download the firmware, Do not bother about the 'CDMA' tag attached to country code. It works for the GSM model phones too. If the link to find out the country codes doesn't work, use the 2nd method mentioned in the post to find out the country code using your phone's IMEI or ESN number }
Download the required Firmware onto your PC.
Links to Original firmware versions for Indian P500 are mentioned in THIS POST
Procedure to install original firmware using KDZ-FW-UPD.exe ( KDZ FIRMWARE UPDATER ) This procedure can also be used to restore the stock firmware and recovery onto your phone in case you want to give your phone to the service centre during warranty period as the phone will appear similar to as you bought it from the store.
[Note: This procedure was used to install V10B_00.kdz(android2.2) over V10C_00.kdz(android2.2.1) on an unbranded Indian GSM model of LG P500 using a Windows 7 Ultimate 64bit updated to date PC.]
1. Install LG PC Suite IV from SD card which came with phone by connecting the phone to PC through USB cable. This is done to install the drivers for the phone on the PC (the procedure is as follows)
- Enable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard & Phone Storage menu.
- Connect phone to PC with the USB Cable.
- Press the 'Turn on USB Storage' button which appears on phone.
- Browse to the folder containing the 'LG PC Suite IV' on the phone's SD card using Windows Explorer and run the LG Installer file. PC Suite will now install on your system along with the required drivers for your phone.
- Cancel setting up PC Suite or continue setting up PC Suite if you want to Sync or backup the phone data.
- After closing PC Suite, Safely remove the USB device from your system.
- Press the 'Turn off USB Storage' button on phone screen.
- Detach the USB Cable.
- Disable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard &Phone Storage menu.
Alternatively, I also tried installing the latest drivers via LG Mobile Support Tool from LG's website (available HERE) but KDZ-FW-UPD.exe (mentioned below) crashes when run. This could be happening only to me, so please try for yourself before writing off this method.
2. For my comfort more than anything else, I switched off the screensaver and other power saving features on the PC and also set the screen timeout delay on the phone to 30 minutes.(Settings/Display/Screen Timeout)
3. Charge the phone to the maximum.
4. Enable USB Debugging on Phone (Settings/Applications/Development).
5. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
6. Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.)
7. Unmount the SD card from the phone (Settings/SDcard & Phone Storage).
8. Open phone back and remove the SD Card.
9. Download KDZ_FW_UPD_EN.7z onto your PC and extract it to a folder. Available HERE.Direct Download Link. (MD5 of 7zip file - 813A28BE9182AB604A1D43E745CE7AD7)
10. Run the msxml.msi file and complete the installation.
11. Connect the phone to PC with USB Cable.( If you are using a desktop PC, make sure you use USB ports that are in the back of your PC, avoid the front ports.)
12. Run KDZ_FW_UPD.exe from the extracted folder.
13. Chose TYPE as 3GQCT & Phone Mode as DIAG.
14. In the 'KDZ file' space, browse for the firmware you want to install. (In this case V10B_00.kdz)
15. Press the 'Launch software update' button.
16. The firmware flashing process is now underway.
If all goes well, in 5-10 minutes the phone will be flashed with the new firmware.
I shall describe in detail what happened with my phone - 10-15 seconds after launching software update on PC, my phone screen turned blank and in a couple of seconds the phone entered the 'Emergency Mode'. During this mode the screen was yellow with Emergency Mode written along the middle of the screen. The phone stayed in the same way till the Software update procedure finished on the pc and the phone turned blank. I waited a while for it to reboot but after a minute or so, I manually switched on the phone. The phone came alive and following the LG boot animation, the android logo screen came up. The phone spent about 2 whole minutes in that state before booting up fully and entering the home screen. Update: Wait till phone reboots by itself or wait for a while before manually switching it on.
17. After booting up fully, detach the phone from the pc.
(If the phone gets stuck in the android boot logo screen during first boot, doing a hard reset by pressing and holding the VolDown+Home+Power buttons may resolve the problem.)
Go to 'About Phone' in Settings and confirm the change from 2.2.1 or 2.2.2 to 2.2.
Root the phone using z4root as mentioned before.
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
IN CASE OF PROBLEMS DURING DOWNGRADING FIRMWARE, read the following thread completely. Various types of errors and various measures to correct them including some innovative ones like shaking the phone etc. are mentioned here - [HOWTO] Phone not responding at all - last chance to repair. It is advisable to read this thread completely before attempting to downgrade the firmware using KDZ_FW_UPD.exe to become aware of all the possible problems you might encounter and their possible solutions.
PS: Here is the link to the phone drivers that came with my SD card. One user reported a problem wherein kdz updater would recognise the phone but the update process would fail during kdz unpacking. the problem was resolved by using the drivers i sent him. So, if anyone has the same issue, it might be worthwhile to try out the following drivers. I wouldn't advise everyone to follow this method, but those of you who are feeling lucky might try it out. Download Link
---------------------------------------------------------------------------------------------
2. INSTALLING ANDROID SDK ON YOUR WINDOWS PC
This step is required to install Custom Recovery on your phone using adb from your PC. Using a Custom Recovery, you can make a backup of your current ROM, restore backups, create partitions on your SD card, wipe your phone and the SD card and then also go on to install Custom ROMs using the Flash from Zip option.
Installing a Custom Recovery can also be done in other ways. Using Android SDK from your PC is just one method.
(Custom Recovery can alternatively be installed on your rooted phone using the commands given in the next section using a Terminal Emulator. This method removes the need for installing Android SDK on your PC and connecting your phone to PC. Download Terminal Emulator from Android Market. Install on phone. Run it and give it root permissions when prompted by the 'Superuser' application. As mentioned in the next section, copy the 2 files (flash_image & the custom recovery image file) needed to install Custom Recovery onto the root directory of SD card. Reboot phone. Open terminal emulator and type 'su' without the quotes and press Enter. This will take you to the root shell (#) from the default user shell($). Carefully type in the 7 commands mentioned in the next section one after the other. After typing in the last command (reboot recovery) and pressing enter, WAIT. The phone will reboot. Custom Recovery will have been succesfully installed on your device.
Hint: Copy the installation commands as a text file to phone & copy and paste the commands one by one into terminal emulator using a text editor. Please make the necessary changes to the installation commands depending on the recovery version used)
To install Android SDK on PC, there are a few requirements/downloads which have to be completed first:
JDK (Java Development Kit) - Download Here
JRE (Java Runtime Environment) - Download Here
Android SDK installer - Download here
So after all the downloads are completed, you are good to go. Run PC as Administrator.
First of all install the JDK, then the JRE and then the SDK Installer.
{If when android sdk installer is run, you get an error that JDK or JRE is not detected even after their installation, wait for a while, shut down the computer and restart and run the SDK installer once again.}
Make sure that while installing the android sdk, the installation directory should be the root of a partition i.e. it should be in the following form: C:\android-sdk, where you should replace the letter C with the letter you have assigned to the partition that you want to install it in.
Now that the Android-SDK is installed, go to the installation directory and start the SDK Manager. You need to add the components of the Android SDK to your installation. Before that I would like to inform you that you can save time if you download only what is necessary. If you are on Android 2.1 then you should download the 2.1 sdk, for 2.2 the 2.2 sdk and so on. You do not need to have all the versions for this thing to work. Just your version would do. So to start adding components, I recommend that you read THIS
After installing the desired components, you need to do perform some simple steps in order to use the adb terminal just like the cmd terminal for Windows.
For that purpose, here are the steps to be followed:
Right click My Computer, select Properties, and click Advanced System Settings. (Windows XP users - Right click My computer and just click Properties and select the Advanced Tab)
Click on Environment Variables, in the System Variables box, scroll down to the variable name 'Path' and double click to edit it
It would read something like " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static".
Here you need to add a semicolon ( ; ) and add the path of the tools folder in android-sdk.
It should finally be like this " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\android-sdk\platform-tools {or the location where adb.exe resides on your system}
Click OK wherever asked and then restart your computer.
Now open a command prompt window and type adb and hit enter. If a terminal window is displayed, you have done it all right.
If it gives some error message, read the article carefully and see what you have messed up with.
---------------------------------------------------------------------------------------------
Tip:
Using adb - How to install apps from PC without having to copy them first to the SD card?
If you want to install apps in one click, all you need to do is download the .apk file of your application to your PC and set the open with option to this batch file which you can download HERE
Save the batch file on the desktop of your PC before setting the option to 'Open With'.
---------------------------------------------------------------------------------------------
3. INSTALLING A CUSTOM RECOVERY
(Procedure of installing Custom Recovery using a terminal emulator from your phone instead of installing android SDK on your PC and connecting your phone to PC is mentioned in the last section.)
UPDATE - 3 May 2011 : Very simple way of installing Custom Thunderg Recovery by AmonRa/modified by Drellisdee version 1.2. Originally posted by ungaze in this post.
1. Download Android Terminal Emulator from Android Market. Install it on your rooted phone.
2. Download the file "amon_ra_recovery_installer.zip" from here or here. Check the MD5 hash value of the downloaded 'zip' file using tools like HashTab etc. before proceeding further. Correct MD5 value : 86db8a52b01f049cadb8f097a4c5bd9e
3. Extract the contents of the 'zip' file to the root of the sd card (ie. not inside any folder) using tools like 7-Zip or WinRAR or any other similar tool.
4. Open the terminal emulator app on your phone and type in the command 'su' without the qoutes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions to the terminal emulator app. Click 'Allow' and proceed. You will notice that the shell prompt has changed from the previous user shell '$' to root shell '#' in the emulator app.
5. While in the root shell '#', type in the following command and press Enter. Wait and the phone will reboot into the Custom Recovery.
Code:
sh /sdcard/rf.sh
Once you are up and running with a rooted phone, you will need to download the 2 files needed to install the Custom Recovery. They are:
Download No:1: flash_image - (This file is the same one needed to install any of the 3 versions of Custom Thunderg Recovery by Drellisdee given below)
Download Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link - requires registration at androidforums.com. (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Download No:2: Custom Recovery image file - Choose & download any version among the 3 available after reading what is written below.
Custom Thunderg Recovery by Drellisdee has versions 1.1, 1.2 and 1.2.1 at the time of writing this. I personally prefer version 1.2 as it supports backup & restoration of ext4 Partition on SD Card. Version 1.2.1 is a little experimental in nature & it may not fit all devices as it has a size near 5 MB.
Link to xda-forum thread for Custom Recovery P500/Thunderg - HERE.
The different versions of the Custom Recovery image files are available at the following pages
Custom Recovery P500/Thunderg v1.1
Direct Download link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Mirror Link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Custom Recovery P500/Thunderg v1.2
Direct Download link - (MD5 of zip file - 217FC9115899A41195CF124CAF07B880)
Custom Recovery P500/Thunderg v1.2.1
Direct Download link - (MD5 of zip file - 388aac16b1184ab15b5500b2b32d914c)
Please check the MD5 hash values of downloaded files to ensure that files are not corrupted using tools like HashTab etc.
Now to install Custom Recovery, Copy the two files [ the chosen recovery image file (*.img) & the flash_image file (flash_image) ] and paste in the root of your SD card (root means the directory L:\ where L is the letter for your Phone's USB Storage. In short, don't create a folder and paste the files inside it on your SD card).
{Note that the recovery image file should have an .img extension and flash_image file should have no extension when placed on the SD card}
Reboot the phone. Connect phone to PC.
The next step requires Android SDK to be installed on your PC.If you have installed the Android SDK, follow these steps:
Go to Start Menu & Run and type cmd (run as Administrator)
In the cmd window, type adb. If you have installed it correctly, you will see a lot of text on the screen. If you get an error message then you have probably not installed the Android SDK properly.
Type adb shell and hit enter
Type su and hit enter
See your phone at this time and touch the 'Allow' option which SuperUser shows you
Now the terminal window will have a # sign appended to it instead of the previous $ sign. See this screenshot for a better understanding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now one by one, copy the following lines, in the serial order and paste it into the terminal window and press enter following each line(right click on window and paste, CTRL + V won't work)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (if it gives error message here, simply proceed to the next step)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (If the recovery version chosen is different from v1.2, type the appropriate file name of the recovery image here instead.)
reboot recovery
Click to expand...
Click to collapse
Wait. The phone will reboot now.
Note:{If you get this error after step 4
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
Simply move on to the next step.
If you get any errors other that those mentioned here, please do not proceed with the last command of 'reboot recovery'. If you do so, recovery may not be correctly installed and you will lose all data on the phone as the phone will be reset to factory defaults. Please go back to the instructions and see what you have done wrong.
NOTE: If on booting into the recovery you get the following message at the bottom of the screen -
E: 'Bad Boot Message'
Don't panic, it's perfectly normal and you can proceed with what you want to do from the recovery.}
Detach the phone from the PC.
To access the Custom Recovery, turn off the phone and then press & hold Home+Vol Down+Power buttons to boot into the Custom Recovery.
---------------------------------------------------------------------------------------------
Once you have booted into the recovery, the touch screen won't work. The actions assigned to the different buttons are given here. Use them to navigate through the different options in Custom Recovery.
Up & down: vol-up and vol-down key
Select: Menu key (left most)
Back: Back (3rd from left)
---------------------------------------------------------------------------------------------
What does Custom Recovery look like & What does it do?
Note: In Custom Recovery versions 1.2 and above, zips can be extracted from inside folders. So, save the zips in a folder named AAA and flash the zip after browsing inside the folder through recovery. The folder name should be named 'AAA' so that it appears among the first on the recovery screen, since scrolling is not an option in recovery.
Note: There is also an unofficial port of ClockworkMod Recovery availble. I do not recommend this recovery for newbies as it isn't compatible with all Custom ROM's out there.
---------------------------------------------------------------------------------------------
4. INSTALLING CUSTOM ROMs
BEFORE FLASHING ANY ROM, DO A NANDROID BACKUP FROM CUSTOM RECOVERY
Since all the ROMs have their own kinds of partitions to be created and other requirements, you can check them at the ROM specific pages.
General procedure to follow for installing a Custom ROM
Boot into Custom Recovery
Wipe your cache, dalvik cache, SD card
Make partitions according to the ROM requirement
Wipe cache again.
Connect Phone to PC
Toggle USB MS and paste the ROM zip file to a folder called AAA in the root of the SD card
Disable USB MS.
Detach phone from PC.
Select 'Flash from zip' option in Custom Recovery menu
Select the ROM file
Flash the ROM file
After flashing is finished, Reboot the phone.
Note: It will take some time to flash and reboot into your new Custom ROM. The phone may stay with the boot logo displayed for a number of minutes. Do not switch off phone during this period.
---------------------------------------------------------------------------------------------
In case of problems with phone, read: [HOWTO] Phone not responding at all - last chance to repair
Also read: [READ FIRST] [REF] Repository of howto's, roms, kernel, etc.
If you feel benefited by this thread, I humbly request you to rate this thread and vote it to the front page. The option to rate and vote is present in the title bar of the thread on the right side.
Please post your feedback. Also THANKS is always welcome. Use the THANKS button (below right) if you feel that I deserve it.​
Update - 24 April 2011 - New rooting method without needing to downgrade firmware.
Update - 3 May 2011 - Very simple way of installing Custom Thunderg Recovery
Update - 3 May 2011 - Added Simplified Guide to Root & install Custom Recovery on P500

i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help

Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!

I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?

FnH84 said:
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
Click to expand...
Click to collapse
Have you installed the drivers for the phone on your computer? If you haven't, your phone will not be detected when toggling usb mass storage.

saileshchowatia said:
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Click to expand...
Click to collapse
Did you read the thread I have linked to at the end of the article? it may help you.

FnH84 said:
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
Click to expand...
Click to collapse
The procedure for downgrading the firmware is included in the article. The procedure is the same for installing any version of original firmware on the phone.
Procedure to change from one custom rom to another various with each rom.some may need a wipe while others might need repartitioning your sd card.

victortangocharlie said:
Have you installed the drivers for the phone on your computer?
Click to expand...
Click to collapse
Yes. It worked fine before. I tried to flash with CM7, and something went wrong. The whole SD-card is empty, works on another phone though. However, Windows will not recognize it no matter what I do

Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?

victortangocharlie said:
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
Click to expand...
Click to collapse
Both. I put the memory card on another phone and it said it was empty. Also, custom recovery says it's empty and from mount menu, I can see it keeps unmounting.

Have you tried another card on your phone?

victortangocharlie said:
Have you tried another card on your phone?
Click to expand...
Click to collapse
I managed to get the card work via another card reader. I put the zip files on it and trying again now. Hope it will work.
EDIT: It works!!!

nvm.....................

Glad to hear it.

Sorry for noob question, but after downgrade to 2.2, root, can I flash any rooted 2.2.1 ? And is there any?

Once you have rooted your phone, you can install any custom rom meant for p500. This includes all android versions. And, you don't have to apologise for being a noob, this thread is meant for noobs primarily. everyone has to start someplace. There are many rom's accessible on this forum including android versions 2.2 to 2.3.3. I suggest you try Nessy#Euridice ROM by Dookmatt. I am using it and it is easy to set up.it is based on android 2.2.2

Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?

Guess, you will have to ask the people who make the rom's. I don't know about the cm7 rom.haven't used it myself.

IFLPI said:
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Click to expand...
Click to collapse
rooting a stock Rom is hard where as as rooting a custom made rom is easy because u only need the framework to create ur custom rom....
and about CM7 u can choose between many flavours.... its upto u ..

hi
hey man thanks for the wonderful tutorial!!
i just broght my phone 2weeks back. got it after lots of requests to dad!!
i wanna try all the stuff but im damn scared if i would brick my phone..
although i have the exact same phone as yours..unbranded indian optimus one with v10c
should i try it or is there a risk that ill brick it..?
if i brick it.. is there a chance that i can get it repaired? or will the lg ppl refuse to support me because i screwedwith it??
thanks in advance!!

[Q] Full tutorial to put KitKat on N1. Who wants to test?

Hi all, I wrote a long-winded Tutorial to put Evervolv KitKat on a stock N1. I don't have a stock N1 (I stumbled all the way through this process and got done yesterday, was so excited I wrote this tutorial) and don't know how to get it back to stock, so I'm wondering if anyone who has one and has experience putting new ROMs on other devices would like to test this out and let me know if anything doesn't work as written. Please go ahead if you like and reply your updates! Once it's dialed I'll make it a thread in the N1 ROMs forum.
Here's the text:
How to put KitKat on a Nexus One (And have computing power & space to spare):
Things you'll need:
1. A Windows/Linux computer with internet connection, USB port, and terminal
2. A USB Cable
3. A Nexus One with the most recent stock gingerbread rom (Settings->about, look for Android 2.3.6 or GRK39F, else apply/google updates to get to that version)
Before you begin, note that you're playing with a generally safe form of fire, but when playing with fire, you may brick your phone. The maker of this guide and any sites you visit during the process assume no responsibility, the user assumes full responsibility for lost work and damaged or ruined phones. Your warranty will be voided about six times over. Save all your stuff somewhere, save apps with Titanium Backup (Google it) or something, and do a full Nandroid backup (Goog that too) before you begin. You will be fully wiping your phone and SD card multiple times. Make sure at every step of the process that your battery is at least half full. Running out of battery during an update can cause bricks. In this guide, “Boot” means standard boot, the way it normally turns on. Not hboot or fastboot or recovery.
I did part of this from a Windows7 computer on Cygwin and part on Ubuntu 12.04, each presented some annoyance but by far the greatest was due to my Linux ineptitude with PATH and Root. If you're trying the same, I've made an appendix for that.
It may help to have a brief conceptual overview of what you'll be doing in case you run into snags and have to step out of the walkthrough. Your N1 has a few basic parts: Internal memory that is chopped into 3 partitions: One for the system files (System) , one for the files that they will need to make during the first bootup and use in order to operate, along with your apps and their created files (Data) and one for temporary files that your OS and apps can regenerate (Cache). Somewhere in there it also has space for a Radio (that also includes some critical power functions, flashing a new radio is the easiest way to brick an N1 but we won't), as well as a Recovery partition and an Hboot&Fastboot partition. We will be messing with Recovery and Hboot. The virtual machine that turns all the friendly pseudo-english computer code into 1s and 0s for the processor to deal with is called Dalvik, named after a town in Iceland where some old dev's family is from. It has its own Cache (the VM, not the town, as there are no longer any fish in Iceland ). It's SOP to wipe Cache & Dalvik before and after applying any updates, and wipe Data (Factory reset) before applying most updates. Sometimes when my phone bogs I reboot to recovery and wipe caches just for funsies. This makes it take longer to boot the phone and to use each app just the first time after that, while the files are created fresh. The phone also should have an SD-Card. You should have or buy an 8+MB, Class 10 SD card. The class relates to read/write speed, anything less than 10 will noticeably slow your Nexus One's operation. Why?
Because we're going to put some of your operating system on the SD card. We're going to use a special recovery system (aka recovery ROM) called “4ext” to partition your SD card. Mine is 16GB, partitioned to 14GB for storage and 2GB to use as fake internal memory, where my system's Data and Cache live. The KitKat System files that normally live on internal memory's System partition are too big for a normal N1, so we'll use a special Hboot called BlackRose to repartition your internal memory so you can fit KitKat, and then after you first boot it up we'll use an app called Mounts2SD to install a startup script so that every other time you boot it up after that, it will know to find Data and Cache on the SD card. In order to install BlackRose, you'll need to be running CyanogenMod Rom as your main OS, and in order to do that you'll need ClockWorkMod Recovery ROM. So the installation order will be: ClockworkMod recovery->Cyanogen7OS (Gingerbread based)->4ext recovery to partition SD card->BlackRoseHboot to repartition internal memory->Evervolv KitKat-based N1 ROM-> run Mounts2sd for startup scripts ->reboot to your new life among the anatomically modern cyborgs (and then you're on your own for getting all your apps and music and contacts and stuff back on the phone from wherever you saved it).
Ready? Here we go!
1. Install the Android SDK on your computer.
1. Get the appropriate version here: http://developer.android.com/sdk/index.html
2. Unzip it.
3. Run the setup.exe (if using windows)
4. When asked which packages to install, choose “Android SDK Tools”, “SDK Platform Android 2.1″, and “Usb Driver package” (If you use eclipse, check that last link for instructions on using the ADT plugin (Not the same ADT that cuts your paycheck, much less inept))
5. Make sure the USB drivers installed properly (windows).
1. Go to printers and devices in the control panel, or device manager
2. If you see an android device with no warnings, you're golden. If it has warnings, right click it and go properties->update driver (driver can be found in your android sdk directory where you unzipped the sdk bundle, in \usb_driver).
6. Boot up your N1 and plug it in to the computer. If the computer recognizes it and they play nice, you're set with the sdk. To extra check, open terminal and cd to the sdk's platform-tools folder that should contain the adb utility. Type #adb devices and see if it comes up with a message telling you that it's running a daemon on a port like 5037, and then lists something like HT9CPP800063 device. This is your phone, it's telling you you're beyond connected. You've got the sdk working. Else have your friend Google help you get the SDK properly installed.
2. Root the phone so it will let you dig in.
1. Put your N1 in USB debugging mode (Settings > Applications > Development > USB Debugging)
2. In the terminal, in the platform-tools folder, type #adb reboot bootloader. (((My phone has a power hardware issue and will not reboot while plugged in ever to any mode ever at all ever, if yours does too you can unplug (first type #adb kill-server to make it ok to unplug) the usb cable, power down, wait five seconds, and hold the trackball and power button to power back up into the bootloader, then plug in again. There was a lot of unplugging, waiting fifteen seconds, booting while holding buttons, plugging in, adb devices -ing that I will omit henceforth due to low likelihood that you have the same problem.)))
3. Using the onscreen directions on the phone and the hard buttons, navigate to fastboot mode. It may be unresponsive and throw some not-found messages for five seconds before it lets you do anything.
4. In the terminal on your computer, in the platform-tools folder, type #fastboot devices to see if your devices is connected (it should come up with the same HT#XXX###### number).
5. This step will gain Root access, unlock the bootloader, and WIPE ALL YOUR ****. Now type #fastboot oem-unlock . You may have to accept the warranty voiding. If for whatever reason it doesn't work, use this method http://code.google.com/p/bexboot/, and unzip the files to the platform-tools folder.
6. Using the phone buttons, reboot. Your little lock logo during the bootup should be unlocked now.
7. Power down and boot again for good measure. Re-enable usb debugging in the phone app dev settings.
3. Get ClockworkMod Recovery.
1. Download koush's ClockworkMod Recovery from : recovery-clockwork-5.0.2.0-passion.img and put it in the platform-tools folder.
2. To make sure the file is not corrupted and will not brick your goods, check the md5sum. This is the result of a complicated equation that easily reveals even a single flipped bit in the file by vastly changing the output. Google how to do this, in windows you'll need to download a tool like winmd5free. The output for this particular file should be: md5: 45716c8d51ed2375873f01f0b14b2184 If it's anything else don't use it.
3. Reboot to the bootloader again, either by #adb reboot bootloader or by powering up while holding the trackball, and navigate to fastboot.
4. Verify that you're connected with #fastboot devices
5. Flash ClockworkMod Recovery by typing #fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
6. It should give a success message. Reboot to recovery from the fastboot menu. It should be a sweet new blue and white ClockWorkMod recovery. Power down and reboot to recovery by holding volume up as you power up, just for good measure.
4. Get CyanogenMod7 ROM.
1. On your computer, go to http://download.cyanogenmod.org/?device=passion&type=stable and download the latest stable CM7 zip. Put it in the platform-tools folder.
2. Check its md5 as you did in part 3.
3. Do #adb-devices, which should give you that serial again, and the word recovery.
4. Place the zip file on the root of your SD card by doing #adb push cm-7.2.0-passion.zip /sdcard/
5. If that last step failed, try running #adb shell mount /sdcard or #adb kill-server then #adb devices then #adb shell mount /sdcard, then try the push again. Or mount the sdcard through the recovery menu before running that push command. Or use your computer's file system to drag and drop the .zip to the root (lowest) folder of the sd card.
6. Using the recovery menu, in backup and restore options, backup your current ROM.
7. In the format menu, do a wipe data/factory reset. Wipe the cache and dalvik cache while you're at it.
8. Back in the main recovery menu, do install zip → choose zip from sd card.
9. Select that CM7 zip file.
10. Return to the main menu and reboot the system. It should come up with a totally different looking leaner meaner version of Gingerbread, that gives you more control and speed and saves battery. But even with this system, given modern app sizes, you'll soon run out of room on the internal memory if you stop now. And besides, you're having too much fun.
5. Get 4EXT recovery
1. Go to 4ext.net and download the free .apk file: http://www.4ext.net/get.php?apk Congratulations if you're about to install your first not market app (apps are now .apk, not just something you get from the store's GUI.). Save it in platform-tools. Or, to be really nice to Max, you can just buy the app in the play store and skip the next two steps.
2. Enable USB debugging, plug in and #adb-devices.
3. # adb install 4EXTRecoveryUpdater.apk. You should get back a success message in a fistful of seconds.
4. At this point you may need to back out to regular settings, turn on wifi, and hook up to your wifi router.
5. Open the 4ext recovery updater app. Go to settings. Allow superuser permissions and everything else. It should detect Nexus One, connect to the internet, and boot you back to the main menu.
6. Go to online install. They're all release candidates and no stable versions, so just go with the newest one. Select install.
7. Wait for it to finish and then reboot to recovery, either by # adb reboot recovery or manually. You should have a beautiful new touchscreen recovery.
6. Partition your SD Card
1. In recovery, go to tools->partition sd card->remove all partitions and start from scratch.
2. For the first Ext partition, where you'll be keeping a good chunk of your OS, The consensus online is not to go above either 1.5GB or 2GB. I'm working fine with 2GB aka 2048MB.
3. You can skip the 2nd Ext partition.
4. The internet says Swap size should be 0.
5. Internet says File system should be ext4. This should do the partitioning, the rest of your SD card will still be great for storage as before.
7. Repartition internal memory using BlackRose:
1. I have never used BlackRose on Windows, but here goes: go here : http://forum.xda-developers.com/showthread.php?t=1270589 and download this zip archive: http://forum.xda-developers.com/attachment.php?attachmentid=1016437&d=1334971685; It has windows and linux files. The site also has a manual in case this walkthrough lets you down.
2. Unzip it into a folder in your platform-tools. Execute it with a ./ in linux or a .exe in win. It should say waiting for devices.
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
4. Blackrose is rumored to have an interactive guide to partitioning, but it didn't work for me and at least some other genius on the internet, but being an industrious Austrian, he figured out the fix: Run Blackrose in Editor mode. Type resize as prompted.
5. The post here http://forum.xda-developers.com/showthread.php?t=2540366 on Evervolv KitKat implies that 250MB for System works with enough space for Gapps (Google does not allow their standard apps like Play Store to be included with Mod roms anymore, so you will need to install them from recovery too, but they distribute them bundled so it's not hard.), and some commenter said 260MB, but that didn't work for me long enough to run startup scripts and move some of it off. So I had to redo it and I went with 265MB for System and 10MB for Cache, which is working fine. Give it a name, I went with Kat.
6. BlackRose will shut down, but it will leave a golden turd in the form of a file called hboot_brcust.nb0 probably in the folder called “other.” That's what you want.
7. Put that file in the same folder as the Blackrose utilities fastboot-l and fastboot-w if it's not already there. Then boot your phone into fastboot again, via adb or manually. I think. Maybe try this from being standard booted up if the next part doesn't work.
8. Run # fastboot-l flash hboot hboot_brcust.nb0 . Windozers should use fastboot-w instead. Blackroot will wait for the device again.
9. Reboot your phone into the bootloader manually, by holding the trackball while powering up. The image should install on this boot, resizing your phone's internal memory partitions.
10. Run # fastboot -w. Your Bootloader should be loaded up, with the 1st line saying something about BlackRose and the 2nd line saying 265/10/161. This is how you know it worked. That 265 is where it's at for KitKat. Your main OS had been destroyed, but your Recovery ROM should still work.
8. Install Evervolv KitKat.
1. Go here http://evervolv.com/devices/passion and download the latest stable release. At press time that's the 4.0.0p4.2 version. Save it to platform-tools.
2. Reboot to Recovery from the menu in the BlackRose bootloader.
3. Do # adb devices. Then do # adb push ev_passion-4.0.0p4.2-perdo-squished.zip /sdcard/ . If it doesn't work, try using the touch recovery menu to toggle mount USB, then push, then unmount. Or mount USB, use the computer's file system to move the file to the root of the sd card, then unmount USB. Or try as root if you're using linux.
4. From the main recovery menu, select install zip from SD card → choose zip → select the ev_passion-4... zip. Wait up, it could take a while.
5. Success!! Right? Right. #adb kill-server, you can unplug now and won't need to plug back in! Reboot the phone, you're getting perilously close! This boot could take five plus minutes, or just one, but be patient.
9. Install Gapps.
1. You are such a lucky dog. Gapps bundled updates are available through the Evervolv toolbox. So you can get Play Store and everything else will come easy. Go to settings → wifi, turn it on, hook it up to your wifi router.
2. Back up to settings, and go Evervolv Toolbox → Updates and swipe over to the Gapps section. Tapp the most recent Gapps-kk zip. Tap the down arrow to download.
3. Reboot manually to recovery.
4. From the main recovery menu, select install zip from SD card → choose zip → select the gapps-kk... zip. This could also take a sec.
5. Reboot again! You're almost done! When it's all loaded up, Play Store should now be installed, as well as various google options that you can enable through the Evervolv settings.
10. Install Mounts2sd.
1. Go to the Play Store and get Mounts2sd.
2. Hit the top right corner for application settings. You'll need to install a startup script. Agree, give it permanent superuser status.
3. Reboot.
4. Go back into Mounts2sd, and go to the Tool menu (Wrench). Note that boxes aren't checked unless they're green-checked.
5. Enable the Cache to move cache partition to data or sd-ext. Storage threshold is up to you. Make sureApplications, Libraries, Data, and Media are all checked. Dalvik should stay unchecked, System apps can too.
6. Reboot again.
11. You're done!!! Or at least we're done. You still have to restore your apps and put all that music back on and figure out how to resync your contacts and... Good Luck.
12. If you want to get extra tricky, it's believed to be possible to leave app data on the real internal memory by default, and use Titanium Backup to move the data of most of your apps to the SD-ext, thereby leaving the data of your favorite apps on real internal memory. Use at your own risk.
ENJOY!!
Appendix 1:
Linux PATH env: I put all my android stuff in a file called androidy, so my path to my platform-tools was /androidy/adt/sdk/platform-tools, and my blackrose was in there too. So to set my PATH, I used: $ export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sean/androidy/adt/sdk/platform-tools:/home/sean/androidy/adt/sdk/platform-tools/blackrose_120421/binary"
In order to make sure that while using it as root (as was necessary for some fastbot operations), I referenced the same PATH instead of the messed up root PATH, I used sudo env PATH = $PATH a few times.
Appendix 2:
The only actual bug I've noticed in a few days with this ROM is that my Chrome bookmarks don't add shortcuts to the homescreen when I tell them to from within Chrome. The widget-adder (longpress homescreen) has a bookmark option though, so if you bookmark it you can put it on the homescreen from there.
Huge Thanks to everyone involved with ClockworkMod, Cyanogen, 4Ext, BlackRose, and Evervolv!
Sources:
http://wiki.cyanogenmod.org/w/Install_CM_for_passion
http://nexusonehacks.net/nexus-one-...n-how-to-unlock-bootloader-on-your-nexus-one/
http://marian.schedenig.name/2012/07/22/installing-android-4-ics-on-the-google-nexus-one/
http://forum.xda-developers.com/showthread.php?t=2540366&page=24

Wooooh, Amazing book ! Everything is soo.... deep. In my opinion, tutorials should be only few lines.
Some mistakes :
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
In my mind, big steps should be :
1) Backup SD, and SMS and Apps
2) Root
3) Install recovery (TWRP is advised by evervolv, but CWMRecovery is OK)
4) Partition SD
5) Install Blackrose (using 260mB system)
6) Flash ROM
7) Flash GAPS
8) A2SD Y N Y
Notes :
About SD-Ext size, i recommend reading this post from his creator : http://forum.xda-developers.com/showthread.php?t=1716124
A2SD is an old version of INT2EXT+
Using terminal is not friendly for beginners. Avoid it at maximum.
Provide a link for a MD5 sum checker.
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)

ldFxl said:
In my opinion, tutorials should be only few lines.
Click to expand...
Click to collapse
This tutorial doesn't need to exist at all. All the information is available elsewhere on the internet, I did nothing original. Its only value is that it puts all the information in full detail in one place so you don't have to look in the forums for elaboration on each line of a more concise tutorial. Hopefully with info this detailed, someone with more chops than me could script it.
ldFxl said:
Why installing CM7 and then backing up ? (You can install non market apps without CM7, and when flashing CM7 you erase all user data)
Why using m2sd if the rom has a built-in feature called a2sd ?
Click to expand...
Click to collapse
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
ldFxl said:
Why installing CWM then 4EXT recovery ? (TWRP is a touch one, and you can flash recovery once you have root access)
Click to expand...
Click to collapse
4EXT is also touch, CWM cannot repartition SD. If you can go stock to TWRP this might be the best option. Or if not, stock to 4ext.
ldFxl said:
"You should have or buy an 8+MB, Class 10 SD card" ? typo ?
Click to expand...
Click to collapse
Yes! Thanks.
ldFxl said:
Using terminal is not friendly for beginners. Avoid it at maximum.
Click to expand...
Click to collapse
Don't you have to use terminal to use the built in A2SD? At any rate, it didn't work for me (I'm kind of a beginner), Mounts2SD's GUI seemed a little more beginner friendly. Also I certainly wouldn't have been able to make BlackRose work
ldFxl said:
Provide a link for a MD5 sum checker.
Click to expand...
Click to collapse
Good idea
ldFxl said:
I don't know if it works with actual stock rom, but when i rooted my n1, i used SuperOneClick. Plug, Click, Wait, Smile. (I still have it if needed)
Click to expand...
Click to collapse
I once used SuperOneClick on another phone, it looked like it struggled and finally worked with a DDoS style attack, it seemed simpler to just do it the way the manufacturer intended (if that's even a thing). But I suppose if it works with one click it really is simpler as seen by the user. Anyone have a report on whether it worked from stock N1?

Fituate said:
I had already installed CM7 when I thought to write this, Marian (my 3rd source) seems pretty skilled as he is the only one who could make BlackRose work for me so I trusted his advice that it was the easiet procedure he found. Have you put TWRP Recovery on from stock after unlocking the bootloader (fastboot oem unlock)? And have you successfully repartitioned SD (fat32 &ext4) from TWRP? If so and you want to quickly write up the steps, I'd gladly replace my steps 3-6, that would save people a lot of time and doing.
Click to expand...
Click to collapse
On my first flash, i was pretty beginner, so i followed a tutorial ; ) . And they used CWM. But flashing a recovery procedure from .img file doesn't differ with the recovery. TWRP allows you to partition SDCard. I did it last week (on HTC wildfire S, TWRP 2.6 as for N1).
Flashing step is the same -> just replace img file name. You can get it Here (From official TWRP Website)
Procedure from TWRP Website said:
Download the above file. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fasboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
6. Partition your SD Card
1. In recovery, Tap Advanced
2. Tap Partition SD Card
3. Set 2048 (MB max) on EXT Size and 0 on Swap Size
4. Tap EXT4 then swipe to start partitioning
Fituate said:
3. Reboot your phone manually. BlackRose should hijack the startup, install itself, and quit. Boot your phone up again.
Click to expand...
Click to collapse
Backrose is a custom Bootloader-> it replaces your HBoot/Fastboot
You don't need to reboot your phone to install blackrose. You just need your phone in ADB over USB, then the win setup will install blackrose.
Once done, run setup again, your phone will automaticaly go to HBoot, then choose 1, and 1 again.
Then enter "resize", "260" and "8".
In case that the installer don't work correctly, you can get flashable HBOOT from [Provide a nb0 (texasice recommend 260/8/168) AND MD5 Checksum]
While googling to find some infos (I don't remember me unlocking my bootloader) I found this guide : http://forum.xda-developers.com/wiki/HTC_Nexus_One/Flashing_Guide
Apperently SuperOneClick does not even need unlocked bootloader on 2.3.3 or previous ...
Isn't what we are trying to write down ?
There are many links pointing to this forum aswell.

[HOW-TO][ROOT][4NOOBS] Resize sdcard0 and internal storage to maximize space for apps

Ever since I bought my Xperia TL (LT30at), I've been upset at the ridiculous allocation of onboard memory: only 1.97GB were available for apps. The rest was allocated to an emulated external SD card, which meant that any app installed on it would lose widgets and suffer from other weird glitches on reboot. I've searched all over the place and couldn't find a solution until @teidus shared his method (per my research, it has been used on older devices from other manufacturers as well). I tried it and adjusted the steps to ensure 100% compatibility with my phone (and added explanations so that other devices could be tested).
See proof in the attached screenshots.
WARNING: You will lose a lot of data if you don't follow this guide!
WARNING: These operations require a rooted device. If you are running unrooted Android 4.3 or newer, you cannot proceed.
NOTE: All of these changes will be reversed if you flash an FTF that includes partition-image.sin.
DISCLAIMER: I'm not responsible for bricked devices and data loss from power surges, hardware damage, or changes to the linked software. Always check the native manuals for all the tools listed here!
Required Downloads:
1. Flashtool, which includes ADB (got questions about it? - ask them here) - requires installation
2. @[NUT]'s dual XZDualRecovery. I'm linking to v2.7.94 BETA installer. If you wish to check for a more recent version, go to his download page and do a page search (CTRL+F) for XT-lockeddualrecovery[version-goes-here].installer.zip. (got questions about it? - ask them here) - unzip to a location you'll remember (say, C:\xperia-resize\recovery\)
3. FTF with your phone's 4.1.2 firmware - save it to the default Flashtool firmware directory (C:\flashtool\firmwares\)
4. File system utilities (attached) - unzip to a location on your phone's physical SD card you'll remember (say, fs-utils\)​
The Guide (skip all the way to the bottom for the short guide if you know how to backup and flash FTFs):
1. Back up all data stored on internal storage:
Option 1: Connect your phone to the computer and save it to a computer drive.
Option 2: Open a file manager on the phone and copy it to a physical SD card (/sdcard1).​2. Back up your current installation with either Online Nandroid or your current recovery and remove the SD card for safety.
3. Flash your phone with basic 4.1.2 install.
3.1 Turn off the phone.
3.2 Launch Flashtool.
3.3 Click the thunderbolt icon on the left and select Flashmode.
3.4 Select the appropriate 4.1.2 FTF from the list (it'll be there if you saved it to c:\Flashtool\firmwares\).
3.5 Tick "No final verification" checkbox on the right, click Flash, and when prompted, hold the VOLUME DOWN button, and connect the phone to the computer. The operation will take about 10 minutes. DISREGARD THE INSTRUCTIONS IN THE ANIMATION. Xperia T/TL doesn't have a hardware Back button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3.6 When flashing is complete, boot the phone.​
4. Connect your phone to the computer and let the computer recognize it.
5. Enable USB debugging.
5.1 Go to (System) Settings -> Developer options and flip the switch in the top-right corner of the screen.
5.2 Look a bit down (toward the middle of the screen) and check USB debugging.​6. Install the dual recovery.
6.1 Go to the location on your computer where you extracted dual recovery (e.g., C:\xperia-resize\recovery\).
6.2 Double-click install.bat.
6.3 Press 3 on your keyboard for the option 3. Installation on unrooted ROM.
6.4 Follow the instructions on your computer's screen.
6.5 When you will try to reboot the phone back into Android, the recovery will prompt you to root the OS. Do that.​
7. Boot into PhilZ Touch recovery by opening App Drawer, starting NDR Utils, and selecting the appropriate option.
8. When the phone boots into recovery, connect it to the computer.
9. Start ADB.
If you don't know where ADB is, press WIN + R on your computer keyboard, type cmd in the pop-up window, hit ENTER, then copy & paste this command (paste by right-clicking the command prompt window): cd C:\Flashtool\x10flasher_lib. Then type adb shell and hit ENTER again.​10. Execute the following commands one-by-one (you can copy & paste, hit enter, and wait for the output):
Code:
umount /storage
parted /dev/block/mmcblk0
print
These commands unmount all drives, launch parted utility for mmcblk0 (onboard flash storage), and show the partition table.​11. Record the beginning of the partition Userdata and the end of the partitionSDCard. These are the limits of your new partitions The numbers are in megabytes (MB) unless specified.
For Xperia T/TL, Userdata begins at 1621 and SDCard ends at 15.6GB. Xperia V (and any other device with less than 16GB of storage) will definitely have a different value.​
12. Remove the last 2 partitions by executing the following commands:
Code:
rm 14
rm 15
13. Calculate the new end point for Userdata, which is also the new start point for SDCard:
1621 (or another number you recorded in step 11) + additional space = new end. I added 4GB (4 ×1024MB = 4096MB) so my new end point was 7865. I advise to add at least 2GB (2048MB) to feel safe about having enough storage for apps. DON'T TRY TO REMOVE SDCARD ALTOGETHER BY ALLOCATING ALL OF THE AVAILABLE SPACE TO USERDATA! Emulated storage is coded into OS environment and requires additional modifications to work properly.​14. Create and name new partitions by executing the following commands (don't copy the text in parentheses):
The system might throw several errors in the process. When prompted, just type ignore and hit ENTER.​
Code:
mkpartfs logical ext2 1621 7865 (change the numbers as appropriate for your device)
name 14 Userdata
mkpartfs logical ext2 7865 15.6GB (change the numbers as appropriate for your device and notice the GB to make sure the partition extends to the end of the onboard storage)
name 15 SDCard
quit
These commands create the partitions with ext2 file system and given beginning and end parameters, rename them as required, and close parted.​15. "Damage" the internal, emulated SD card so that it could be formatted properly later.
Tap Mounts and storage -> Format /storage/sdcard0 -> default and confirm the operation.​16. Insert the physical SD card (sdcard1) that you removed in step 2 back into the device.
Make sure it's mounted by tapping Mounts and storage and checking its status (it should say unmount /storage/sdcard1/). If not, mount it by tapping on the appropriate option.​17. Execute the following commands one-by-one in the ADB command prompt:
Code:
cd /storage/sdcard1/fs-utils (the directory name will be different if you didn't follow my conventions)
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
These commands convert Userdata partition into the appropriate ext4 filesystem, which is not supported natively in the recovery environment.​18. Reboot the device into full Android.
18.1 Remove the physical SD card for safety.
18.2 Tap Back until you make it to the top level of recovery. Then tap the top option Reboot the device.​19. When Android loads fully, you'll notice a notification about storage file system. Tap it and follow the prompts to format it.
20. Insert the physical SD card and reboot into the recovery you used to create the backup in step 2 to restore it.
In PhilZ, that's Backup and Restore -> Restore from /storage/sdcard1.​21. Reboot back into full Android and copy the files saved from internal storage back into it. Then reboot again so that apps recognize the data.
DONE!​
Short guide/list of ADB commands and other events (*enclosed in asterisks*) if you know the safety drill:
Code:
*flash 4.1.2 & install dual recovery*
*boot into PhilZ Touch*
adb shell
umount /storage
parted /dev/block/mmcblk0
print
*record start point of Userdata and end point of SDCard*
rm 15
rm 14
mkpartfs logical ext2 1621 7865
name 14 Userdata
mkpartfs logical ext2 7865 15.6GB
name 15 SDCard
*Mounts and storage -> Format /storage/sdcard0 -> default -> confirm*
*insert physical SD card*
*Mounts and storage -> Mount /storage/sdcard1*
cd /storage/sdcard1/fs-utils
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
*remove physical SD card*
*reboot*
*format emulated SD card*
*reboot recovery*
*restore backup*
*reboot*
*restore sdcard0/*
*reboot*

nice, i was looking for a way to increase the /data after switching to Omni and ART
Will try ASAP..
PS: i think this thread should be added in ALL IN ONE THREAD Section:good::victory::victory::victory:

raghulrr said:
PS: i think this thread should be added in ALL IN ONE THREAD Section
Click to expand...
Click to collapse
That's a request to @gregbradley.

#6 would be the most welcomed way to resize partitions, but unfortunately it's not so easy as it was e.g. with ZTE Blade. But altogether it's good to know that you can resize them now! Thanks!

nice tutorial brother... i'll be trying tommorow
Sent from S5J using Tapatalk

Thanks
Thank you I was definetly looking for it
Thanks

@TO: I couldn't test ist but I think made a little mistake:
I think you want want to execute the programms wich are in the Directory in wich you made the cd. So you have to add ./ before each command.
I don't have such a device, to test it by myself: You said you have to make a new virtual SD. Some ROMes have a vold.fstab in /etc. Mayby it't enough to change this file to be able to remove the SD Partition completly.

Partitionator said:
@TO: I couldn't test ist but I think made a little mistake:
I think you want want to execute the programms wich are in the Directory in wich you made the cd. So you have to add ./ before each command.
I don't have such a device, to test it by myself: You said you have to make a new virtual SD. Some ROMes have a vold.fstab in /etc. Mayby it't enough to change this file to be able to remove the SD Partition completly.
Click to expand...
Click to collapse
I was writing the guide as I was executing commands so everything is exactly as I entered it. I obviously removed all steps that turned out to redundant and wrong.

Will that work with the Xperia Arc S?!
What is the difference between your method and the [MOD]{CM10.1}{CM10.2}{CM11}{AOSP}Working Int2Ext for Xperia 2011 [ART-compatible]?

metaljoker said:
Will that work with the Xperia Arc S?!
What is the difference between your method and the [MOD]{CM10.1}{CM10.2}{CM11}{AOSP}Working Int2Ext for Xperia 2011 [ART-compatible]?
Click to expand...
Click to collapse
These are some great questions! This approach is very different from all Int2Ext scripts:
HUGE NOTE: This works only for devices where the onboard NAND capacity is at least 8GB. That means that 2011 devices with 1-4GB of onboard memory are better off with mounting the physical SD card as /data.
This is a semi-permanent modification to the partition table (it'll work fine if you do factory reset and flash a new ROM .zip but the allocation will be reset every time you flash FTF, possibly even if you exclude partition-image because each .sin contains its offset and size bits).
This approach is compatible with locked bootloaders because support of init.d comes from the kernel.
This approach allows you to allocate as much or as little of onboard NAND storage to each of the 2 partitions (/data and /storage/sdcard0) used for storing apps and their data instead of just allocating the entire physical SD card.
This approach allows you to live a life independent of your physical SD card (i.e., your apps still work and your phone boots up just fine even if the physical SD card dies).

bsined said:
These are some great questions! This approach is very different from all Int2Ext scripts:
HUGE NOTE: This works only for devices where the onboard NAND capacity is at least 8GB. That means that 2011 devices with 1-4GB of onboard memory are better off with mounting the physical SD card as /data.
This is a semi-permanent modification to the partition table (it'll work fine if you do factory reset and flash a new ROM .zip but the allocation will be reset every time you flash FTF, possibly even if you exclude partition-image because each .sin contains its offset and size bits).
This approach is compatible with locked bootloaders because support of init.d comes from the kernel.
This approach allows you to allocate as much or as little of onboard NAND storage to each of the 2 partitions (/data and /storage/sdcard0) used for storing apps and their data instead of just allocating the entire physical SD card.
This approach allows you to live a life independent of your physical SD card (i.e., your apps still work and your phone boots up just fine even if the physical SD card dies).
Click to expand...
Click to collapse
That's a great info! There are steps in the thread that aren't clear enough not only for me but also for others, that's for sure.
For those who have partitioned their SDcard, unlocked BL & rooted phones, should have their own line of steps, however I feel like I might mistake something in case I use it.
P.S.:
01. You didn't answer my question whether this is compatible with my phone, did you?!
02. There should be a video demonstration for this method for it is new in this website, don't you think?!
03. unzip to a location on your phone's physical SD card you'll remember (say, fs-utils\) what do you mean by remember "say, fs-utils\" ??

@up
It depend on your partition scheme, which ones are on the end of memory (physical).
Wysłane z mojego GT-I8160 przy użyciu Tapatalka

batlin said:
@up
It depend on your partition scheme, which ones are on the end of memory (physical).
Wysłane z mojego GT-I8160 przy użyciu Tapatalka
Click to expand...
Click to collapse
I have a 1GB partitioned SDcard for the apps! Does this info help?!
How the heck could I install the TeamWin Recovery Project (TWRP) ??!!

metaljoker said:
That's a great info! There are steps in the thread that aren't clear enough not only for me but also for others, that's for sure.
For those who have partitioned their SDcard, unlocked BL & rooted phones, should have their own line of steps, however I feel like I might mistake something in case I use it.
P.S.:
01. You didn't answer my question whether this is compatible with my phone, did you?!
02. There should be a video demonstration for this method for it is new in this website, don't you think?!
03. unzip to a location on your phone's physical SD card you'll remember (say, fs-utils\) what do you mean by remember "say, fs-utils\" ??
Click to expand...
Click to collapse
SD partitioning and status of the bootloader should not have any effect on the process. However, root is required in order to install recovery.
1. Theoretically, this mod is compatible with any device that has the latest version of CWM or TWRP. I've tested it with Xperia TL and Nook Tablet 16GB. However, if your device's total available user storage (/data + /storage/sdcard0) is 4GB or less, you will likely require a physical SD card for storing your apps, user data, and whatever is written to sdcard0 by default.
2. Although I realize that some people learn best by watching instead of reading, this procedure is very quick when your device's recovery supports all the required commands. I repartitioned Nook Tablet in barely 10 minutes. If I were to make a screen cast of it, 90% of the video would be just moving the mouse around or waiting for the phone to boot. The longest operation is to create the journal, which takes about 10 seconds by the phone.
3. "Say" = "for example". Create a folder on the physical SD card and call it "fs-utils".

bsined said:
SD partitioning and status of the bootloader should not have any effect on the process. However, root is required in order to install recovery.
1. Theoretically, this mod is compatible with any device that has the latest version of CWM or TWRP. I've tested it with Xperia TL and Nook Tablet 16GB. However, if your device's total available user storage (/data + /storage/sdcard0) is 4GB or less, you will likely require a physical SD card for storing your apps, user data, and whatever is written to sdcard0 by default.
2. Although I realize that some people learn best by watching instead of reading, this procedure is very quick when your device's recovery supports all the required commands. I repartitioned Nook Tablet in barely 10 minutes. If I were to make a screen cast of it, 90% of the video would be just moving the mouse around or waiting for the phone to boot. The longest operation is to create the journal, which takes about 10 seconds by the phone.
3. "Say" = "for example". Create a folder on the physical SD card and call it "fs-utils".
Click to expand...
Click to collapse
WOW! I am very impressed for answering each question in an informative way! W E L L D O N E! ! :good:
I'll take my chances since I've read your lines. Wish me luck!
I'll get back to you once I encounter the unexpected, or maybe not. We'll see! Here goes nothing...

metaljoker said:
WOW! I am very impressed for answering each question in an informative way! W E L L D O N E! ! :good:
I'll take my chances since I've read your lines. Wish me luck!
I'll get back to you once I encounter the unexpected, or maybe not. We'll see! Here goes nothing...
Click to expand...
Click to collapse
I realized that I've forgotten to include roll-back instructions if anything goes wrong. Here's the short version:
1. You better have made Nandroid backup of your system and have copied the content of your /storage/sdcard0
2. Find a stock, rootable FTF on the forums, download it, and flash it using Flashtool
3. Install recovery on the reflashed device
4. Restore backup from recovery and copy the content back to /storage/sdcard0

ADB Shell
Sorry if this silly questions
I want use your mod on my XV, but I've some problem (on Windows 8.1 Pro 64bit)
1. When I reboot from PhilZ Touch recovery for a first time, i don't get root question
2. Cause i don't get about root question, so i try root from PhilZ Touch recovery menu
3. When I try run adb shell on TWRP recovery, there no device notif (I already install Windows Update : http://support.microsoft.com/kb/2917929 and use Flashtool Driver 1.5)
So, am i mis something? Where i got wrong? Thanks before

thunder888 said:
Sorry if this silly questions
I want use your mod on my XV, but I've some problem (on Windows 8.1 Pro 64bit)
1. When I reboot from PhilZ Touch recovery for a first time, i don't get root question
2. Cause i don't get about root question, so i try root from PhilZ Touch recovery menu
3. When I try run adb shell on TWRP recovery, there no device notif (I already install Windows Update : http://support.microsoft.com/kb/2917929 and use Flashtool Driver 1.5)
So, am i mis something? Where i got wrong? Thanks before
Click to expand...
Click to collapse
I guess is the problem is with Win8 and ADB drivers. However, just to be sure, try attaching the phone to the computer to test ADB when it's booted to PhilZ and full Android. If the phone is not recognized, search the forum for a fix (there should be one). Unfortunately, my only Win8 machine is Surface RT, which doesn't accept ADB drivers, so I can't test anything myself.

bsined said:
I guess is the problem is with Win8 and ADB drivers. However, just to be sure, try attaching the phone to the computer to test ADB when it's booted to PhilZ and full Android. If the phone is not recognized, search the forum for a fix (there should be one). Unfortunately, my only Win8 machine is Surface RT, which doesn't accept ADB drivers, so I can't test anything myself.
Click to expand...
Click to collapse
Yes, i agree. But if I attach phone at full Android and run ADB, it can be recognized. I'll reinstall my windows and will give a report later. Thanks :good:

My dearest friend...
My phone was revered back to original. In order to have it rooted it took me 17 hours
1] Regarding the "Flash your phone with basic" my phone's already rooted which means that I do not need to flash an FTF file. In case I need to, which version?! Would that harm anyhow?
2] I'm stopped at 6.5. Because I do not have the TWRP installed on my phone.
3] My Recovery is CWM-based Recovery v6.0.4.7, if no problem then how can I Start ADB?!!!
Obviously, I'm not even half way. I need your help my friend!
* Xperia Arc S