Database Info

[Q] t959v cvm message

Hi all. i have Samsung galaxy 4G. Phone not start just showing
______________________________
Galaxy S 4G\exlusively from T Mobile
SAMSUNG
______________________________
How this happend? My sister try to send or receive file in skype, and phone freeze. after that i never can load os.
i'm trying load new software using odin.. but nothing help.
After flashing i can hear Linda voice..
and after restart CVM message
Wiping data
Formating /data
E:format_volume: rfs format failed on /dev/block/stl10
Formating /cache...
E:format_volume: rfs format failed on /dev/block/stl10
Wipe data failed.
when i'm trying install firmware from SD
--Install /sdcard ...
E:Short write of /tmp/sideloadpackage.zip (No space left on device)
Instalation aborted.
how can i fix my phone?? das anybody help me?

Go to this thread:
http://forum.xda-developers.com/show....php?t=1358498
Select and download:
Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders
Let me know when you have it downloaded and I can help you proceed.

i cant open this page..
404 Page Not Found
The page you requested was not found.

http://forum.xda-developers.com/showthread.php?t=1358498
While you are waiting for the download - go ahead and do step one in that thead:
"Get the latest version of Java 1.6 from this link."
** Just so you understand - Froyo and GB have different bootloaders. If you were on Froyo and trying to flash GB without bootloaders - that is a problem. That is why - to be safe - you are downloading KJ6 WITH BOOTLOADERS so we know you will be good to go afterwards.
Make sure you refresh your browser so you can see my replies.

downloading progress 23% ....
and i really need your help
Step by step... :-( bcuz i have no idea how to fix this problem ..

nvitek said:
downloading progress 23% ....
and i realy need your help
Click to expand...
Click to collapse
Let's do it. Look at the post above yours. And take care of the Java.

nvitek said:
downloading progress 23% ....
and i really need your help
Step by step... :-( bcuz i have no idea how to fix this problem ..
Click to expand...
Click to collapse
Step by step is no problem. Using this method is fairly easy.
What is your status? I need to take my daughter to the park

can't believe, file is broken . Looks like i'm must download this file using Download manager.
23 nmin left.
Zz...
Java is up to date, battery charged.

nvitek said:
can't believe, file is broken . Looks like i'm must download this file using Download manager.
23 nmin left.
Zz...
Java is up to date, battery charged.
Click to expand...
Click to collapse
You are downloading it on your computer correct?
And downloading the link:
'Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders'
Correct?
ADD: I don't think you realize the thread is on page 2. Click the '2' at the bottom of your thread to see the next page. You also need to keep refreshing your browser to see new posts.

download Completed. Device connected
Operating System: Windows
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device not connected.
SMS-KJ6 (v0.0.2d) Stock-Rom with Bootloaders UVKJ6 is ready for your device.
Ready for flash.
After Heimdall
Android recovery <3e>
...
installing update...
Succesfully installed package.
....
-- Updating filesystem...
E:failed to mount /data <Invalid argument>
E:discard_filesystem_for_rfs:Can't mount /data
--wiping cache...
formating cashe...
E:format_volume: rfs format failed on /dev/block/stl11
Chashe wipe failed.
--Apling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'.
Successfully applied multi-CSC

nvitek said:
yeap..
url correct
54% and 12 min left
Click to expand...
Click to collapse
Since you have some time to kill -
Read these two threads start to finish:
http://forum.xda-developers.com/showthread.php?t=1529348
http://forum.xda-developers.com/showthread.php?t=1515319
These are two people that did exactly what you are about to do.
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
When you are ready to get started:
USE A USB PORT YOU HAVE NOT PLUGGED YOUR PHONE INTO AT ALL AND THAT IS CONNECTED DIRECTLY TO YOUR COMPUTER (I.E. NOT A USB HUB OR ADDON PORTS)! DO NOT USE THE SAME PORT YOU TRIED TO USE ODIN WITH. DO NOT USE A PORT YOU MIGHT HAVE USED KIES MINI WITH. USE A PORT THAT YOU HAVE NEVER PLUGGED YOUR PHONE INTO DIRECTLY ON YOUR COMPUTER!
You will do this first:
- Get your phone in Download Mode
How to get into download mode:
Take your microUSB cable and plug it into the computer, but not the phone (yet).
Take out the battery from the phone.
Put the battery back into the phone.
Put the back cover back onto the phone, make sure it's snug so the battery doesn't fall out.
Hold vol + and -, keep holding them.
Plug the USB cable into the phone.
You should now be in download mode and should see a picture of a yellow triangle with Andy and a shovel in the middle.
Second:
- Run the Heimdall One-Click you downloaded using the directions in that thread:
Run: 'java -jar SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar'
Third:
- You will need to install drivers. When doing the driver install make sure you go to "options" menu and make sure "list all devices" is checked. Then from the drop down menu choose "Samsung USB Composite device" and click the "install drivers" button and let it do its thing.
It will tell you whether it was successful or not.
Fourth:
- Heimdall should show you that your phone is connected:
See attached image.
If so - Select Flash.
Fifth:
- Your phone will reboot. You will hear Linda talk to you. Wait. Let me know if you get a rainbow screen. If not it will boot into CWM Recovery. If it does - select reboot system now and you will be good to go.
- If you see the rainbow screen - Let me know and we will proceed.

OK - I assume you are sitting on page one of the thread. I can't reply to you if you don't come to the second page. Sorry.

Thx for your help.
After all steps andflashing with Heimdall my phone rebooted to CVM recovery.
after reboot phone stop in message like in my first post.

What are you doing in CWM to get that message? And do you know if you were on Gingerbread or Froyo previously. Because if you were on Froyo you were not finished with Heimdall One-Click. You would need to flash a second time - checking flash bootloaders.

1.CWM is automatically loaded after a reboot.
2.Froyo was previously.
3."You would need to flash a second time - checking flash bootloaders." - already done.
Message appears after downloading new software with using heimdall and automatical reboot
Phone still freezes on startup.
Is it possible to connect terminal to mainboard? perhaps that will help to see diagnostic messages... and will give me a chance to understand the problem.....

nvitek said:
1.CWM is automatically loaded after a reboot.
2.Froyo was previously.
3."You would need to flash a second time - checking flash bootloaders." - already done.
Message appears after downloading new software with using heimdall and automatical reboot
Phone still freezes on startup.
Is it possible to connect terminal to mainboard? perhaps that will help to see diagnostic messages... and will give me a chance to understand the problem.....
Click to expand...
Click to collapse
If you correctly flashed KJ6 Heimdall One-Click WITH Bootloaders and that did not work -
Verify that you have a Samsung S 4G SGH - T959V for me. Look under the battery for the model number.
And to be clear - after flashing it will take a bit to boot your phone as things are being done to your phone during boot up. If you pulled battery too quickly that may affect it.
Lastly - "Message appears after downloading new software with using heimdall and automatical reboot" - Where is the message appearing? In Heimdall or on phone?

if you are still having issues, you can check the "Potential Problems" section of the guide in my signature (provided that you do indeed have the right phone model)
Sent from my SGH-T959V using xda premium

Hahahaha - This kid is so proud of himself. Aww me too Juls. Keep self-promoting every where you can. You still haven't asked dsexton to link to you in his OPs.

Juls317 said:
lumin, im just trying to help the guy out as your way isnt cuttinv. sorry for caring for the community.
and you self promote too you hypocrite.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
ok
10 chars

No need to belittle members. Lets keep things nice and clean ok? Happens again, I will not be so nice. Have fun guys.

[Fix] EMMC brick bug issue on P6200/P6210 16gb? Give this a go!!!

For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app

Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated

There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..

chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:

I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app

@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium

Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...

unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium

U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app

Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:

Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app

Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd

Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell

EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse

ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance

doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium

A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it

P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks

Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?

one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please

Solved: stuck at "Firmware upgrade encountered an issue. Please select recovery mode

Solved: stuck at "Firmware upgrade encountered an issue. Please select recovery mode
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:

JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse
Hi. Tried your method and it worked on windows. I tried 2 different ODIN softwares before it worked. Thanks for your help and information.

can't enter download mode
thanks for the notes. i tried to update to 4.2.2 from 4.1.2. the upgrade was unsucessfull. now i did whatever u have told. now i got the recovery but i can't enter download mode. now the tab 2(p3100) is just restarting. please help me as soon as possible
JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse

pls help..
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..

shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
kies is not nesccearlly needed we need the usb drivers make sure you installed them and you are using stock samsung usb cable or else IT WON"T WORK !!!

shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
If you can reach to the CWM recovery mode: Download firmware in zip form, you can get it from the below link. if you have a zip file leave it.
After obtaining the firmware copy to your external sdcard using a card reader or any other method
In recovery mode select "Instal zip from sdcard" then select "choose zip from external sdcard" then select the copied firmware zip file from the list and wait for completion
After completion go back and select "wipe data/factory reset" and "wipe cache partition" reboot . it will take some time for reboot atleat 15min. it worked for me. hope it will work for you. good luck
http://forum.xda-developers.com/showthread.php?t=2054901

Thanx...
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply

shubham.butle said:
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply
Click to expand...
Click to collapse
You can choose any of the roms, deodexed will be better. And there won't be any problem flashing 4.2.2

You should install latest kies version
Sent from my GT-P3100 using xda premium

sukkukikku said:
You should install latest kies version
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
---------- Post added at 02:05 AM ---------- Previous post was at 02:01 AM ----------
shubham.butle said:
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
Click to expand...
Click to collapse
I update rom by cwm..

would you like to give me clear solution? i have same problem here with P3100, already tried many CWM but none of them fixed it, flashing directly through odin with this file (DBT-P3100XWDMI1-20140113101559) and still no luck. Any link to download correct CWM please... Thanks

Awesome post
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:

ragujay said:
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:
Click to expand...
Click to collapse
Hi! Do you still having the CWM and Odin 1.3?

Hi.. I was experiencing this problem. Then without even thinking deeply, I try google any solution regarding this matter without referring to this thread first. I found this guys solution as he said it is for all samsung model.
https://www.youtube.com/watch?v=Jfgq6bYfKLg
After done flashing, my tab giving a samsung logo and went off until now. I was unable to enter the recovery and download mode. I try to connect the tab with PC but it kept reconnecting repetitively although universal samsung usb driver has been installed. Any idea how to solve this?

Unique ECHOE ROM Flashing-Guide accepted by the Echoe ROM TEAM

Official:
Unique ECHOE-ROM Flashing-Guide
since v5 to v37 and up, still the best guide!
Always have a NANDROID Backup before changing anything on your device!
Please make a backup of your APP´s with e.g. Titanium-Backup to restore them after flashing!
Also it is advisable to make a backup of your contacts!
Note: You might have ROOT before getting custom recovery (CWM, TWRP, PhilZ) to work!
Flash MGA based Pre-Rooted ROM from DjeMBeY or ROOT your Phone to get it!
Users with NEW Bootloader simply flash a MI8 or higher pre-rooted ROM!
You have to build your System completely new to get a 100% working ECHOE ROM!
No "dirty flash" without wipe! Make it like I describe now or leave this Guide immediately!
​
You need the following for your Galaxy S4 I9505:
Device fully charged! =D--._.-----
Samsung USB connection cable to connect phone to PC
Micro SD-Card Reader for your PC (only if you have a micro-SD Card in the phone)
Samsung USB driver for PC Click here!
Latest Philz Touch Recovery Click here!
Odin (latest) ........................ Click here!
ECHOE ROM ....................... Click here!
Modem Collection .............. Click here!
Perhaps CSC Changer App Click here!
DOWNLOAD MODE:
(for Odin operations (.tar.md5 Files))
NOTE: You might have to extract downloaded .RAR file to get the inserted .tar .md5 file!
From switched OFF phone push the power button until the S4 vibrates, IMMEDIATELY push "volume DOWN" to enter download mode.
Push volume UP when you be asked!
Connect the Phone to PC with USB connection cable!
RECOVERY MODE:
(for Recovery operations (.zip Files)):
From switched OFF phone push the power button until the S4 vibrates, IMMEDIATELY push "volume UP" to enter recovery mode.
Process:
Prepare Phone:
1: ROOT YOUR PHONE like described above (if it´s not already rooted)!
2: Flash Philz Touch Recovery with Odin (as "PDA" or new Odin as "AP") or SGS4 flasher APP!
... Look at the above line "RECOVERY MODE" in this Guide how to start!
... If Philz Recovery asks you to fix ROOT (after you choose Reboot Now) choose NO !!!
Prepare SD-Card:
If you don´t have a Micro-SD Card just copy the downloaded EchoeRom ZIP to the internal SD!
3.: Switch OFF your phone and take out the micro SD-Card
4.: Put the micro SD-Card in a card reader and delete the folder ".android_secure"
.... It might work without deleting the ".android_secure" if you come from older ECHOE ROM Version (not tested by me)
5.: Copy the downloaded EchoeRom ZIP to the micro SD-Card
6.: Put the micro SD-Card back into the phone (DONT BOOT UP THE PHONE WITH INSERTED micro SD-Card, ".android_secure" is written again)!
Cleaning Phone:
7.: To completely clean your S4 and get rid of all older remaining´s you now start into Recovery Mode
... Look at the above line "RECOVERY MODE" in this Guide how to start!
8.: In the Settings of Philz Recovery choose:
8a: Advanced: Wipe Dalvic Cache
8b: Wipe Cache Partition
8c: Wipe Data/Factory Reset / Factory Reset
8d: Wipe Data/Factory Reset / "Clean before flash new ROM"
... Note: You have to flash a new ROM after doing point 8d !!!
... Stay into the Philz Recovery and read ahead!
Flashing ECHOE ROM:
9.: Because you stay into Philz Recovery hit the option "Install ZIP" then hit "choose zip from/storage/sdcard1" or internal SD and choose the EchoeRom ZIP
10.: After the flashing process finished go back to main menu and choose "Reboot System Now"
..... If Philz Recovery asks you to fix ROOT (after you choose Reboot Now) choose NO !!!
First Start:
11.: The first time the phone boot up take about 3-4 minutes
12.: After the phone has started do furthermore NOTHING for about 5 minutes (let the system set up in calm)
13.: Switch OFF the phone with the power-button
Flashing another Modem for your Echoe ROM Version (if the included modem is not working properly):
14.: Boot device into Download-Mode from switched off device (important)!
15.: Connect Phone to PC with the Samsung USB Cable!
16.: In Odin remove the "Auto Reboot" hook
17.: In Odin click on PHONE or newer Odin click on CP, load your Modem and press START
18.: Wait 3-4 minutes till there is a message: All threads completed. (succeed 1 / failed 0)
19.: Hold Power-Button for 10 seconds till phone resets (you feel the vibration)
Ready for take off!!! :laugh:
Phuuu... that was a ride... everything clean and new now!
Enjoy this famous ECHOE ROM!
Hit the :good:THANX Button if you enjoy!
.

Great guide and should help a lot of people out! Thanks for this!!
Sent from my GT-I9505 using XDA Premium 4 mobile app

I can't find an .android_secure folder anywhere on my SD card.
Just checked and the checksum is correct:
MD5 (/Users/Hate/Downloads/Echoe Illusion Rom v6_28Oct.zip) = 0fba4efafe95457a934cb50946bf552e
Same one as listed at http://d-h.st/AX5 the download link.
Prehaps the upload is corrupt?
Can anyone provide me with an alternative link? I don't want the themed version.
I'm trying downloading it with a different browser however I really cant see chrome being any problem at all?
Please someone help, I'm stuck with an expensive brick currently Well semi-brick :'(
I'd ideally like to fix it as its my only alarm clock!
Thanks

Hmmmmmm.
Just downloaded the themed version,
Wiped everything as instucted ( noticed it said Formatting external_sd/.android_secure despite me checking many time before and its not there, not even a hidden file or folder )
Getting the exact same error Can't open... bad...Can anyone help this is driving me crazy!
All the md5 hashes match
Thanks

Hey I cant seem to get my phone to stop losing signal when the screen is off. I have flashed the modem that the firmware checker says is good for my phone but its still not working any ideas.

HollowVegitoRay said:
Hey I cant seem to get my phone to stop losing signal when the screen is off. I have flashed the modem that the firmware checker says is good for my phone but its still not working any ideas.
Click to expand...
Click to collapse
Did flashed the ROM like described above?
Did you use the inbuilt Faux Kernel?
Have you flashed the Modem like described in Point #18 ?
What is your Bootloader (old or new (with or without Knox)?
This works flawless! Many people have confirmed! :good:
This flashing method is beyond any doubt, it MUST work if you dont have made thinks wrong!

philipkroberts said:
I can't find an .android_secure folder anywhere on my SD card.
Just checked and the checksum is correct:
MD5 (/Users/Hate/Downloads/Echoe Illusion Rom v6_28Oct.zip) = 0fba4efafe95457a934cb50946bf552e
Same one as listed at http://d-h.st/AX5 the download link.
Click to expand...
Click to collapse
Never mind, this folder is written from the System itself (after first booting up).
Whats the problem with your downloaded ROM?
Prehaps the upload is corrupt?
Can anyone provide me with an alternative link? I don't want the themed version.
I'm trying downloading it with a different browser however I really cant see chrome being any problem at all?
Please someone help, I'm stuck with an expensive brick currently Well semi-brick :'(
I'd ideally like to fix it as its my only alarm clock!
Thanks
Click to expand...
Click to collapse
Flash a stock ROM with Odin first and then go ahead!
For new Bootloader you have to flash stock .tar.md5 XXUEMJ5 Firmware with ODIN.
For old Bootloader you have to fllash stock .tar.md5 XXUEMGA Firmware with ODIN.
Flash stock ROM with my Guide here: http://forum.xda-developers.com/showthread.php?p=46399517#post46399517
So you should have a starting point to continue with the ECHOE ROM Flashing guide!

fAiLOfax said:
Did flashed the ROM like described above?
Did you use the inbuilt Faux Kernel?
Have you flashed the Modem like described in Point #18 ?
What is your Bootloader (old or new (with or without Knox)?
This works flawless! Many people have confirmed! :good:
This flashing method is beyond any doubt, it MUST work if you dont have made thinks wrong!
Click to expand...
Click to collapse
I flashed like described in point 18. I don't know what bootloader I have and I'm not sure about the kernel.

HollowVegitoRay said:
I flashed like described in point 18. I don't know what bootloader I have and I'm not sure about the kernel.
Click to expand...
Click to collapse
Did you ever flashed a ROM higher than MGA or MH1 you have the NEW Bootloader!
Flash a stock ROM with Odin first and then go ahead!
For new Bootloader you have to flash stock .tar.md5 XXUEMJ5 Firmware with ODIN.
For old Bootloader you have to fllash stock .tar.md5 XXUEMGA Firmware with ODIN.
Flash it like I described in my Best ROM Flashing Guide (in my Sig)!
Then continue with this ECHOE ROM Flashing Guide!

Hi, really like your threads and just discovered this one.
I have a android.secure folder on my external sd card but am wondering, why I can't just delete that one, boot into recovery, wipe and flash the new ROM. In your steps you recommend to take out the card, put it into a card reader, delete the folder, put ROM on external sd card, put card in phone and boot into recovery. Wouldn't that be the same as if I delete it on my phone with a file Explorer and booting into recovery?
Or is this folder recreated while shutting the phone down?
Also, could you explain a bit why this particular folder can make problems?
Thanks in advance!!
---------------------------------------------
If you like Techhouse you can listen to my tracks here:
www.facebook.com/mister.adl

adl said:
Hi, really like your threads and just discovered this one.
I have a android.secure folder on my external sd card but am wondering, why I can't just delete that one, boot into recovery, wipe and flash the new ROM. In your steps you recommend to take out the card, put it into a card reader, delete the folder, put ROM on external sd card, put card in phone and boot into recovery. Wouldn't that be the same as if I delete it on my phone with a file Explorer and booting into recovery?
Or is this folder recreated while shutting the phone down?
Also, could you explain a bit why this particular folder can make problems?
Thanks in advance!!
---------------------------------------------
If you like Techhouse you can listen to my tracks here:
www.facebook.com/mister.adl
Click to expand...
Click to collapse
I know mate!
I couldn´t delete the .android.secure folder from phone within! I think its used from System and should not be deleted while the system is runnig.
I don´t know what errors/problems this folder could make, I always removed it first.
I think friedrich420 has written that it should be deleted because of making problems when switching from stock ROM to e.g. ECHOE ROM!

SLIM - Yes, Full - No
Hi!
Huge Fan of Echoe Rom. I have a very weird issue with the echoe celstial voices goint to echoe illusion v7. Flashed celestial voices and worked like a charm. Then Illusion V6 Full came up. So downloaded and flashed it. Again worked like a charm. Then I tried the slim version and from there, something weird happened. echoe illusion v6 slim with no kitchen worked out fine, but game me random resets and freeze. So i tried goin back to full. But I cant flash the full version. But can go back to slim without a problem. tried it 20 times now but still getting stucked at boot logo. then v7 came out and still same results.
Cant post to echoerom thread directly due to restrictions. Please advice as to what should i do. Thanks in advance.

fAiLOfax said:
I know mate!
I couldn´t delete the .android.secure folder from phone within! I think its used from System and should not be deleted while the system is runnig.
I don´t know what errors/problems this folder could make, I always removed it first.
I think friedrich420 has written that it should be deleted because of making problems when switching from stock ROM to e.g. ECHOE ROM!
Click to expand...
Click to collapse
Thanx mate!
Will try your way for Echoe 7, even i never encountered any trouble. :fingers-crossed:

adl said:
Thanx mate!
Will try your way for Echoe 7, even i never encountered any trouble. :fingers-crossed:
Click to expand...
Click to collapse
:laugh:
BTW: i like to get "thanx" if I could help you!

cut

Sorry, me with another question regarding external sd + android_secure.folder:
I should take out the external sd, delete the folder and put the ROM on the external sd card. Now when i boot right into revovery will the folder be created again? Cause then it would make more sense to leave external sd card out and put the ROM on internal sd card and flash from there.
As I usually do a fullwipe, including formating internal sd card the ROM would be formated as well. So the ROM needs to be on the external sd card, but then again the android_secure folder might be created while booting up in recovery...i hope you understand my dilemma. :silly:

adl said:
Sorry, me with another question regarding external sd + android_secure.folder:
I should take out the external sd, delete the folder and put the ROM on the external sd card. Now when i boot right into revovery will the folder be created again? Cause then it would make more sense to leave external sd card out and put the ROM on internal sd card and flash from there.
As I usually do a fullwipe, including formating internal sd card the ROM would be formated as well. So the ROM needs to be on the external sd card, but then again the android_secure folder might be created while booting up in recovery...i hope you understand my dilemma. :silly:
Click to expand...
Click to collapse
Man! The folder is created from the Android System not from recovery!
Make it like I said in the Guide and that's it!

fAiLOfax said:
Man! The folder is created from the Android System not from recovery!
Make it like I said in the Guide and that's it!
Click to expand...
Click to collapse
DUUUUDE!!
Thanks so much for the hint with android_secure folder! #
I had this weird issue that after flashing Echoe ROM Slim Version 3-6 that while booting up for the first time after flashing 4 apps where installed which where totally bloat stuff (such as "mytaxi" and some other shi*t)
I have a "free" Phone, so i always wondered what is happening as this couldn´t come from any "carrier" service. I also formated my external sd card but the problem was still there when i installed Slim V6.
With your methoed this time NO bloat App was installed after the reboot!
Thank you so much, i finally figured out what was causing this! :good:

adl said:
DUUUUDE!!
Click to expand...
Click to collapse
Thanks so much for the hint with android_secure folder! #
I had this weird issue that after flashing Echoe ROM Slim Version 3-6 that while booting up for the first time after flashing 4 apps where installed which where totally bloat stuff (such as "mytaxi" and some other shi*t)
I have a "free" Phone, so i always wondered what is happening as this couldn´t come from any "carrier" service. I also formated my external sd card but the problem was still there when i installed Slim V6.
With your methoed this time NO bloat App was installed after the reboot!
Thank you so much, i finally figured out what was causing this! :good:
Click to expand...
Click to collapse
Nice mate!
That makes me happy! :good:

I have this modem installed now, can i update to this rom without having to update modem? Or still needed? And can i TB everything back?
And will this modem break my sounds? Since ive seen some comments of users breaking there sound ...
Sent from my GT-I9505 using app: XDA Premium and rom: CarbonRom

[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: