Database Develop

Cyanogen wiki guide? Does it work for newbies?

I plan on installing the CyanogenMod once I get my Nexus One. I have heard many positive things from him, especially from G1 owners
My question is, is the Cyanogen wiki guide sufficient for someone who can read and understand directions? It's located here:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod
I have read everything and it seems to be laid out nicely! I haven't encountered any steps that were confusing at all.
My only question is the lack of partitions. I've watched some youtube videos and they are always taking about setting up partitions (using words like "ext4" and "ext6"). But this guide doesn't mention anything regarding this. Does this guide do the partitions automatically without user intervention?
edit:
I actually do have questions.
Regarding the "Flash Recovery."
1. Note: The Recovery.img should NOT be on the SD Card, it should be in the current working directory.
2. On the command prompt you opened earlier, type in the following command.....
Where exactly is the current working directory? Do I need to select it or do Ii simply enter the command "fastboot flash recovery Recovery.img"
Many thanks! I haven't done anything yet but just want to go over the steps so I don't get lost!

the working directory will likely be the tools directory of your SDK, or whatever directory you have fastboot.exe in.
Before writing in fastboot flash recovery, you need to navigate to the tools directory in the cmd prompt, either by typing "cd" then the /route/to/the/directory, or in vista and above, go to the tools directory, right click while holding shift and go to the option "open command window here"
Don't worry about partitions unless you intend to use apps2sd.

Easiest way to parition for apps2sd is with amon ra. Just follow the prompts, no directions required. Figuring out what size you want those partitions or swap, not so easy. I searched for ages without coming across anything concrete. Ended up going 64 meg swap, 1 gig ext 4 and the rest FAT.

the working directory is the place you extract the AndroidSDK file (usually in the local C drive, so it may look like this: C:\AndroidSDK-windows\tools\
once you install the usb drivers and get adb/fastboot working, you'll usually be running cmd commands from inside the "tools" folder
those directions in his wiki are perfect; as for partition, if you want to use Apps2SD, it's really simple to do as it's one of the options under Amom-RA's recovery image

Thanks guys!
So the partitioning is actually related to Apps2SD? This means that I do all the partitioning after the rom is installed?

Before, all data is lost when you partition. You can mount the sd after you partition while in amon ra and move the rom over then dismount it. Before you flash wipe everything. My advice would be to do a nandroid on the old sd to start. Then copy all files from the old sd to the pc, only takes a minute.

EDIT:
I went to the following http://forum.xda-developers.com/showthread.php?t=613217 and it worked that way. I am not sure why that method works but it does
Hmm it seems I have trouble already.
After I install the USB drivers via Android SDK, and then enable usb debugging mode,
When it installs drivers, one of them doesn't install:
{
"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"
}
I tried using USDBDeview to remove em and reinstall em, but I end up with the same message.
I am using Windows 7 64 bit
attached below is my android sdk settings:
and what happens when i go to command prompt:

Ok if driver isn't installed, go into device manager and update Nexus One driver yourself.
Browse for this DIR C:\AndroidSDK\android-sdk-windows\usb_driver (where you have installed it etc)

Just seen you're edit, my bad.

Leoncc said:
Ok if driver isn't installed, go into device manager and update Nexus One driver yourself.
Browse for this DIR C:\AndroidSDK\android-sdk-windows\usb_driver (where you have installed it etc)
Click to expand...
Click to collapse
No apologies! You are correct though. That is the why to install it if it can't automatically find it
Anyway, I managed to install it! The instructions are very clear so props to whoever created that wiki page!!

I do have one more question and it's regarding Apps2SD.
On this page, it gives instructions on how to enable and disable it.
When I go to the option menu, it doesn't allow me to select it. It's faded out. What do I do to go about enabling this?

i thought cm's instructions were enough; but thanks to the help i got here, i was able to root.

bozeefus said:
I do have one more question and it's regarding Apps2SD.
On this page, it gives instructions on how to enable and disable it.
When I go to the option menu, it doesn't allow me to select it. It's faded out. What do I do to go about enabling this?
Click to expand...
Click to collapse
Usually that means you need to partition or if you are partitioned to switch to ext 4 on CM

I cannot install Cyanogenmod again before unbricking my Touchpad.

Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language

This is what appears on display after running ACMEInstaller3.
{
"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"
}
I guess the problem is the difference between the reported free space, and the the real free space on system.
How can I fix that?

Gabonjour said:
Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language
Click to expand...
Click to collapse
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244

chicle_11 said:
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Thank you very much but... I cant access to Touchpad as root user when using novaterm in windows and linux. It doesnt say [email protected] It only shows a "]" symbol. When I type "lvm lvscan" or any other command, it says "This command doesn exist"...

[Q] TWRP installs and loads on my KFTT, but will not load ROM

I've installed TWRP on my KFTT, and the recovery menu loads fine, but when I try to load the system ROM (either the stock Kindle Fire HD one or CM) it sits on the blue kindle fire screen for a long time before the screen gets all corrupted (looks like TV static but motionless.) Here's what I have done, twice:
1) Installed full system recovery with KFFirstAide via my Skorpn factory cable
2) Started it once, not giving my Amazon login or Wifi info
3) Root with "Root with Restore by Bin4ry"
4) Insert Wifi info and log into Amazon, download ES File Explorer
5) Install FireFlash, use it to install TWRP (checking the current system version, to use the right bin)
6) Reboot into recovery mode, make a backup with TWRP, use TWRP to install CM11 and gapps-kk
Even trying to boot into the stock Kindle OS (before or after backing up/restoring with TWRP) has the same result. Help? I'm tired of dealing with the idiosyncrasies of the Kindle version of Android, and I want something closer to stock.

m2pt5 said:
I've installed TWRP on my KFTT, and the recovery menu loads fine, but when I try to load the system ROM (either the stock Kindle Fire HD one or CM) it sits on the blue kindle fire screen for a long time before the screen gets all corrupted (looks like TV static but motionless.) Here's what I have done, twice:
1) Installed full system recovery with KFFirstAide via my Skorpn factory cable
2) Started it once, not giving my Amazon login or Wifi info
3) Root with "Root with Restore by Bin4ry"
4) Insert Wifi info and log into Amazon, download ES File Explorer
5) Install FireFlash, use it to install TWRP (checking the current system version, to use the right bin)
6) Reboot into recovery mode, make a backup with TWRP, use TWRP to install CM11 and gapps-kk
Even trying to boot into the stock Kindle OS (before or after backing up/restoring with TWRP) has the same result. Help? I'm tired of dealing with the idiosyncrasies of the Kindle version of Android, and I want something closer to stock.
Click to expand...
Click to collapse
Okay, before you install your ROM.zip file(s), do you do a factory wipe?
>>>Sent from my homebuilt TARDIS running Android 4.0.3... or maybe it's a rooted Kindle Fire HD<<<

I do a factory wipe from the recovery console, yes. I forgot to mention that.

m2pt5 said:
I do a factory wipe from the recovery console, yes. I forgot to mention that.
Click to expand...
Click to collapse
Which version of TWRP do you have? I'm not sure, but I think you need the latest version (2.6.3.1) to flash anything based on Android 4.4.
>>>Sent from my homebuilt TARDIS running Android 4.0.3... or maybe it's a rooted Kindle Fire HD<<<

Yep, the recovery image is kfhd7-twrp-2.6.3.1-recovery.img.

Make sure you are clicking on all appropriate boxes, including stack, also try formatting sdcard.... But save files onto computer beforehand
{
"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"
}
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

[Q] N9005 Cyanogenmod nightly device name failure

I rooted my SM-N9005 with CF-Autoroot and tried installing the hltexx cyanogenmod 11 nightly Rom. First, I flashed Clockworkmod 6.0.4.5 via Odin and put the .zip of the cm rom on the external sd card. When I tried installing the Rom, it failed: This version is for hltexx, you have htle
As far as I read, htle stands for various samsung devices, but htlexx stands for SM-N9005. I looked up my device description in the build.prop:
ro.product.name=hltexx
ro.product.device=hlte
The first attempt to fix this was to simply change the build.prop (which might have been a stupid idea). CWM reported the same problem as before... :/
Then I flashed twrp 2.6.3.7. and tried flashing the cm rom. Not only did it report a problem with the wrong phone model, it also reported that it couldn`t mount drive E (Usbstick).
My next troubleshooting approach was to erase (not delete) the file "metadata", which determines the right device as hltexx. That caused the installation to abort at the point where it usually reports the error... Adapting the metadata to hlte caused the installation to abort, too.
All metadata approaches where done on both cwm and twrp, I also tried restoring the build.prop, so I don`t manually create a difference between the Rom target device and what the ro.product.device tells.
For the sake of it, I also wiped the phone multiple times....without any impact apart from me having to get back old data soon
Someone please help me solve this problem, I did everything I could to get the rom to work. This is my first Android device and attempt to flash a custom Rom, so please don`t laugh at me if I did a stupid mistake somewhere

Ie0n said:
I rooted my SM-N9005 with CF-Autoroot and tried installing the hltexx cyanogenmod 11 nightly Rom. First, I flashed Clockworkmod 6.0.4.5 via Odin and put the .zip of the cm rom on the external sd card. When I tried installing the Rom, it failed: This version is for hltexx, you have htle
As far as I read, htle stands for various samsung devices, but htlexx stands for SM-N9005. I looked up my device description in the build.prop:
ro.product.name=hltexx
ro.product.device=hlte
The first attempt to fix this was to simply change the build.prop (which might have been a stupid idea). CWM reported the same problem as before... :/
Then I flashed twrp 2.6.3.7. and tried flashing the cm rom. Not only did it report a problem with the wrong phone model, it also reported that it couldn`t mount drive E (Usbstick).
My next troubleshooting approach was to erase (not delete) the file "metadata", which determines the right device as hltexx. That caused the installation to abort at the point where it usually reports the error... Adapting the metadata to hlte caused the installation to abort, too.
All metadata approaches where done on both cwm and twrp, I also tried restoring the build.prop, so I don`t manually create a difference between the Rom target device and what the ro.product.device tells.
For the sake of it, I also wiped the phone multiple times....without any impact apart from me having to get back old data soon
Someone please help me solve this problem, I did everything I could to get the rom to work. This is my first Android device and attempt to flash a custom Rom, so please don`t laugh at me if I did a stupid mistake somewhere
Click to expand...
Click to collapse
First of all this is the wrong forum. You are in the ATT Note 3 forum.
Secondly, you don't erase the meta inf folder.
If you want to fix your updater issue, go to the meta inf>com>Google>android and find the updater-script
Send it to me and I will fix it for you so it will install
Sent from my SM-N900A
{
"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"
}

Bricked device

Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
{
"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"
}
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.

Leader0fr4tz said:
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Click to expand...
Click to collapse
adb root; adb remount

Does your phone get recognized by your pc?
Mine went black a few days ago and i cant do anything.

LuK1337 said:
adb root; adb remount
Click to expand...
Click to collapse
Hi LuK1337
Firstly thanks for the help.
adb root returns a message saying adb already has root access.
asb remount only remounts the /system partition (unless im using it incorrectly).
So far I have well and truly wiped every partition of this device excluding the /data partition which returns a message saying partition is read-only

So I have now officially proved that this is a hardware issue at least for me, look here for my findings:
http://forum.xda-developers.com/moto-g-2014/help/battery-drained-encrypted-device-pinned-t3079871/page2
Short version I've used every available software method including 'Fastboot Erase all' which has no effect.
So would anyone be able to help build a usb jig or finding a hardware way to fix this ? my device has been opened so I would be able to provide high res pictures of the motherboard to anyone who needs it, will also upload when my 10 post count has been reached

Solved: Dead battery stuck in fastboot mode unable to flash any image. Works for all.
Same thing happened to me.
Nothing to do with the hardware.
Steps to Follow:
1) Open fastboot mode in your phone.
2)Connect to your pc and open cmd in platform-tools folder.
3)Place the twrp.img file in platform tools.
4)In cmd, type : fastboot boot twrp.img (Very Important Command)
Now your phone will boot to recovery mode i.e. TWRP and the connect it to charger. It will charge slowly.
Now you can flash anything using ADB Sideload.
(If found helpful, hit the thanks button )