[RECOVERY][ALPHA]Clockworkmod 6.0.0.0 Touchscreen version - T-Mobile myTouch 4G Slide

Clockworkmod 6.0.0.0 Alpha Full touch recovery for the myTouch 4G Slide
As of right now, I don't recommend using this recovery until issues are resolved
How to install using terminal emulator (DD)
1. Download image to your sdcard then
2. Also download and open terminal emulator from the Play then type:
Code:
su
dd if=/sdcard/CWM_recovery_6000.img of=/dev/block/mmcblk0p21
reboot recovery
How to install using adb
1. Download
2. Setup ADB and Fastboot
Code:
adb reboot bootloader
fastboot flash recovery CWM_recovery_6000.img
fastboot reboot
How to install using terminal emulator (Flash_Image)
1. Download image to your sdcard then
2. Also download and open terminal emulator from the Play then type:
Code:
su
flash_image recovery /sdcard/CWM_recovery_6000.img
reboot recovery
Features:
Latest fixes from upstream CM
Power off charging
Full Trackpad support (left and right is disabled because it isn't used)
Openrecovery support (pretty sure)
UI changes
Four times smaller backups
Touch screen GUI
New CWM changes
slick blue theme with some Gnexus bootloader overlay themes
better logging\error detection
I will hopefully soon be able to put it in rom manager
USB Storage doesn't seem to be working. However it should be an easy fix as I had the same problem in 5.5.0.4 before I fixed it
This version of CWM is in alpha so there will most likely be some UI bugs
Thanks:
Kornyone
Koush and Cm team

Holy Crap AGAIN
MAN! You are one BUSY dude XMC! I can't begin to tell you how MUCH everything you do for this community and the MT4Gs is appreciated. I've gotten to feel like a kid at Christmas every time I open up these threads in the past couple of months. That goes for EVERYONE else that is involved.............except James.

WeekendsR2Short said:
MAN! You are one BUSY dude XMC! I can't begin to tell you how MUCH everything you do for this community and the MT4Gs is appreciated. I've gotten to feel like a kid at Christmas every time I open up these threads in the past couple of months. That goes for EVERYONE else that is involved.............except James.
Click to expand...
Click to collapse
Oh come on now james is part of the team too jk lol..
Good stuff xmc when my interview is over i now have an excuse to reflash. ( recovering flashaholic lol )
Oh yeah perms are good on my mint setup too thanks for that help xmc
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

Thanks for all your hard work you make this device fun to have.
I hate being a newb but i got to ask i keep getting a flash_image not found
I am trying to install recovery image with terminal
I am rooted(su works and is updated to latest version)
Downloaded image seems to be good
When i open terminal i do get $ export path= data local bin :$path
I dont recall if this is right, i dont think i remember seeing this before
Any help would be great thanks
Sent from my cm_tenderloin using xda premium

Small input: You cant select with trackpad and with key test trackpad left and trackpad right doesn't work.

used adb method and it worked flawlessly thanks XMC!!!!!

kkeller416 said:
I hate being a newb but i got to ask i keep getting a flash_image not found
I am trying to install recovery image with terminal
I am rooted(su works and is updated to latest version)
Downloaded image seems to be good
When i open terminal i do get $ export path= data local bin :$path
I dont recall if this is right, i dont think i remember seeing this before
Any help would be great thanks
Click to expand...
Click to collapse
Make sure you have busybox installed, if not, grab the installer from the Play store and run it and install it. Other than that, make sure you're doing an _ in flash_image and not a -. I'm on AOKP and it worked fine from the terminal using flash_image.

Thanks for your reply
I was using the commands for terminal emulator (flash image)
When i used the commands for terminal emulator(dd)
It worked fine
Sorry for the confusion
Whats the difference for the two anyways?
Sent from my cm_tenderloin using xda premium

CWM Touch on the Doubleshot is FAR superior to the one for the Vision.

Paitor said:
Small input: You cant select with trackpad and with key test trackpad left and trackpad right doesn't work.
Click to expand...
Click to collapse
Left and right on the trackpad isn't implemented because none of the UI options require moving left or right. But I'll look into why you cant select

Wow you have been busy. I'm psyched we have this now! I loved 4ext touch on glacier, going back to CWM was quite an adjustment. The touch feature is just a novelty obviously but it's a pretty sweet one. I see the backup sizes will be smaller, this is going to help a lot of people. It would be a life saver for me if I didn't just switch to a 32gb sd card literally last night lol. Thanks again!
Sent from my myTouch_4G_Slide using xda app-developers app

aawillma said:
Wow you have been busy. I'm psyched we have this now! I loved 4ext touch on glacier, going back to CWM was quite an adjustment. The touch feature is just a novelty obviously but it's a pretty sweet one. I see the backup sizes will be smaller, this is going to help a lot of people. It would be a life saver for me if I didn't just switch to a 32gb sd card literally last night lol. Thanks again!
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
First run: Did not succeed. Message as follows:
*Error while formatting /data!
*E:Error in /cache/recovery/log
*(I/O error)
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
(I'm rerunning the 'nand & restore now to check behind myself).
MAJOR ISSUES: Did not succeed. Message as follows:
*CWM-based recovery v5.5.0.4
*Checking MD5 sums.....
*Erasing boot before restore.......
*Restoring system......
*Restoring data.....
*Can't open /cache/recovery/log
*Can't open /cache/recovery/log
*Can't open /cache/recovery/last_log
*Can't open /cache/recovery/last_log
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
At present this is where I am stuck and can go no further that I can see. I reran the 32mb restore with the same results. Assuming that the nand was just bad, I tried to restore my 5.5.0.4. built nand with 6.0.0.0. SAME results. I reflashed 5.5.0.4 and tried another restore from my last good one and received the error message listed above. Am I reading this right that partition 31 has been left open for writing before CWM exited? Am I screwed?
HELP?

WeekendsR2Short said:
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
Click to expand...
Click to collapse
Epicness.
Sent from my MIUI V4

Worked like a charm via ADB. The new touch features are pretty sweet. Thanks!

I have some real issues here. See previous post above.....

WeekendsR2Short said:
I have some real issues here. See previous post on page 2.....
Click to expand...
Click to collapse
Uh oh... can you boot?

aawillma said:
Uh oh... can you boot?
Click to expand...
Click to collapse
I can't even get out of CWM. Well...I can but since the boot.img was erased before my restore it just hangs at the boot animation. Battery pull, then back to square 1.

this works flawlessly, you should really send this in too rom manager ASAP.

WeekendsR2Short said:
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
First run: Did not succeed. Message as follows:
*Error while formatting /data!
*E:Error in /cache/recovery/log
*(I/O error)
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
(I'm rerunning the 'nand & restore now to check behind myself).
MAJOR ISSUES: Did not succeed. Message as follows:
*CWM-based recovery v5.5.0.4
*Checking MD5 sums.....
*Erasing boot before restore.......
*Restoring system......
*Restoring data.....
*Can't open /cache/recovery/log
*Can't open /cache/recovery/log
*Can't open /cache/recovery/last_log
*Can't open /cache/recovery/last_log
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
At present this is where I am stuck and can go no further that I can see. I reran the 32mb restore with the same results. Assuming that the nand was just bad, I tried to restore my 5.5.0.4. built nand with 6.0.0.0. SAME results. I reflashed 5.5.0.4 and tried another restore from my last good one and received the error message listed above. Am I reading this right that partition 31 has been left open for writing before CWM exited? Am I screwed?
HELP?
Click to expand...
Click to collapse
try wiping data just by it self. If so just try flashing a rom not restoring

WeekendsR2Short said:
I can't even get out of CWM. Well...I can but since the boot.img was erased before my restore it just hangs at the boot animation. Battery pull, then back to square 1.
Click to expand...
Click to collapse
Can you ADB flash your boot.img? Or advanced restore just your boot partition?

Related

[Guide] *NOOB's* guide to flashing FROYO <> With the GB release

I am putting this up for new users of the Samsung Galaxy S 4g that are having issues with flashing, well, pretty much any rom right now.
1) The main issue right now is our recovery and rom manager not working together....NOT THE ROM's!
2) Here is a walk through for problem free flashing (I have officially flashed every rom posted here right now and have no issues whatsoever)
So here we go:
1) I'll start this assuming you have already rooted.
2) Download the update.zip and recovery from HERE
3) Place files on the root of your sdcard (not in any file) DO NOT UNZIP THE UPDATE.ZIP!!!
4) You must have a file system explorer with root permissions (IE...Root Explorer or equivalent)
5) Once in Root Explorer, your system MUST BE MOUNTED AS R/W, navigate to your sdcard, find the recovery file you downloaded and long press....select "copy"
6) Hit the back button until you return to the file marked "/" and make sure it is still mounted r/w, then navigate to system, then bin. Once you are in bin (this is important) hit "paste" on the bottom of your screen. It will ask if you want to overwrite the existing recovery. Select yes. DO NOT REPLACE IT, ONLY OVERWRITE IT!!!
7) Keep hitting the back button on your phone until you exit out of root explorer.
8) Power off your phone, then, after fully shut down, holding volume up AND down plus power (yes, hold all 3 of them) you will enter a blue stock recovery screen. Scroll down 1 option to "reinstall packages", press power........you should now be in the orange Clockwork Mod recovery.
9) Scroll down to "backup and restore" and hit power, then go to "Backup" and hit power. Let it do it's thing. This will create a backup on your sdcard in a file called "clockwork". Keep this so you can restore in case something goes wrong (or like me, like to change things up all the time).
10) Now, again, I will assume that you have the rom of your choice on the root of your sdcard. This is where things get screwy....so pay attention to the OP's instructions for mounts. Scroll to "mounts and storage" and hit power.
11) The first 4 things you will see are : /cache, /data, /sdcard, and /system. This is where you need to pay close attention to what you are doing.
A) For KD1 and Bionix Frost your mounts must appear like this:
/cache : unmount
/data : mount
/sdcard : mount
/system : unmount
B) For Trigger your mounts must appear like this:
/cache : unmount
/data : unmount
/sdcard : mount
/system : unmount
If they are not in this order,change them so they are, or it will flash but will not boot. YOU WILL BE IN A SOFT BRICK STATE THAT REQUIRES ODIN TO FIX!!!!
12) Install RomManager if you wish, but DO NOT, I REPEAT DO NOT FLASH CLOCKWORKMOD RECOVERY FROM THE LIST, this will cause your phone to get stuck at wiping a file called /.android_ secure in recovery.....so once again, HELLO ODIN! Also DO NOT REBOOT RECOVERY from rom manager, this will also cause /.android_secure to not wipe.....so once again, HELLO ODIN!
Last but not least, follow instructions on the OP to the "T" and you will be fine, unless you enjoy odin that much.....personally, I hate it.
If anything here is wrong or not working for you, please let me know so I can fix/update this. Please double/triple check everything that you did and make sure it is correct before *****ing "It's still not working".......because it does work. I have flashed and flashed and flashed with only 1 soft brick, and that was my fault.....not these instructions fault.
To see if I can make this make a little more sense now, here we go: The reason for changing mounts is that, by default, /system is not mounted. To be able to flash and boot successfully, it has to be. When you are looking at them, it will say "mount", this means that it is NOT mounted. If it says "unmount", then it means it IS mounted, confused yet? Just remember it like this: It is the opposite of what it says...so make sure that system says "unmount", which actually means it's mounted. This step is absolutely CRUCIAL.
Enjoy the hell out of your bad ass Samsung Galaxy S 4g, because I am
This should definitely make the sgs4g bible. Its a great tutorial on getting through the flashing issues people are having. Thank you this is ( . ) ( . )
Sent from my SGH-T959V using XDA Premium App
mad_fitter said:
I am putting this up for new users of the Samsung Galaxy S 4g that are having issues with flashing, well, pretty much any rom right now.
1) The main issue right now is our recovery and rom manager not working together....NOT THE ROM's!
2) Here is a walk through for problem free flashing (I have officially flashed every rom posted here right now and have no issues whatsoever)
So here we go:
1) I'll start this assuming you have already rooted.
2) Download the update.zip and recovery from HERE
3) Place files on the root of your sdcard (not in any file) DO NOT UNZIP THE UPDATE.ZIP!!!
4) You must have a file system explorer with root permissions (IE...Root Explorer or equivalent)
5) Once in Root Explorer, your system MUST BE MOUNTED AS R/W, navigate to your sdcard, find the recovery file you downloaded and long press....select "copy"
6) Hit the back button until you return to the file marked "/" and make sure it is still mounted r/w, then navigate to system, then bin. Once you are in bin (this is important) hit "paste" on the bottom of your screen. It will ask if you want to overwrite the existing recovery. Select yes. DO NOT REPLACE IT, ONLY OVERWRITE IT!!!
7) Keep hitting the back button on your phone until you exit out of root explorer.
8) Power off your phone, then, after fully shut down, holding volume up AND down plus power (yes, hold all 3 of them) you will enter a blue stock recovery screen. Scroll down 1 option to "reinstall packages", press power........you should now be in the orange Clockwork Mod recovery.
9) Scroll down to "backup and restore" and hit power, then go to "Backup" and hit power. Let it do it's thing. This will create a backup on your sdcard in a file called "clockwork". Keep this so you can restore in case something goes wrong (or like me, like to change things up all the time).
10) Now, again, I will assume that you have the rom of your choice on the root of your sdcard. This is where things get screwy....so pay attention to the OP's instructions for mounts. Scroll to "mounts and storage" and hit power.
11) The first 4 things you will see are : /cache, /data, /sdcard, and /system. This is where you need to pay close attention to what you are doing.
A) For KD1 and Bionix Frost your mounts must appear like this:
/cache : unmount
/data : mount
/sdcard : mount
/system : unmount
B) For Trigger your mounts must appear like this:
/cache : unmount
/data : unmount
/sdcard : mount
/system : unmount
If they are not in this order,change them so they are, or it will flash but will not boot. YOU WILL BE IN A SOFT BRICK STATE THAT REQUIRES ODIN TO FIX!!!!
12) Install RomManager if you wish, but DO NOT, I REPEAT DO NOT FLASH CLOCKWORKMOD RECOVERY FROM THE LIST, this will cause your phone to get stuck at wiping a file called /.android_ secure in recovery.....so once again, HELLO ODIN! Also DO NOT REBOOT RECOVERY from cwm, this will also cause /.android_secure to not wipe.....so once again, HELLO ODIN!
Last but not least, follow instructions on the OP to the "T" and you will be fine, unless you enjoy odin that much.....personally, I hate it.
If anything here is wrong or not working for you, please let me know so I can fix/update this. Please double/triple check everything that you did and make sure it is correct before *****ing "It still not working".......because it does work. I have flashed and flashed and flashed with only 1 soft brick, and that was my fault.....not these instructions fault.
Enjoy the hell out of your bad ass Samsung Galaxy S 4g, because I am
Click to expand...
Click to collapse
HAHAHAHA man good job on sending me that personal message i was in the process of typing everything!!! wonderful guide! keep up the good work!!
dsexton702 said:
HAHAHAHA man good job on sending me that personal message i was in the process of typing everything!!! wonderful guide! keep up the good work!!
Click to expand...
Click to collapse
Thanks brudda I wanted to hurry up and get ahold of you before you wasted all of your time and talent
@Mr. Clown , Any chance this could get a sticky in general until these issues disappear? I only ask so that the development threads can stop getting CLOGGED with "I can't get it to flash" and "I can't get it to boot" or "I still can't get into recovery" (making your life easier )
Great post!..quick question as for the rom..I heard that the mounts should look diffirent before and after flash..so after flash how should i order them?
Sent from my SGH-T959V using XDA App
johndrdragon said:
Great post!..quick question as for the rom..I heard that the mounts should look diffirent before and after flash..so after flash how should i order them?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Don't be concerned with how they look afterwards. I never have. Just make sure that when you flash they are set up properly
Thanks..one more question im currently running odex kd1 meaning original tmobile stock because i was actually waiting for roms...should I flash straight to bionix or trigger or go to kd1 first then flash those 2? because I"m concerned odex might mess it up
Sent from my SGH-T959V using XDA App
johndrdragon said:
Thanks..one more question im currently running odex kd1 meaning original tmobile stock because i was actually waiting for roms...should I flash straight to bionix or trigger or go to kd1 first then flash those 2? because I"m concerned odex might mess it up
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
mad_fitter said:
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
Click to expand...
Click to collapse
Don't forget his thanks button for this everyone
Sent from my SGH-T959V using XDA Premium App
dsexton702 said:
Don't forget his thanks button for this everyone
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
+1 brutha! Thank you
mad_fitter said:
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
Click to expand...
Click to collapse
thanks a million,just flashed it!
Nice post, yo.
Sent from my SGH-T959V using XDA Premium App
johndrdragon said:
thanks a million,just flashed it!
Click to expand...
Click to collapse
I like to hear thanks
But, ummmm, ya >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>thanks button lol.
robbbbit said:
Nice post, yo.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Shanks dude
Great job! I just came from the HD2 and was wondering if any of these roms helps the ****ty battery life?
They are all better than stock for sure. Also if you use the battery recalibration trick.....its much better.
sent from the pits of hell (from an sgs4g)
yes im a noob and yes i approve of these directions lol ya followed to the letter got clock work installed and bali installed ty
I got a question. I have this problem since I screwed up flashing the first Trigger, and then, with a brain fart, odining with the Vibrant .pit file. I got it fixed but now it will not let me change the /cache mount. I am running Trigger .4 with no problems but just curious why I can't change that mount. When I go into root explorer the only file in there is "lost&found"????
Let me do some research on that one, lol.
sent from the pits of hell (from an sgs4g)
Nevermind, figured it out.

Help: EFS Not Mounting After Flash

I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App
Ugh...an unfortunate response. Yes...I'm on the right forum.
I did make a CWM backup from a couple weeks ago. Not sure if that helps.
mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App
*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT
Additional Note: Settings are not saved between reboots.
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App
I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064
That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT
If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.
Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT
I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!
I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App

[RECOVERY]CWM-Based Recovery 5.0.2.8 For P999(Internal & External SD)

The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..
Seems the Chinese are on to this files too..lolz..
Thank you!! It flashed perfectly, no issues here.
Troy.
thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??
So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy
thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance
Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.
Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.
MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)
Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk
Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk
Works as advertised! Thanks!
works great! thanks!
So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]

[HOW-TO] Fix soft brick & error mounting sdcard

EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
Got it after several tries
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2

[SOLVED] CWM + Cyanogenmod 10 installation help - Did I forgot anything ?

Hey XDA ! =D
I'm still interested in installing Cyanogenmod 10 on my LG Optimus One P500h, but I want to make sure I follow the steps properly first - this is my first time installing a custom ROM, and when I heard it was possible to install Android 4.0 on the P500h, I performed a backup from ROM Manager, and I "bricked" my device a few days ago. XD
I wouldn't want this to happen again, but at least, I must say I have more experience now, and learned a lesson.
Did many searches on how to install CWM with Cyanogenmod 10, I found many different ways to do it, and I'm still unsure of which procedure follow.
Read the FAQ and that was really helpful.
I will list the procedure that I would normally try - please correct me if I forget anything:
0. Root the device
Done that already. I'm on Android 2.3. When I flashed the KDZ on my LG (and so to my surprise, got me updated from 2.2 to 2.3.3) , I've used V20A_00.KDZ, so I *assume* this is the second baseband.
1. Compact/Trim Cyanogenmod ROM
Downloaded CM10 here. This look correct: http://forum.xda-developers.com/showthread.php?t=1811325
January 8: Build 7/Final
I chose C10 over C11 because more things are compatible I believe - was it Bluetooth that did not worked under C11, but does on C10 ?
Anyways, that solve a known problem: many users said they loose network after the ROM installation. Shinobisoft confirmed it was because of the lack of space on the System partition, right ? Compacting the ROM would also fix problems for installing Link2SD ?
I've downloaded the tool "OOne ROM Editor" and opened it - it doesn't look complicated at all. What apps are safe to delete ? Will converting them to "user app" save space for system apps (I'm not sure - Where are the apps stored when defined as "User"? SD card rather than /System ?) ? Can I delete fonts without problems (I don't see why I can't keep ONLY 3-4 fonts, not 10) ? Then how much space will be left on the device ?
Read I cannot delete LatinIME.apk. Is this the default keyboard? 20MB is huge, there's no way to compact this file, right ?
Assuming there's like 10MB free, network will work, but I will have no choice but to use Link2SD to install apps fully on SD card, is this correct ?
2. Baseband stuff
Ehm, what are we referring to as "baseband" in first place?
All ROMs starting with CM7 are new baseband. If your device had Android 2.2 prior to flashing, you are on old-baseband. There is a patch for that also in the LG Optimus One FAQ on the first page, not sure which post off the top of my head tho. If your device had Android 2.3 on it then you have a new baseband device which shouldn't require any patches.
Click to expand...
Click to collapse
Allright, this should make this a lot easier - as I said, I originally was on Android 2.2, when I bricked the phone, I flashed "V20A_00" throught KDZ Updated, then I rebooted as 2.3.3, so I shouldn't do anything, right ?
In "About Phone", it's listed "Software Version: LG-P500h-v20a".
3. Install ClockworkMod Recovery
This look like the tricky part.
A lot of people on other sites said to use ROM Manager...
shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
Click to expand...
Click to collapse
ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Click to expand...
Click to collapse
Yes, ROM Manager is completely broken in this regard. It needs to download a signed ZIP and discard it and report an error when verification fails. Heck, ZIP format has even its own CRC check. What ROM Manager is doing (download whatever .IMG and flash it no matter what) is a nice WTF! Broken by design, go rewrite from scratch!
Click to expand...
Click to collapse
I don't trust the use of ROM Manager anymore on my device, and I'm not comfortable with using it again. I actually wonder: When I press VolumeUp-Home-Power, the phone perform a factory reset (Many people asked already why. This apparently mean that CWM is not installed).
But is it really installed? ROM Manager actually says: "Actual Recovery: ClockworkMod Recover 5.0.2.0". What? Am I supposed to press VolumeUp-Home-Power to verify, only to do another factory reset?
So what would the non-ROM-Manager method be ? I found this one here:
http://forum.xda-developers.com/showthread.php?t=1146566
I know about the Android Terminal Emulator already, and as a Linux user on PC, the commands "su", "cat", "chmod", "mount" are not unknow to me. I should be able to do this... That's not risky ?
So when CWM will be installed, I should be able to boot in it using "VolumeUp-Home-Power"; in theory, this is a bootloader, so if the ROM get screwed up, I *should* be able to access the bootloader to restore the ROM (I compare this to a PC BIOS - the OS is screwed, but BIOS remain accesible) ?
How could I explain that when I bricked my device with ROM Manager, I couldn't perform a factory reset, and only had access to Emergency Mode (I assume there is not such thing as a "Recovery Mode" on a P500h stock, new/untouched. The equivalent immediatly perform a factory reset) ?
All Android devices have a recovery partition. This is essentially a section of the device’s memory devoted to a very basic recovery system that is separate from the normal operating system. This is normally used by manufacturers for recovering a broken device (as even if the operating system crashes, the recovery image has a chance of still being access and used to reflash the operating system, etc.).
Click to expand...
Click to collapse
By default, the LG P500h recovery partition perform an immediate factory reset - CWM will be installed here, so I should be able to access it if the ROM freak out. But why couldn't I access the factory reset, when I bricked the device? That's what I wonder.
4. Access CWM and do a Nandroid Backup to SD Card
I will now have the files boot, cache, data, recovery and system, as well as"nandroid.md5" on SD card.
5. Wipe everything, clean SD Card
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
Click to expand...
Click to collapse
6. Partition SD card (?)
Is this at that point that I should do it, in CWM ? Or wait until I access Cyanogenmod and use a software on PC to partition ?
Assuming I don't partition, I guess I definitely will lack space for applications (Due to the space of Android 4.0) ?
I will do "Partition SD Card>EXT4 1024MB>Swap:64MB. Is this correct?
7. Install Cyanogenmod
Install ZIP from SD Card, choose the CM ZIP;
8. Install Google Apps
Once the install is done, I won't reboot and immediately install Google Apps, with "Install ZIP from SD card". I chose this package (Working on JellyBean):
http://forum.xda-developers.com/showthread.php?t=1917411
Then I should reboot in CyanogenMod and finally install Link2SD, I believe.
***
..Did I forgot anything ?
I *believe* that makes sense, but this is my first time installing a ROM - I doesn't look *that* hard, I did researches, but things can go wrong... :/
What should I do if I screw things up? Use KDZ Updater again ?
I'm still a little worried about that baseband thing, and the lost network connection.
Thanks for the input, cheers!
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
GameX2 said:
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
Click to expand...
Click to collapse
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Allright, I got it!
I saw the success message, then used the keys to reboot in recovery, that worked!
At the boot, I can read "ClockworkMod Recovery v5.0.2.0 E: Bad boot message "recovery ".
I believe the "E: Bad boot message "recovery " is a known issue, and but is not a problem - please let me know if I have to do anything about this.
So now I will compact the Cyanogenmod ROM (I don't know how much space I should free, but I'll try to free a decent ammount), and perform a Nandroid backup to SD card.
I believe the hardest/scariest is done. From now, if the ROM install fail, I could just restore the backup, I guess.
Are they any case when CWM is unaccessible (When I bricked my device, I had no access to stock recovery (which only perform factory reset) but just Emergency Mode. Why was that?) ?
Thank you, I will let you know about the rest.
(Will press the thanks button at the end I don't know if it's OK to thanks on multiple posts on one thread, on this forum)
EDIT:
That error message means you dont have SD-ext. Ignore it.
Click to expand...
Click to collapse
EDIT 2: Nandroid backup succesfully taken! I now have the files .android_secure.vfat.tar, boot.img, cache.yaffs2.img, data.yaffs2.img, nandroid.md5, recovery.img and system.yaffs2.img. Will backup these on my PC.
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I appreciate the information;
It's quite akwards that ROM Manager broke everything (And I asked for a BACKUP - that's so broken, it brick the device when you want to BACKUP <__<) - when it rebooted, it was in Fastboot mode, and I never saw that mode before. Tried a few recommended commands without problems, but when I rebooted, I only had access to Emergency Mode.
What would be informative for me to know, is that ROM Manager seems to not only have screwed the ROM, but the stock bootloader as well. Weird.
Shinobisoft said we need to compact the CM10 ROM with his utility first, because the System partition is too small (Otherwise, I will have no network). I will do that, I have the tool, that doesn't look complicated.
From now, I am backing up my SD Card content (DATA is backed up too) with Nandroid present on SD, so I could start formatting, immediately followed by SD partitioning.
I guess I should be fine at that point - if anything goes wrong, I should have the option to restore the Nandroid backup.
Will let you know when I'll have the ROM compacted (Probably today).
EDIT: YAY !
Everything worked as we expected! I saved my SD Card on my computer, wiped it, partition it from CWM (EXT: 1024MB, SWAP: 64MB. I have a 16 Micro SD, class 4 (Can't afford higher class much, for now), then installed the compacted ROM. Immediately after, I installed Gapps, then rebooted.
That worked !! This ROM is DOPE ! Totally worth upgrading ! Blazing fast !! (Will be slower with apps installed, but well)
I also have a working network!
There is one thing that "failed", I cannot get Link2SD to work. It always says "cannot create mount script". I checked with Windows (I know by experience that I should absolutely not edit Unix partitions in Windows, I just check), and the FAT32 partition is the first, then I have a EXT4 partition, then the Linux-Swap, I don't know why it doesn't work.
I used Gparted to format the EXT4 partition to EXT2, but same problem, "cannot create mount script". What am I supposed to do ?
Thanks youuu !! =D
I'm really happy to have done this on my own, with help - I now have more experience with Android, I have experience with Windows, Linux OS and OS X, but never did I tried flashing a ROM yet.
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Hi,
Tanks for replying. out of 200mb, I have 70Mb free, but on /data. Last time i checked, /system was almost full (where can i check system size?).
Seems like lot of people have this link2sd issue.
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
@akiratoriyama
Yes, that's right. You can check /system space by using Root Explorer. Or go to
Settings>About phone>Partition info.
I got 10+MB space left on /system partiton after trimmed the ROM and installed mini gapps.
You're right, Link2SD only works if there is 3MB, at least, left in system partition.
Sent from my LG-P500 using xda app-developers app
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Click to expand...
Click to collapse
It worked !!
Geez, I went to 170MB of internal MB to 1GB, that's just plain insaneee !
Now I can use my LG P500h for an extra 2 years.
ibub said:
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I was confused, because sd-ext2 at root is empty - nice to find it in /data/sdext2.
Suceess !!
Thanks !!
How Do I Install?
GameX2 said:
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
Click to expand...
Click to collapse
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Drachinos said:
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Click to expand...
Click to collapse
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
I guess I was thinking too much (or not at all!) Simplicity is the key a lot of times!
I tried all of the points in this thread and now this Optimus One has root, recovery and a new ROM. Thanks everyone! :good:

Categories

Resources