Database Develop

Cyanogen slow downs?

I'm using cyanogen-4.1.999 and for some reason, I'm seeing a massive speed decrease. I got 4.1.99 to run before it, but it also got slow-downs as well. None of cyanogen's roms did this before.
Example. It takes more than a few seconds for the screen to go from off, to maximum illumination (according to system setting that is).
What should I do?

I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions

ninjavampire said:
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
Click to expand...
Click to collapse
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?

Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!

Tactical Fart said:
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Click to expand...
Click to collapse
Yes I mean the sdcard when talking about second partition

ninjavampire said:
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Click to expand...
Click to collapse
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?

NOback said:
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
Click to expand...
Click to collapse
Yes in the instructions I posted above "wipe" is the same as "alt+w"

Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/dalvik-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.

supremeteam256 said:
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/[B]dalvik[/B]-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
Click to expand...
Click to collapse
fixed typo (dalvik instead of dalvick)

B-man007 said:
fixed typo (dalvik instead of dalvick)
Click to expand...
Click to collapse
Thank you. Way to keep your eye on the ball son.

This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?

Tactical Fart said:
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Click to expand...
Click to collapse
Well when you reboot the phone...android remakes those files. thats why it takes so long to boot after you do that. the phone should run smoother then.
Have you tried wiping your ext partition?

B-man007 said:
Have you tried wiping your ext partition?
Click to expand...
Click to collapse
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.

Tactical Fart said:
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Click to expand...
Click to collapse
is it in that order? because its in the wrong order then. it needs to be FAT32, EXT, Linux-Swap
you should upgrade to EXT3 as it uses journaling (its safer)
did you try booting without the sd card? (wipe and flash the update, remove the sdcard, and reboot)
is there still a problem with the speed w/o it?

No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.

Tactical Fart said:
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Click to expand...
Click to collapse
im starting to get these problems too. Cyan is going to release anotherr rom (probably today) that aims to fix some of the major errors with the rom according to his twitter. I guess we should just wait and see if it makes it better

cyanogen 4.1.99 and 4.1.999 slow down cure
I upgraded two g1’s to 4.1.99 and then to 4.1.999. First they were slow. I had to upgrade my ext2 partition to ext3. I did this from cyanogen recovery console, 4.1 If you already have 4.1 console installed, Go to console, enter/return, on the keyboard and typed the command, upgrade_fs next to the # and then pressed enter.
If you do not have recovery console 4.1 installed. Use this link below, in the instructions for installing it from the terminal emulator make sure you type, su then press the return/enter then type in the flash command per the instruction.
http://www.cyanogenmod.com/downloads/recovery-image
Then you must be in the 4.1 recovery console, you access by holding down the power and home buttons while rebooting, got to alt-x, Go to console)
in console press enter/return
type the command upgrade_fs then press enter/return then type reboot and press enter/return.
I then downlaoded everything I needed and put them on my sd card and installed following these instructions.
http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Worked like a charm and runs fast and stable. Hope this helps.

Clockwork Recovery?

Hi,
I was curious if there is any way to replace the recovery with CWR (or something similar)? I would like to tinker, but i always feel better about having a backup in case something goes wrong.
Thanks,
Rich

while it is quite impressive that we have things such as angry birds and launcherpro, we dont seem to even have a system dump. i would think that a system dump would be required in order to better understand the rest of the system, including the nook launcher itself. then we could go after a recovery and custom roms. but i think it wont be long. like a week or two, it didnt take long to root it from initial release.

I would assume someone has noticed this, since it seems obvious, but I'll point it out just in case.
Partition 3 is an ext2 partition, which I mounted temporarily. On there are a few recovery files, including factory.zip, which appears to be a full firmware backup. What's puzzling is that factory.zip does NOT seem to be applied when I do a factory reset via Home+Vol Up, as my installed apps on /system are still there (and factory.zip has a script to format and rewrite the system partition).
So....anyone have ideas for how to trigger an update from this zip? It's not as nice as clockwork recovery, but at least we would be able to mess around and restore to factory easily.

clockworx said:
I would assume someone has noticed this, since it seems obvious, but I'll point it out just in case.
Partition 3 is an ext2 partition, which I mounted temporarily. On there are a few recovery files, including factory.zip, which appears to be a full firmware backup. What's puzzling is that factory.zip does NOT seem to be applied when I do a factory reset via Home+Vol Up, as my installed apps on /system are still there (and factory.zip has a script to format and rewrite the system partition).
So....anyone have ideas for how to trigger an update from this zip? It's not as nice as clockwork recovery, but at least we would be able to mess around and restore to factory easily.
Click to expand...
Click to collapse
try to strings the u-boot.bin that's in that partition (or in p1). The u-boot environment variables are in there. When one of the recovery modes are triggered, a file called BCB is written with a string presumably instructing recovery on what to do. It's a little hard to follow since the envs have to write the string into memory and call fatsave to save the string into the file.
Here's what I can see is happening:
-up+home recovery writes "boot-recovery recovery --wipe-data-ui"
-some condition (dead battery + charger just plugged in?) writes "boot-recovery --update-package=BOOT:charging.zip"
-too many reboots (looks like >7) without devconf/BootCnt being written with 0 (don't know where this happens) writes "boot-recovery recovery --update_package=MISC:factory.zip"
If you were daring you could probably mount partition 2 and echo 8>devconf/BootCnt and I'd imagine it would force a complete factory.zip install.
edit: BootCnt seems to be binary valued, though ASCII '8' should still trigger it.
-if devconf/DeviceID doesn't exist (this is a copy of the serial number file) then it writes "boot-recovery recovery --update-package=BOOT:romrestore.zip". No ideas about this one.
-finally, if a plain FAT microSD is found with the file "encore_update.zip" then it writes "boot-recovery recovery --update_package=SDCARD:encore_update.zip". Guess how we'll get non-OTA upgrades?

Haha, I was just searching for the string .zip in the recovery binary. I found that, and googled "encore_binary.zip", and here I am again, full circle.
I'm guessing encore_binary.zip only gets flashed from VolUp+Home recovery, right?
I copied factory.zip to my SD and renamed it encore_binary.zip, just to try...Couldn't get it to activate, unfortunately.

clockworx said:
Haha, I was just searching for the string .zip in the recovery binary. I found that, and googled "encore_binary.zip", and here I am again, full circle.
I'm guessing encore_binary.zip only gets flashed from VolUp+Home recovery, right?
I copied factory.zip to my SD and renamed it encore_binary.zip, just to try...Couldn't get it to activate, unfortunately.
Click to expand...
Click to collapse
I've got one better for you:
I tried what I recommended about /rom/devconf/BootCnt and got the "Installing..." screen. Then a boot loop running through the installer over and over.
Then I broke in by putting a Nooter card in the slot. It seems that u-boot uses itest.l to test the boot count, where .l is for long and we wrote just one byte leaving whatever was in the remaining 3 bytes of ram to stick around. Why it bootloops I don't know. So in Nooter I mounted /dev/mmcblk1p2 /mnt then "echo -n -e "\000\000\000\000" > /mnt/devconf/BootCnt", removed the card, and rebooted. No more boot loop!
Then for the lulz: On my PC I did "echo -n -e "\008\000\000\000 > /tmp/foo" and "adb push /tmp/foo /rom/devconf/BootCnt; adb reboot". This (writing a (long)8 ) forced the reboot into recovery and then booted normally when done. After doing this, I noticed that adb is enabled (/data left alone), my user partition untouched, but my root is gone (ramdisk overwritten) and /system was wiped.
So if you wanted to remove all traces of your rooting, use the above to force recovery, then use up+home to force factory reset. The next question (which I'm too much of a wuss to explore) is if the recovery or factory reset will rebuild trashed /system or /data filesystems.

pokey9000 said:
I've got one better for you:
I tried what I recommended about /rom/devconf/BootCnt and got the "Installing..." screen. Then a boot loop running through the installer over and over.
Then I broke in by putting a Nooter card in the slot. It seems that u-boot uses itest.l to test the boot count, where .l is for long and we wrote just one byte leaving whatever was in the remaining 3 bytes of ram to stick around. Why it bootloops I don't know. So in Nooter I mounted /dev/mmcblk1p2 /mnt then "echo -n -e "\000\000\000\000" > /mnt/devconf/BootCnt", removed the card, and rebooted. No more boot loop!
Then for the lulz: On my PC I did "echo -n -e "\008\000\000\000 > /tmp/foo" and "adb push /tmp/foo /rom/devconf/BootCnt; adb reboot". This (writing a (long)8 ) forced the reboot into recovery and then booted normally when done. After doing this, I noticed that adb is enabled (/data left alone), my user partition untouched, but my root is gone (ramdisk overwritten) and /system was wiped.
So if you wanted to remove all traces of your rooting, use the above to force recovery, then use up+home to force factory reset. The next question (which I'm too much of a wuss to explore) is if the recovery or factory reset will rebuild trashed /system or /data filesystems.
Click to expand...
Click to collapse
Actually, factory.zip touches data, but all it does is kill packages.xml and wipe the dalvike cache.
Also, the factory.zip script will reformat mmcblk0p5, so it fixes it in that sense, but I doubt it could recover if you started killing partition layouts and stuff like that.

I was just looking through the updater-script in factory.zip and I noticed this:
Code:
mount("vfat", "/dev/block/mmcblk0p1", "/boot");
I just thought it was interesting that mmcblk0p1 is type vfat.

staulkor said:
I was just looking through the updater-script in factory.zip and I noticed this:
Code:
mount("vfat", "/dev/block/mmcblk0p1", "/boot");
I just thought it was interesting that mmcblk0p1 is type vfat.
Click to expand...
Click to collapse
It has to be, otherwise the OMAP won't find the bootloader.

clockworx said:
Actually, factory.zip touches data, but all it does is kill packages.xml and wipe the dalvike cache.
Also, the factory.zip script will reformat mmcblk0p5, so it fixes it in that sense, but I doubt it could recover if you started killing partition layouts and stuff like that.
Click to expand...
Click to collapse
I've been messing around with the monster root pack, and can confirm that doing a "Erase and Deregister" doesn't clean out the system; I was still at least half-rooted and nearly unusable. I wiped the transient partitions from CWR and then the eight-boots reset got me back to (what I think is) stock.
I re-applied the monster pack and am having stability issues, but that's another thread, somewhere, I hope...
Dennis

stolenmoment said:
I've been messing around with the monster root pack, and can confirm that doing a "Erase and Deregister" doesn't clean out the system; I was still at least half-rooted and nearly unusable. I wiped the transient partitions from CWR and then the eight-boots reset got me back to (what I think is) stock.
I re-applied the monster pack and am having stability issues, but that's another thread, somewhere, I hope...
Dennis
Click to expand...
Click to collapse
The only thing that actually fully restored a rooted (via auto-nooter) NC to stock for me besides using clockwork recovery to overwrite the sys, data and boot partitions is the 3 finger salute - power on while holding down N and Vol+. I manually erased the internal memory just in case auto-nooter put junk on there as well.
Stability issues here too. Can't decide whether to go back to stock, cm7 emmc or stock and sd cm7.

I messed up and cannot revert to stock

Ok, so I have read through all of the posts I can and still cannot revert to stock.
I was playing with some different APKs and accidentally rewrote the AccountandSyncSetting apk with one from another device. At that point my NC rebooted and went into a boot loop. I eventually was able to get to recovery to restore factory settings, but after that completed it continued to boot loop. I have installed Nookie Froyo on an SD card which boots, however I get an SD card error, you may have to reformat. (nookie froyo is still usable, just no SDCard to mount) I have the stock files that I need to fix the device, however I cannot figure out how to do it from Nookie Froyo. Will someone please walk me through this.
thank you
I did this and I am still in a boot loop... please help
http://forum.xda-developers.com/showthread.php?p=10599116#post10599116

There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App

samuelhalff said:
There are two different resets. Power+n (hold around 30 secs to boot) (data) and 8 failed boots (system). Do those two and your set.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do I get it to 8 failed boots... just turn it off each time it starts looping?

Yes. Once the Nook tries to boot up unsuccessfully 8 times, It reinstalls the factory settings during the 9th time.

Solution:
All that you need to do is create a bootable clockwork mod sd card:
http://forum.xda-developers.com/showthread.php?t=922870
Then download the system and boot images from here:
http://forum.xda-developers.com/showthread.php?t=919353
Install ADB:
http://forum.xda-developers.com/showthread.php?t=910008
- ADB is a command line interface to your Nook.
Mount your Partitions (except sd) using ClockWork Mod (easy to find in the Nook ClockWork menu)
Get that system.img/boot.img file to your internal partitions:
Open your comand prompt. Browse to the folder with adb.exe using the cd command. (If you're on Vista or Higher you can shift+right click on the adb folder's background to get the option "open command window here".)
Type adb push "path to system.img file" / (eg.adb push "C:\Users\Name\Desktop\system.img" /). The last slash tells adb where to push your system img to. Also, this takes a few minutes 5-10.
Type adb shell, or adb.exe shell if the first doesn't work.
You'll just get a # symbol after that.
Type dd if=system.img of=/dev/block/mmcblk0p5 (dd - writes image to a location, if=input file, of=output file.
You can do the same with the boot.img just make the of=/dev/mmcblk0p1 for your dd command.
Also go ahead and format all of the partitions (except for sd anything) using clockwork mod before you use dd to write your img files to your partitons.
I think that should work to restore your system partiton.
If you have trouble getting it to boot, what works for me is holding all of the buttons for 10 seconds...3 times. And that usually makes it boot off of the microSD. That's probably the same as n+power, but idk.

dfellars77 said:
How do I get it to 8 failed boots... just turn it off each time it starts looping?
Click to expand...
Click to collapse
Actually, if you wait for the looping logo to start, you've waited too long. you want to hit the power button, then hold it down to start the restart as soon as you see the "n" logo to power it off. it will only trigger the auto reset after eight consecutive reboots that dont make it past that first "n" logo.
You could also do the reflash methods mentioned in this thread or in the dev threads, if you're up for something more intense. just be sure to take out the SD card when you're done flashing, or else you will boot back into whatever recovery you are using.

Thanks everyone. CWM is up and running and once I have a solid charge I will take another go at it. I have been having a heck of a time getting ADB to work properly on my machine (although it works fine on my Galaxy S). I think I just need to uninstall the Mass Storage Driver each time I connect and manually install the NOOK ADB driver. I will try some of the Dev tools recommended above and report back.
Thank you for the help (and at the very least nookie froyo works and has a better linpack score than my rooted stock!)

SUCCESS!!!! I can finally close all of the tabs I have open. In the end I had to run the dd commands through ADB while Nookie Froyo was running, but it all seems to have worked!
Thank you for all of the help.

[Q] help!cant unroot/restore

I tried to flash my nc with clockwork to speed it up, somehow i failed and nook color rebooted to original but with market app and superuser still installed. Google sing in fails and when i try to reset it doing the 8 step reset it boots up into clockwork recovery, what can i do?! i want to unroot and reroot and have my nc working again. Any help is gladly appreciated i have been trying everything for the past 2 days with no success
Thanks in advance

Sounds like you selected 'Clear Cache AND DATA' when you installed your ROM.
Bad move, now all data was deleted. Hopefully you made a backup before you did that.
You can get into CWM directly by pressing Power and N simultaneously, wait for screen flash, hold 2 seconds, then release.

http://forum.xda-developers.com/showthread.php?t=914690

Here is my experience with bringing Nook back to stock.
Here is the steps that I took:
1.Not really sure about this one,you but I flashed this file in CWM "just in case"- "repartition-boot-with-stock.zip (10.49 MB)"
http://forum.xda-developers.com/showthread.php?t=929670&page=6
post at the bottom of the page.
2.Download and burn Nookie Froyo 0.5.9 Image.I used class 4 4GB card to burn
"Image that will fit any card larger than 1 GB" image from this thread:
http://forum.xda-developers.com/showthread.php?t=922324
Follow the instructions.This part is important-after you burned and booted Nook:
"Wait a minute or two then unlock, relock, then unlock (gets rid of lag)
Goto to App Drawer>DevTools>Terminal Emulator
su
Allow Superuser Request
You might have to leave Terminal Emulator and go back in because keyboard disappears
Run these commands, note that your prompt has changed to #
/data/data/makepart/makepart.sh
Hit <enter> to reboot
After it reboots, go back into Terminal Emulator
su
/data/data/makepart/formatpart.sh
Hit <enter> to reboot again.
At this point, your last partition should take up any available space on your card."
This is the partition where you need to put "boot"and"system" .img files.
3.Go to this thread:
http://forum.xda-developers.com/showthread.php?t=919353
to get "boot" and "system" .img files.
Follow the instruction-read the whole thread(its small).
In my case I had to use Ubuntu to transfer "boot" and "system" .img files to sdcard patrition of my SD card(it says "filesystem 2.7GB" or something like this in Ubuntu,depending on your sd card size.)
Hope this helps.

followed forsaken82 thread and unrooted successfully,THAnK YOU, and thanks to everyone else for their input, i love you guys, now to upgrade and root once again

Bootloop after CM install. Won't restore backup, mount /data, flash stock

Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...

I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse