i am using NfiniteFx45 stock ROM De-odexed (Hero.C.Sprint_2.27.651.6-3.A2SD.2.7U-3_signed) i updated to Recovery RA 1.6.2 so i can backup nandroid + ext. (I saw instructions that said to update to RA 1.6.2 if you had an earlier version, so I did. now everytime i try to do a nandroid backup + ext i get error: run 'nandroid-backup.sh' in adb. when i open command prompt and run nandroid-backup.sh it says i have to list a command {-b{--backup etc. thats where im lost. dont know how to enter it i entered -b (didn't work) entered --backup (didn't work). can someone assist me please?!?
I am using a2sd also.
I don't think you can do the nandroid+ext with amon ra recovery. Try just a standard nandroid.
You could also try clockwork mod recovery.
Sent from my HERO200 using XDA App
Try putting the recovery img on the root of your SD card ( make sure to name it properly ) power down ur device then reboot into recovery holding the home and power button then plug your phone into ur computer/laptop then from adb reflash the recovery might work for you good luck
Root-Hack-Mod-Always™
if that doesn't work i would strongly suggest ClockworkMod Recovery. I've been using it for months now with no problem.
First I would suggest posting in the right section. This is a question and rules say don't post questions in this section. Its a very huge thread posted above saying this.
Don't be lazy next time and read rules.
But I would suggest clockwork mod recovery.
Sent from my HERO200 using XDA App
Thanks guys, even the forum cop.
Sent from my HERO200 using XDA App
t12icky0 said:
First I would suggest posting in the right section. This is a question and rules say don't post questions in this section. Its a very huge thread posted above saying this.
Don't be lazy next time and read rules.
But I would suggest clockwork mod recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I will next time
Clockwork Mod = Fail
Did u try what I suggested it might work?
Root-Hack-Mod-Always™
bodyshop said:
i am using NfiniteFx45 stock ROM De-odexed (Hero.C.Sprint_2.27.651.6-3.A2SD.2.7U-3_signed) i updated to Recovery RA 1.6.2 so i can backup nandroid + ext. (I saw instructions that said to update to RA 1.6.2 if you had an earlier version, so I did. now everytime i try to do a nandroid backup + ext i get error: run 'nandroid-backup.sh' in adb. when i open command prompt and run nandroid-backup.sh it says i have to list a command {-b{--backup etc. thats where im lost. dont know how to enter it i entered -b (didn't work) entered --backup (didn't work). can someone assist me please?!?
I am using a2sd also.
Click to expand...
Click to collapse
Most times when you get that error, it means there isn't enough space on your SD card to make the backup. Do you have at least 300 MB free on your card? You may even need more than that if you are trying to do nand + ext. That could possibly be the reason for your error if you don't have enough space.
I got the same error before I updated to Darch's Amon RA 1.7
http://darchroms.pocketdevelopers.com/recoveries/RA-Darchstar.img
chromiumleaf said:
Most times when you get that error, it means there isn't enough space on your SD card to make the backup. Do you have at least 300 MB free on your card? You may even need more than that if you are trying to do nand + ext. That could possibly be the reason for your error if you don't have enough space.
Click to expand...
Click to collapse
yes second that one actually...i had only 200mb free from having 2 nandroids on my sd card..deleted one and had around 375mb and it worked great. must have 300mb in order for all the Temp folders/files to work.
add144 said:
I got the same error before I updated to Darch's Amon RA 1.7
http://darchroms.pocketdevelopers.com/recoveries/RA-Darchstar.img
Click to expand...
Click to collapse
My fav. recovery so far, but I'm using Darch's Godspeed now because he recommended it for Darktremor a2sd.
I usually get that error when I try to nand +ext, with full batt and lotsa memory on card and in phone. I've gotten it simply nand-ing w/ low batt too. I've put it down to a lack of understanding regarding Darktremor and a2sd in general.
With NFX Hero I get constant "android media" f.c.s and have no access to much of anything on sd. Usually run one of Darch's cm6s.
Ezintn said:
My fav. recovery so far, but I'm using Darch's Godspeed now because he recommended it for Darktremor a2sd.
I usually get that error when I try to nand +ext, with full batt and lotsa memory on card and in phone. I've gotten it simply nand-ing w/ low batt too. I've put it down to a lack of understanding regarding Darktremor and a2sd in general.
With NFX Hero I get constant "android media" f.c.s and have no access to much of anything on sd. Usually run one of Darch's cm6s.
Click to expand...
Click to collapse
Drarch's 1.7 amon RA is slightly newer than Godspeed, ad it's also overclocked. I'd check it out, it's pretty good IMO
So can a nandroid + ext backup be done with RA 1.5.2? Thats the only reason i even changed the Recovery to RA 1.6.2 because this post http://forum.xda-developers.com/showpost.php?p=7054986&postcount=7 Said you needed to switch to 1.6.2 id you didnt have it. I just want to upgrade my SDcard from 2GB to 8GB.
Just make sure you have more then 30% battery and decent space left on your SD card. Sometimes recoverys are corrupt but rarely. I use clockwork recovery. Don't freak either lol. You should have a working backup on your comp ^_^
Sent from my HERO200 using XDA App
theimpaler747 said:
Drarch's 1.7 amon RA is slightly newer than Godspeed, ad it's also overclocked. I'd check it out, it's pretty good IMO
Click to expand...
Click to collapse
Switching back, thanks!
Ezintn said:
Switching back, thanks!
Click to expand...
Click to collapse
No problem, let me know if you need any more help
feefeeboomboom said:
Just make sure you have more then 30% battery and decent space left on your SD card. Sometimes recoverys are corrupt but rarely. I use clockwork recovery. Don't freak either lol. You should have a working backup on your comp ^_^
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
OK so i was trying to switch recoverys for nothing. I figured if there was the option for nandroid backup + ext on the recovery then it should work. I mean i don't think developers would put an option that doesn't work, they'd just omit it right? Im still kind of new and this post says u need RA 1.6.2, if you dont have it get it. that's why i thought it wouldn't work. They should update that information.
Nand+ext 2 or 3 times w/ Darch's RA 1.7, no errors - thanks theimpaler747!
Often I can avoid old data by checking post dates, but sometimes that gets confusing, it's great when dev.s keep their instructions up-to-date! So what's the best a2sd to use w/cm6 builds? native? Darktremor (with out dated directions)? This stuff can change fast !
Related
Hey all,
I know I just put up my tutorial on how to do this but hopefully this will make things easier for everyone. I'd still suggest doing a nandroid backup first just to make sure but I tested this on my phone so it should work. Just run the app and if this is the first time moving your apps to your sd card(and you want to keep the ones you have) leave the checkbox checked. Otherwise uncheck it. Then just press the buttons that correspond to what you want to do. Enjoy
In order to use this you MUST:
1: Have an apps-to-sd ROM
2: Have your sd card partitioned correctly with FAT32 first and ext2 second.
3: Have busybox already installed to /system/xbin
NOTE: I'll try to help as much as I can but I can't take responsibility for anything this does to your phone. I'm pretty sure nothing bad will happen and nothing irreparable can happen but gotta say these things just to be sure anytime I'm messing with root permissions.
ANOTHER NOTE: I'll put this up in the market for $1. It'll remain free here but people can donate to me that way.
YET ANOTHER NOTE: I've managed to get a new method working that's a lot more stable and flexible. I will keep this thread here but won't be maintaining it.
EDIT: Moving data is too unstable, I've removed the option. It doesn't force close anymore when you don't have the setup right, it just gives an error and wont let you do anything, so that's better.
Tried it this morning and worked great. You might add a pop up at the end of moving apps to restart the device. When less experienced people use it, they won't know to do that I'm afraid.
the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd
Nismo300zx said:
the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd
Click to expand...
Click to collapse
OH SHOOT!!! I fixed this problem on the market one but forgot to put it back up on here. Umm... for now no1 should use the one posted here, until I can get home and post the updated one. OR if you still want to fix this and don't much just a bit of fiddling in the recovery terminal, after moving apps to sd, restart in recovery mode and do this:
Code:
mount data
ln -s /system/sd/app /data/app
For anyone who cares about such things, the problem is that it deletes the /data/app folder and then makes a symlink, which sounds ok, except that every super user command has to be run through the whitelist app... which no longer exists. So it's not able to set up the link and all hell breaks loose.
i did use the 1 from here
it says ln: /data/app: file exists
if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?
Nismo300zx said:
i did use the 1 from here
Click to expand...
Click to collapse
ya it's the one from here that's broken, sorry. If you haven't already flashed back and everything(still have the boot loop) then you can use the code I posted and it should fix it. I'll post the updated version tonight when I get back home.
AbsoluteDesignz said:
if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?
Click to expand...
Click to collapse
Yes, just uncheck the checkbox. But you might want to read the note that I just posted, there's a known problem with it that has a fix but requires going into the recovery terminal. I'll post the updated version of this app that doesn't have that bug tonight.
jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me
Nismo300zx said:
jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me
Click to expand...
Click to collapse
Try reading a few of the posts above yours.
ThaBadBoy said:
Try reading a few of the posts above yours.
Click to expand...
Click to collapse
i been at this for 2days ive tried evrythin ..hmm time to give up soon
Nismo300zx said:
i been at this for 2days ive tried evrythin ..hmm time to give up soon
Click to expand...
Click to collapse
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on
Dantehman said:
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on
Click to expand...
Click to collapse
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up
Nismo300zx said:
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up
Click to expand...
Click to collapse
you had the "stale NFS handle" right? I'm not really sure what's going on but something in your phone's file system sounds like it went screwy. Maybe someone like JF or LucidREM could help? Your problem goes way over my head and I'm guessing the same is true of a lot of people on here unfortunately.
its cool imma jus stay with apps n caches to sd...n kep dalvik on the fone..i got passed the nfs error and get stuck at tmo g1 screen maybe ill try again l8ter
jf rom
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually
jjjackson56 said:
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually
Click to expand...
Click to collapse
It should work on any apps to sd ROM. This includes LucidREM's modified JF ROMs. If you're gonna be manually changing it into an apps to sd, then I would think it would work but can't promise it. I wasn't able to figure that out when I tried so I'm not 100% sure that they work the same but I would imagine they would. Again, though, the one posted here has that known bug which will be fixed after I get home from work.
Short answer(s):
Haykuro's ROM: definitely works
LucidREM ROM: Don't have it to test it but almost assuredly works
Self-modified: probably works?
Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial
jjjackson56 said:
Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial
Click to expand...
Click to collapse
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...
[email protected] said:
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...
Click to expand...
Click to collapse
True. that sure would be a lot I dont even think all the apps in the market would fill 2gigs lol. Thanks for your work look forward to trying it later
Hi,
Sorry if I'm wrong,
But thanks to NK02 mentioning in a thread to make one small change to boot.img ramdisk I now have JACHero 2.7.3 fully working (WIFI Bluetooth & FAST!) on my Magic 32B.
I used the normal update.zip from the dream forum, and extracted and changed the boot.img and flashed it in fastboot.
Heres the boot.img to save you making the change as well
http://www.megaupload.com/?d=R8OX15W1
I had also previously partitioned my sd card to have an ext2 and swap partition, all of which have been set up automatically so I know the boot.img is working as intended.
Very happy bunny now
UPDATE:
Seems to work for some. Having your SD card prepped with 3 partitions helps a lot.
Speed is going to be slower than say the NK02 Cyano ROM, but thats down to Rosie and the limited RAM, don't think we'll ever get that perfect.
At least now we know a way to use Dream Roms easily (sorry 32A owners, I think K4R1M will have something for you later)
UPDATE 5PM
i just used same method on cyanogens latest rom and works perfectly
Sounds real nice :> What about the gyro/compass ? Doesnt seem to work for me when using the original JACHero 2.7.3
Running well after 1 hour, widgets all stock not removed any and NO rosie reloads.
Little bit of lag, but nothing terrible (and for me to say that means it is hardly there!)
Anyone else tried it? I want to rule out me doing something silly
Compass working (at least in sky map)
Hi Again
Trying to set-up my sd card paritions, but parted command in adb shell is not working (not found error). Do I need a particular recovery image to be able to use parted ?
Thanks!
dazcox5181 said:
Running well after 1 hour, widgets all stock not removed any and NO rosie reloads.
Little bit of lag, but nothing terrible (and for me to say that means it is hardly there!)
Anyone else tried it? I want to rule out me doing something silly
Compass working (at least in sky map)
Click to expand...
Click to collapse
i dont think there is a magic recovery with the parted command. thats why i used a Gparted live usb boot (google unetbootin - will create a bootable usb stick for you) and a card reader in my netbook (yes I use a MSI wind with OSX )
well done dazcox.
can you please describe the process people need to take to load up boot.img?
eg. recovery screen, wipe, flash G1 ROM, reboot, let ROM load, reboot into fastboot, flash boot.img,.. and the required commands etc.
might be annoying, but it'll help to answer the flood of questions that your answer has brought
presumably as each new ROM produces changes we will need to edit the boot.img each time, as they may contain updates, yah?
Yes, I would assume each time new release we make the change.
My Process was this.
download the scripts from http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
(beware if on OSX google and download newer cpio utility and copy to /usr/bin)
Download JAChero 2.7.3 full from dream forum
rename downloaded file to update.zip and copy to sd
on computer open update.zip and extract boot.img
Use unpack-bootimg.pl boot.img to extract the kernel and ramdisk
in the ramdisk dir rename init.trout.rc to init.sapphire.rc
repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk boot1.img
On your phone reboot to recovery (I use amon ra recovery from this forum)
BACKUP (nandroid is your saviour)
wipe
apply update.zip
reboot, but go straight to fastboot (vol down + power)
in fastboot
fastboot flash boot boot1.img
reboot
enjoy
*decide you want to try something else and start all over again*
For me who already have JACHero 2.7.3 installed with the cyanogen kernel, can I just flash the boot.img or do I need to make a complete wipe and include it into the update.zip?
zw4mp said:
For me who already have JACHero 2.7.3 installed with the cyanogen kernel, can I just flash the boot.img or do I need to make a complete wipe and include it into the update.zip?
Click to expand...
Click to collapse
I would rather use the full update.zip and then flash the boot.img to be sure.
Sorry - I'm learning as I go and don't know how to sign an update.zip yet
@ dazcox5181
can you make a working update.zip for us?
jan.lamp said:
@ dazcox5181
can you make a working update.zip for us?
Click to expand...
Click to collapse
I might later, probably not though, as it's really easy to do.
I've followed the steps, and after flashing the boot1.img adn rebooting, the phone is really taking forever.
The screen is totally dark but i know the phone is on as i can enter through adb to it.
Any tips?
I had from before a class 6 card with 3 partitions, FAT, ext2 and swap (in that order).
Thanks
did you wipe/flash the normal (not ported) jachero rom first?
Then fastboot flash the boot.img?
Yes please +1
jan.lamp said:
@ dazcox5181 can you make a working update.zip for us?
Click to expand...
Click to collapse
+2
That would be fantastic for those of us that I are still on the steep part of the learning curve...
Cheers
Ben
Signing and uploading update.zip now...
When I get my paypal sorted you all owe me a beer!
I'm flashing it myself to be sure, upload will be done in about 20min then i have to do some work.
My update_signed.zip failed, can't find update script error.
Anyone help? the only file I changed was the boot.img?
dazcox5181 said:
Signing and uploading update.zip now...
When I get my paypal sorted you all owe me a beer!
Click to expand...
Click to collapse
With the new update all predone all that needs doing is the partitioning of the sd card to be fat32 + ext2 then update rom in normal way, correct?
dazcox5181 said:
I would rather use the full update.zip and then flash the boot.img to be sure.
Sorry - I'm learning as I go and don't know how to sign an update.zip yet
Click to expand...
Click to collapse
I decided to try just flash the boot image before redoing it all to see what would happen, and it is actually working Wifi and gyro didnt work before but is now.
The only thing is that Bluetooth A2D2 mode (playing music) doesn't seem to work. It says "playing media through bluetooth headset" but I get no sound. Can anyone confirm that this is working for you? If so maybe I will need to wipe and reinstall anyway.
stevetigersix said:
With the new update all predone all that needs doing is the partitioning of the ad card with an ext2 then update rom in normal way?
Click to expand...
Click to collapse
That will be the plan, if i can get the update.zip to work
dazcox5181 said:
That will be the plan, if i can get the update.zip to work
Click to expand...
Click to collapse
Sweet looking toward to it daz, now all I've got to do is pluck up the bottle to root and partition the ad card then install your Rom , I'm new to this on android lol
Hello,
I wasn't able to post a response in the Development forums yet, so please move this thread if you see fit and sorry as I'm still new to posting here.
------------------------------------------------------------------
I am using the original full leaked version of the ROM.
If you are having issues using ODIN to flash Dr. Honk's amazing new kernel: [http://forum.xda-developers.com/showthread.php?t=1194032] Or if you are having issues with not seeing your SD card after successfully flashing the kernel try the steps below:
If your having issues with ODIN, get Winrar and extract the zimage from the tar file and use heimdall and it should flash correctly. After you flash the kernel and boot up, you may notice your not seeing your SD card. Try going to recovery which you can now! Wipe your data<factory> then your Cache, then wipe your Dalvik Cache and use fix permissions. Reboot and you should now see your SD card, only catch to this kernel is Dr. Honk's forgot to add busybox, so I would go to the market and get it then you can also use Voodoo lag fix.
It's working great for me! Good Job Dr. Honk!
You would likely get a little more assistance if you would give more info (what room you're currently using; where you're stuck).
honestly, if you're having issues with this install you would probably do better to wait.
Sent from my SGH-T959V using XDA Premium App
I'm Sorry, Did I not clarify my post? I'm not having issues, was trying to help others who are in a forum I cannot yet post in and for others who might have the same issues that may look to the General Forum. Sorry if I wasn't clear enough.
I don't think he has any issues.. he's posting a tutorial for others
Sent from my SGH-T959V using XDA App
bytesfree said:
I'm Sorry, Did I not clarify my post? I'm not having issues, was trying to help others who are in a forum I cannot yet post in and for others who might have the same issues that may look to the General Forum. Sorry if I wasn't clear enough.
Click to expand...
Click to collapse
My apologies... I miss read.
Sent from my SGH-T959V using XDA Premium App
LoL, no problem man...I just figured it would be good to give back to this great community with some helpfull info for once
thanks for the tip!
dont know if this helps or not but this is how i got mine working:
i flashed kg4 leak then did dsextons gb rom root,
then i installed busy box and installed on phone,
then flashed drhonks new kernal for kg4 (his new download works)
now everything works great in=m on ext 4 system cache and data and also have cwm recovery support
Thanks for the tips.
I tried all above, the SD shows right, but I still cannot have lagfix properly work and convert EXT4. Everytime system restart, it reports not enough space on SD card, but actually I have 14 GB available on my SD.
I did my flash exactly like jdubb. it worked flawlessly. Thanks drhonk for everything you do for us
Sent from my SGH-T959V using XDA Premium App
did you install busybox before you flashed the kernel?
jdubb1106 said:
did you install busybox before you flashed the kernel?
Click to expand...
Click to collapse
Yes, I did. I checked the log, it shows the /sdcard avaialbe space is negtive like "-1353 MB". Really strange.
hunterwei said:
Yes, I did. I checked the log, it shows the /sdcard avaialbe space is negtive like "-1353 MB". Really strange.
Click to expand...
Click to collapse
Hunter, can you try this:
pop in an other micro sd, boot into CWM, format sd, enable voodoo ext4 and reboot.
if you don't have a spare one, backup files from the current sd card then proceed as above.
Can someone post the precise links and directions that they used to get this working, please! Much appreciated!
Bro, I really appreciate your quick tip, but I tried it, the issue remains.
Having been searched XDA whole afternoon, still have no idea
ddang25377 said:
Hunter, can you try this:
pop in an other micro sd, boot into CWM, format sd, enable voodoo ext4 and reboot.
if you don't have a spare one, backup files from the current sd card then proceed as above.
Click to expand...
Click to collapse
I was reviewing the source code of voodoo lagfix, just feel like the my sdcard available space is not properly read from lagfix code.
Not sure if you guys still using the factory SD card, I am using the 16GB one came with the phone.
Issues with SD card.
For those of you with issues on their SD card, did you by chance try enabling lagfix via Voodoo Control app? That is what I had to do to get lagfix working properly. I disabled it via recovery and then enabled it via control app. Somehow got it working that way lol.
Unable to answer inbound calls
The install went flawless and phone works great. I do have a major issue though, inbound calls are cause a force close and create an instand missed call. Is anyone else having issues being able to answer inbound calls? I can make calls just fine, it just refuses to let me answer a call.
I am currently running:
2.3.4 KG 6 with the 2.6.35.7 Kernal.
This worked great for me on kg4, but for some reason i flash this on kg6 and after the flash boots up fine. But whenever i restart my phone i get a boot loop at the samsung screen. So confused Any ideas?
kkoshko1 said:
This worked great for me on kg4, but for some reason i flash this on kg6 and after the flash boots up fine. But whenever i restart my phone i get a boot loop at the samsung screen. So confused Any ideas?
Click to expand...
Click to collapse
I was getting the same thing when I turned on Voodoo so I went back to recovery to disable Voodoo (I had to use ADB since the phone wasn't functional long enough to use the Quickboot app).
Then (per crackpot in a dev thread (http://forum.xda-developers.com/showpost.php?p=16264528&postcount=222) booted back up and used the Busybox Installer from stericson to make sure Busybox was installed into bin and not xbin.
Then back to recovery and enable Voodoo.
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]
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.