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

BSG - Boot script generator

Hi to all, i made a python program that help user to install/update the system.
With this program you can stop using the android boot menu, you can put all in the script.
What you can do with Boot Script Generator:
- install system
- update system
- backup system, data (with old and new method)
- apply updates
- clean data and system
- install apps located in /sdcard/andboot/apps
UPDATE 22 / 08 / 2010
New interface
Add new backup options
Add image size options
No more press d-pad or volume up
No more install procedure
cross platform and only python is needed
you can choose where install
NAND - SD - IMAGE both for system and nand
and what you want to do before boot
Little how-to
flash modded nbh or put initrd.gz in andboot for haret users
open python script in a terminal:
Code:
python bootscriptgenerator.py
then choose what you want to do, (i.e first install)
put install-seq.sh in your sd in andboot folder (with other files)
turn on the phone.
you don't need to touch any button just wait
As you can see you can change many things.
Update initrd and nbh on 4/7/10
If you are an "haret" user use this initrd.gz
Boot Script Generator (right click on link -> save as file)
Simple how-to run android from windows - Simple guide to flash android on Nand
{
"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"
}
It could be very useful if you want to speed up your system update

Reserved

Exciting, now you just need to make a android app as well to do this, that way you can set the options and hit reboot
Good job

I'm just working on it.
i think that next dzo nbh will include this changes

Any feedback?

Strange...
I download the latest version of python (2.7).
When I select any options in your tool, and want to create the .sh, impossible to find it !! I think he's not created...
I use it in a windows PC (Windows XP pro SP3).
I try with all options and it's the same thing. Sorry for that.
I hope you can find the problem.
Cheers.
l1q1d said:
Any feedback?
Click to expand...
Click to collapse

I make a simple modification, try with updated version

Source code...
I will try but when I want to download the link in first page, I've the source code...
Could you upload your tool ?
Cheers.
l1q1d said:
I make a simple modification, try with updated version
Click to expand...
Click to collapse

Re update link (extract with win rar/7-zip or other)

Hi l1q1d,
I've download this new version but same result : no product file...
I try to find it in my PC but no file...
I don't know how to help you
Thank you for your release of your tool key mapping
I'm on holiday now : go to Spain...
Cheers.
l1q1d said:
Re update link (extract with win rar/7-zip or other)
Click to expand...
Click to collapse

Hi,
I try to install Android on a Polaris and created an install script with your bootscript creator, but it always stops with the error:
'd: invalid number '512
where 512 is the size of the data image I have set in the creator gui.
Am I doing something wrong?
Thanks in advance
Abomb

Could you please submit a screen shot of your settings and the output file? Thanks

Here they are.
I forgot to mention that I commented out the data.img remove part, because that part gives me the error that the script file did end although a "then" was expected or something like this. But seeing as I do a fresh install and have no old data.img I thought it should not be a problem.

Any other error before?
Could you please test with 256?
Thank you

I tried two things, first with 265 MB and the disk.img remove code left in, the second time with the code commented out.
The first time I got a bootlog.txt that I attached here, the second time I got the error again
'd: invalid number '256
but sadly no bootlog.txt. Oh and no error before the invalid number one.

I update a new version of bootscriptgenerator
Try now

I tried with the new version, but exactly the same thing, tried first with disk.img delete code left in, second time commented that out.
Error messages were the same, first time bootlog was created, second time not.
I also double checked if I was using the new version of the creator.

Could you please make a test with this.
Please don't edit it (it could be a windows endline problem)

With the file from your last post it works!
Did I do something wrong then?
I didn't edit the .sh file for the first try, only when that didn't work I edited it.

The problem is the windows end line.
It isn't your fault is WINDOWS :-(
i update a new version, now i need someone to test it

Root your S5 (CF-Auto Root)

Samsung Electronics Co Ltd’s (KRX:005935) new Galaxy S5 smartphone can now be rooted using the CF-Auto-Root tool, developed by Chainfire, a recognized member of the XDA Developers forum.
Rooting a device allows users to get complete access to the device’s operating system to make changes to the file systems. In order to root the Galaxy S5 running on the latest Android 4.4.2 KitKat, users are required to flash the CF-Auto-Root file in the smartphone.
Users will have to download the appropriate CF-Auto-Root package for their Galaxy S5 models. Users can check the model number by going to Settings > About phone > Model number.
Here are the download links to CF-Auto-Root packages:
Points To Remember Before Rooting
- Users are recommended to back-up all data before rooting the device
- The device should have at least 80 percent charge left on the battery
- USB drivers must be installed on the computer with USB Debugging enabled on the device to transfer files between the phone and computer
- Users should ensure they are using the correct root package for their device
{
"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"
}
Note: International Business Times cannot be held responsible for anything that goes wrong. Users should proceed at their own risk.
Tutorial
Step 1: Download CF-Auto-Root package and Odin v3.09. Then, extract the files to the computer.
Step 2: Boot the Galaxy S5 in Download mode by pressing and holding down the Volume Down, Home and Power buttons together. When a warning screen is displayed, press the Volume Up button to enter Download mode.
Step 3: Now, run Odin3 v3.09.exe as an Administrator and then connect the Galaxy S5 to the PC via USB cable. If connected successfully, a message showing “Added!!” will appear in Odin’s message box, if not, try another USB port. If the issue persists, try reinstalling the USB driver.
Step 4: Click on the AP button, and select the CF-Auto-Root file (a .tar.md5 file), which was extracted in Step 1.
Step 5: In Odin, make sure that the “Auto Reboot” and “F. Reset Time” options are checked while “repartition” is unchecked.
Step 6: Click on the Start button in Odin to begin the flashing process.
Step 7: After the process is complete, the Galaxy S5 will restart and a PASS message with green background will appear in the left-most box at the top of Odin.
Voila! you have successfully rooted your S5!

And this will also trip KNOX I supose?

Hasn't this been covered elsewhere?
Sent from my SM-G900F using Tapatalk

This method seems sooooo much more complex than towelroot and potentially more risky?

AMoosa said:
Hasn't this been covered elsewhere?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yes, in the developer's original thread, and he should be getting the thanks for it.
[SM-G900*] CF-Auto-Root

Thread closed as Chainfire already has a thread here so there is no need for one that essentially copy/pastes the information in his thread.

Erased all My partitions through QFIL. How to fix?

{
"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"
}
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?

nasedase said:
View attachment 5786719
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
View attachment 5786723
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?
Click to expand...
Click to collapse
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it

AsItLies said:
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it
Click to expand...
Click to collapse
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?

nasedase said:
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?
Click to expand...
Click to collapse
one by one. I've done it, it's time consuming, but it can be done. And be sure to pay attention so you don't flash the wrong one to the wrong partition. If you get a message about 'data overflow', immediately cancel, that means you are trying to flash to a partition too small for the image, and you'll overwrite the partition next to it, and probably end up with a brick.

Question HELP

my device is locked in fastboot after flashing gsi, i tried all but nothing, so i locked the bootloader, i know i'm dumb but i was and i am desperate, solutions? idk if there is still a rom in because it was empty and i tried the fastboot method to reflash rom like flash boot.img and vbmeta.img and others (nothing changed).

UPDATE, i unlocked the bootloader but the problem is still here, i tried to flash rom with fastboot but it fails with system and vendor, i think that's the problem.

logs? photos? how you flashed? what you flashed?

Supposing your bootloader is unlocked, just follow this guide taken from this Mi official page.
Method 2: Fastboot Update
Note
A Windows PC/laptop will be needed for the following steps. Make sure that your device is fully charged or has enough power for this process. This guide will help you update your device to the latest MIUI ROM version. All user data will be purged in this process. Please back up your data and think twice before proceeding.
STEP 1
Download MIUI ROM Flashing Tool (Size: 66.7 MB)
STEP 2
Select the right MIUI ROM version for your phone:
★ Redmi Note 11 [spes] Global
★ Redmi Note 11 NFC [spesn] Global
★ Redmi Note 11 NFC [spesn] Europe
★ Redmi Note 11 NFC [spesn] Russia
STEP 3
Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a USB cable
STEP 4
Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path on the computer.
STEP 5
Decompress the MIUI ROM flashing tool downloaded in Step 1, and double click on it to install (if there is security warning, select 'Run'). After installation is completed, open MiFlash.exe and paste into the address bar the ROM file folder path copied in the last step.
Click on the first button (circled out in yellow) to Refresh, and MiFlash should automatically recognize the device. Then click the second button (circled out in red) to flash the ROM file to the device.
{
"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"
}
STEP 6
Wait until the progress bar inside MiFlash turns fully green, which means the ROM has been successfully installed. Then your device should automatically boot to the new version.
If the flashing guide could not help you, please download Mi PC Suite here (after Mi PC Suite is installed, make sure that your phone is in fastboot mode, connect your phone to a computer, and select the correct ROM file to flash).

I finally solved, i unlocked bootloader again with mi unlock and i followed this instructions, thx