[Q] nvFlash 4.0.0.2 problem on G2x - T-Mobile LG G2x

I have CWM 3.0.0.1 on my G2x right now. I ma running Nexxus latest ROM but it is giving me little problems where people are quite happy with. So after reading little more Nexxus Rom states to use latest CWM and that is why I am trying to upgrade.
So I did what was asked.
1. removed battery.
2. Started OneClickRecoveryFlasher.exe
3. Holding down up/down and plugging in the usb cable.
4. APX drivers were previously installed and I can see it in Device Manager
5. Started flashing by presing with "Flash CWM InternalSD/ext4 Support.
6. I get this
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
EXT4 External SD Support by TeamWhiskey
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
unable to retrieve platform info NvError 0x120004
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Any ideas? Is there a better way of upgrading CWM to latest?

Can you remove the old CWM and revert back to the stock recovery?

How can I revert? Go with nvFlash and do 3rd option "recovery to original"?
I also found 4.0.1.4 at http://forum.xda-developers.com/showthread.php?t=1003723
Is it safe to use this one on G2x.
Is there a way to upgrade CWM from current version by updating from some zip downloaded first to internal sd?
I found this recovery-clockwork-3.0.2.7-p999.zip as latest on http://www.clockworkmod.com/ for Tmogile G2x. Is this the latest that should be used on G2x or the site is not updated and I should use 4.0.x version.

I am using the.latest it is 4.0.1.4 I just flashed it last week I have no problems at all so I would do what you said and use the third option in nvflash and start o er from scratch. Just make sure you backup your current rom and jze tjtainium although I'm sure you have a stock backup somewhere right? Anyways do that and then install the same one you tried again and see what happens.
Sent from my LG-P999 using XDA Premium App

My problem was that I as using old drivers from LG downloaded somewhere from xda forum. After getting latest from LG support site it all went smooth

Related

Can't install any custom roms any longer

I am lost.
I had FireFly 2.05 on my SGS (ATT US version) and was going to update to 2.1. I followed the procedure as I aways do; ODIN 1 click to stock rom, master clear, copy update.zip and rom file and reboot into recovery. This time however I get the following error
E:Can't symlink /system/xbin/su SYSTEM:bin/su
E:Failure at line 14
I checked some notes on this and found out that it might be a currupt file. So I re-downloaded FireFly2.1 again and transfered the file to the internal SD card. The outcome was the same.
Then I copied the original 2.05 version back which I know was fine and I still get the same error. Even after a full stock 1-click and master clear the above error will not go away.
Is my internal SD card messed up? Or am I missing something else?
It's running stock right now and all seems to work fine, but I cannot stand all the bloatware and other crap ATT puts on the phone and really want to try FireFly2.1.
Any help is greatly appreciated.
Thanks.
Did you flash clockwork recovery
Did you root the phone after you flashed back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Agree with DaveyBB - sounds like you are not rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App
You do not need to root on stock just flash clockwork with update zip
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
anosis said:
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
To install clockwork select reinstall packages twice
The issue is not with cw recovery. I am already in it, but the error that i get is after i click "yes apply this zip"... The script starts to format the system, data, datadata, etc. And then this error shows up after files ate copied
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried re download of rom package?
My only guess is that clockwork and the rom are not working well. I would try downloading a different clockwork
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
Have you tried re download of rom package?
Click to expand...
Click to collapse
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Maybe try to reformat sd through clockwork
Problem solved, kind of.
My desktop PC, which I always use to transfer the files is somehow responsible for the error I get in CWM recovery. I ended up using my laptop to transfer the ROM to the phone and it worked again.
Something is messing up the USB transfer? That seems very odd but I am glad it's not the phone that caused the issue.
If I find out what the issue is with my Desktop I will post again just in case this rather rare issue might happen to someone else.
anosis said:
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Click to expand...
Click to collapse
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
bames said:
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
Click to expand...
Click to collapse
I don't think he's getting into Clockwork via ROM Manager, as he's said multiple times he's using the CWM update.zip; reinstalling packages in 2e recovery to get to CWM.
He's also said he doesn't believe this to be an issue with Clockwork (and I don't either). And I'm also pretty sure we're not dealing with newbie mistakes of Android Recovery vs. Clockwork Recovery.
any chance you're leaving your usb plugged into your cappy while you're trying to flash it?

[Q] ClockworkMod Recovery, ROM Manager, and Nandroid confusion

So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
bobblack said:
So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
Click to expand...
Click to collapse
Forget about Rom Manager. You have the correct recovery installed and you have made a "nandroid" backup when you used the backup option in CWM recovery 3.2.0.0 R4c. The Rom you want to flash needs to be on your MicroSD card and that needs to be in your Xoom when you boot into recovery. It is from the CWM recovery menu that you will choose to flash the zip file that will install the Rom. You will need to be able to boot into recovery and you can do it by pressing volume up and power to get to dual core screen, then after 3 seconds, press volume down then volume up and you should be in recovery. Or you could download Quick Boot from the market and use its boot into recovery option (that's what I do).
About the version you need to be on to flash Hammerhead...what does it say? I think you may need to be on 3.1 but just read the OP on the Hammerhead thread...it will tell you the requirements.
Good luck!
Thanks a lot for explaining that okantomi, that's very helpful and reassuring!
The only thing I'm left with now is to figure out the version part... the rom OP doesn't say anything about a required version. Here's the thread btw: http://forum.xda-developers.com/showthread.php?t=1203635
I made my way through the first 18 or so pages of the 434 total pages in that thread, but still couldn't find any info on that. I'll keep looking - not giving up
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
bobblack said:
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
Click to expand...
Click to collapse
Me too! ;^ )
Enjoy your shiny new Rom!

Need some Advice plz... SGS 4g with KJ6 + DoomLord'ed but missing CWM because...

Hi fellows
First of all I want to thank for the support im about to receive from such a great community.
I'm new to this whole thing of flashing, rooting, and who knows what else around the Android System and Samsung Platform.
I own a SGS 4G which i just flashed with the KJ6 rom and gained root access[TESTED] using Doomlord method since SuperOneClick wasn't working for me.
I mannaged to add the Init.d folder and to add some mods to it, but right now im tryin to install the Adrenaline mod but forced to stop due to the next situation:
I need the CWM in order to install the Adrenaline, downloaded the files / method from krylon360 (http://forum.xda-developers.com/showthread.php?t=1099374)
At first I got confused cause i had to replace the file /system/bin/recovery (which btw wasn't there) I found it in "/" ... anyways besides copying it in the mentioned folder (/system/bin) i replaced the one in the "/" and that went just fine [TESTED]
Now Im tryin to enter in recovery mode but i only get the 3e stock screen, I read around that there should be an option called "reInstall Packages" in the 3e recovery screen and i would be able to get into CWM from there, but the only options available are:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
Q! Am I missing something?.. am i forgeting about something?. cause i can't find the so called "reInstall Packages" option!!!
---------------
I read about the kernel Bali 3.3 but, it's not optimized for gingerbread (am i correct?)
So.. what are my options?.. how can i achieve my goal of installing the CWM
SuperONeClick only works on Froyo (2.2.x) roms, not Gingerbread (2.3.x).
The easiest way to gain root and clockworkmod recovery on a leaked GB rom is to flash an already rooted kernel through ODIN.
Go get one of DrHonk's modded GB kernels and flash it to your phone with ODIN. You'll get root + CWM at the same time, in one easy step. you should be good after that
Make sure you follow the directions.
http://forum.xda-developers.com/showthread.php?t=1194032
mike-y said:
SuperONeClick only works on Froyo (2.2.x) roms, not Gingerbread (2.3.x).
The easiest way to gain root and clockworkmod recovery on a leaked GB rom is to flash an already rooted kernel through ODIN.
Go get one of DrHonk's modded GB kernels and flash it to your phone with ODIN. You'll get root + CWM at the same time, in one easy step. you should be good after that
Make sure you follow the directions.
http://forum.xda-developers.com/showthread.php?t=1194032
Click to expand...
Click to collapse
Just one clic away from pressing that "Thank you" Button
One more question, what does it mean to "adb reboot recovery"
Quick Update
I FINALLY MADE IT.. ty for your advice mate!
GSG 4G KJ6 build ... Checked
Rooted? ... Checked
Kernel KJ1? ... Checked
WCM? ... Checked
Adrenaline? ... Checked
Now lets have some PHUN!!!.
Adb reboot recovery is a command you could issue from a command prompt if you have the Android Software Developement Kit (SDK) installed. Adb is the command, reboot is a parameter to the adb command, and recovery is a parameter that tells it to reboot your phone into recovery. Adb reboot download can put your phone in downloaf mode.
Hope that helps
Sent from my SGH-T959V using XDA App
stephen_w said:
Adb reboot recovery is a command you could issue from a command prompt if you have the Android Software Developement Kit (SDK) installed. Adb is the command, reboot is a parameter to the adb command, and recovery is a parameter that tells it to reboot your phone into recovery. Adb reboot download can put your phone in downloaf mode.
Hope that helps
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
thank you for ur explanation Stephen

[Q] CM7 / ICS Flashing issues

I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?
Are you trying to install the zip from ClockworkMod?
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either
movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?
Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.
Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck
Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.
A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7

[SOLVED] Can't overwrite CWM recovery

This thread might be a warning not to install CWM through ROM Manager until it's fixed. Aplogies to koush if it isn't broke and it was just my incompetence.
So... I got my TF101 on Saturday and after checking everything worked on it I rooted it with ViperMOD PrimeTime v4.5, installed Team Rogue recovery using the recovery installer apk and flashed Revolution HD ROM.
(I had to use ViperMOD for the rooting becasue I had already done the ASUS ICS update via Wifi)
Anyway, a few hours ago I saw on Twitter that ClockworkMOD recovery for the TF101 was now available. I thought great and installed ROM Manager from the market, clicked on flash CWM recovery and selected my device. It flashed CWM and rebooted into CWM.
Only problem is my device now boots up to CWM recovery every time I turn it on. Also I was expecting CWM to be better than the Team Rogue one but it turns out that the Team Rogue one lets you select a zip from your MicroSD card where CWM does not.
If I want to boot into the OS on my EeePad I have to hold the Vol Down on startup, wait 5 seconds at the recovery prompt and then I get the screen which allows you to wipe data or cold boot into Linux/Android. So I choose boot into linux and the OS starts loading.
This is a bit of a pain in the arse, and not what the device was designed to do so I'd like to get it back to nornal, preferably with Team Rogue recovery due to the better options it has.
I've tried running the Team Rogue recovery installer apk and also reflashing Revolution HD and it always boots up with ClockworkMOD!
My guess is that ROM Manager has placed CWM in an area of memory that it isn't supposed to go in, ahead of where the EeePad recovery should be.
Is there a hardcore recovery/kernel flashing utility I could use?
I've done a lot of flashing with phones but this is my first tablet so I'm a bit of a noob with the TF101.
I've been thinking: would flashing a stock ASUS ROM, complete with ASUS kernel and recovery, fix this?
I can't use nvflash because it's one of the SBKv2 models.
Is there a complete package I could flash with ADB/Fastboot?
Try wiping everything and install the rom again?...
Or.. download an older rom version from asus website and follow their instructions to load perhaps ?
I found out even though I've got a B70KAS serial device I'm lucky to be able to NVFlash. I've flashed a complete, stock Honeycomb image on there and it's sorted out my recovery sector.
It had me scratching my head as I thought I would be able to NVFlash, but I tried and it worked.
where did u find file?
Had same problem ,went to Asus site wouldn'tlet me downloads us version
Here is the page for the NVFlash of the Worldwide/UK version of the file mate:
http://www.wupload.co.uk/file/2628149097/Revolver_TF_3.11_nvflash_gnufabio.zip
I ended up finding out which file I needed and just did a google search for 'Revolver_TF_3.11_nvflash_gnufabio.zip'.
Then when I flashed that I had a brand new installation of Revolver Honeycomb which was rooted and an older version of ClockworkMod installed.
Make sure that you have the NVflash/APK drivers on your PC and you should be OK. I used Windows 7 64 bit and the flash went fine.
I then rebooted Revolver and used CWM to wipe and install the latest Revolution HD zip file from my microSD card. I'm back to Ice Cream Sandwich now and it's running OK.

Categories

Resources