I hope my post will help somewhat those buddies who had the same problem or who will probably have this problem in future.
I had the problem that my gtablet couldn't power on after I did Nvflash. I'd been frustrated in the past week for searching the internet to find the way out.
The similar problem that tcrews had. (http://forum.xda-developers.com/showthread.php?t=903684)
Also some posts I browsed:
http://forum.xda-developers.com/showthread.php?t=999287
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
http://forum.xda-developers.com/showthread.php?t=927006
http://forum.xda-developers.com/showthread.php?t=971608
http://forum.xda-developers.com/showthread.php?t=938706
I am grateful to tcrews and a lot of other buddies for their inputs which saved me lots of time, though i didn't find a right solution from their posts. Acidburn89's solution in tcrews's post (page 9) didn't work out for me either.I don't know whether tcrews solved his problem in acidburn89's method.
I tried all the methods I could find and nothing worked out for me. The only way I can turn the tablet on is to follow tcrews's post on rebooting the tablet by using nvflash (nvflash --bl bootloader.bin --download 9 recovery.img --go)
Some background of bricking my gtablet:
1.my gtab had CWM0.8.and was running rom "zpad clean 3.0" (before that it was TNTL, not any problem)
2.one week ago, I was trying to flash a rom from a chinese website, which was modified from the official malata zpad rom. This was the problem started from. After flashing (nvflash method),the tab was rebooting and stuck at "Tegra II" logo and couldn't never start with the new rom. At this moment, i could still power on and off the tab.
3.next I flashed my tab by following this link (http://forum.xda-developers.com/showthread.php?t=861950) After flashing it, the tab couldn't not reboot, and could not power on. Every time I pressed the power button, it just went to the APX mode authomatically
(with black screen).Only using the above-mentioned method (from tcrews) I could start the tab.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
2.Copy recovery-stock.img into the nvflash folder.
3.Start the tab by nvflash (tcrews' method)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
I tried this method with and without CWM. Both worked. So don't worry whether you tab has CWM or original recovery. My advice: flash your favorite rom using sdcard method instead of nvflash. If you want to nvflash it, save all the files we have used for possilbe repeation of our above job to get your tab back to life!!
I've received a lot of information and help from xda-development before, and hope my first post could contribute to our community a little bit.
Just noticed that idocinthebox has the same idea of correcting recovery.img in this post:
http://forum.xda-developers.com/showthread.php?t=994046
Master
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Well done! If this helps anybody mash the thanks button ;-) ^^^^^^^^^^^
Exact same issue
Can you provide your stock update.zip file? I have not been able to find a file that works for me. So far I have repeated this process many times with many update.zip fules but its still wont start on its own.
I can fin a update.zip.... can you posted here?
Thanks.
I follow this thread but still my gtab is power on APX (only). I was using the stock 3588 and went to the new 4349... start to having issues decided to go back to 3588 using the nvflash. it worked at the first time (until I had the tablet on) As you turned of and turned on, just a black screen (apx) and the only way to get it back is running the nvflash again but if I turned off have to do it again.
Please help!!!!
I can't figure it out on my own.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/show...54&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
*** could you posted your original (stock rom) update.zip? The one above mention is not in zip format. I did a zip format but still not working.
2.Copy recovery-stock.img into the nvflash folder. (i did that)
3.Start the tab by nvflash (I did that)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
*** the only way I could put the update.zip in the internal sdcard on the tablet was after nvflash the tablet power up, then I plug a usb drive (with update.zip in it) and copy to the internal sdcard... i did not plug the tablet to the computer.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
*** I did that the same way above mention from a usb drive.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
6,7,8,9,10,11 **** I did all but at the end still my tablet only work with nvflash unless I never turned off!!!
that download is corrupt...
Err it's the img ranamed... by bad..
Naysses and jettajon:
I uploaded the original update.zip I extracted from my G-tab. Try it to see whether it can help u.
w w w.mediafire.com/?fywhca6fi514toq
(remove space between "w"s)
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Citi said:
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Click to expand...
Click to collapse
I ran across this post http://forum.xda-developers.com/showthread.php?t=1010659 which says that the BCT part of the nvflash isn't the same for all the GTablets and that's my experience.
I couldn't get nvflash_gtablet_2010110500.zip (from the dropbox repository of nvflash files) to work, but nvflash_gtablet_46_2010112600.zip worked fine.
The problem was that I couldn't get CM7 installed on my GTablet, but then I hacked the gtablet.cfg file to swap partitions 7 and 8 by merely cutting and pasting the partition 8 (name=OGO stuff) and putting it before the partition 7 (name=BLO stuff) to match the order of the gtablet.cfg in nvflash_gtablet_2010110500.zip.
Now CM7 has installed and seems to be working fine for me.
BTW- I didn't nvflash the CWM recovery since I was trying to minimize the number of things I was messing with. I assume it'll work, but I already had CWM installed on the internal emmc (SDCARD2) so really didn't even need to nvflash it.
Nope, I have tried both files and neither worked for me
kaluna00 said:
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Click to expand...
Click to collapse
guobug you are a hero
same thing happened to me
and because of you it works!!!
( followed the steps and used your updat.zip)
BUT I have another problem
when I tried to install CW
it says "Can't open sdcard/recovery.log"
now I dont know what to do
because I want to install another rom
I think there is something corrupted in the device after apx boot loop
You are a life saver. Worked like a charm. Have been reading through 50 million threads the last 3 days, and happened to find this one. Absolutely amazing. Thanks.
In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!
guobug said:
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
Click to expand...
Click to collapse
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
BrandonJay21 said:
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
Click to expand...
Click to collapse
That error means the command 'nvflash' is not in the path for the windows command line.
Where do you type the DOS command at? Thanks.
when I hold the volume up and hit enter on the keyboard I get a bad command prompt. What am I doing wrong?
Related
Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe
can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.
I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.
do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.
Following is the NVFlash procedure for installing ClockWorkMod (CWM) for those
people who are having boot loop problems (or other problems) and need
to install CWM by flashing rather than by using /sdcard or a microSD card
via /SDCARD2. No apologies -- this is written so even the new folks can use it.!
1. You need to get a copy of ClockWorkMod v.8, which can best be done
by downloading through the following thread. Also, you might check the
thread for related info -- it's a good one:
http://forum.xda-developers.com/showthread.php?t=1010943
2. Once you have the CWM files, go to your NVFlash directory (or whatever
you call it) and make sure you have the right files in it.
-- Nvflash.exe and related files (nvflash_gtablet_2010110500.zip) from
the original NVFlash Recovery thread.
-- USB drivers (also from NVFlash Recovery thread. If you already are
flashing via APX you should have them installed.)
-- The file "nvflash_gtablet.bat" from the NVFlash Recovery thread.
-- The CWM .img file (next item will tell you how to get it.)
3. Next you will need to extract the CWM .img file from the .zip file you
downloaded. First, extract the files from the download -- you should get
a recovery folder and an update.zip. Now unzip the update.zip file and
you will get a file named recovery.img.
4. Rename the file "recovery.img" to "part9.img".
5. Now edit the file "nvflash_gtablet.bat to make the command line read:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
The command line above for the .bat file does require the quotes around
nvflash.exe!!!
Or you can simply leave the other .bat file alone and create a new
nvflash_cwm.bat file and put the cwm command line in it if you want to.
6. Boot your tablet into APX mode using power/volume - (you will have a black
screen). Connect the USB cable from your G-Tablet to your PC. If you check
the little USB/green check icon on the PC toolbar (bottom right corner of screen)
you see an APX connection listed.
7. Go to the NVFlash subdirectory on your PC and run the .bat file to load CWM.
8. When the flash is done, use the USB/Green Check icon to disconnect from
the PC and then disconnect from the G-Tablet.
9. Shut down and the boot the G-Tablet into Recovery Mode by pressing
Power/Volume + and hopefully you will see the word "Android" and then the
green CWM menu will appear."
Now you're ready to do whatever you need to do with CWM.
Hope this helps.
Rev
This suggest that NVflash tool is more versatile. Not only can you flash the stock ROM but also the recovery and perhaps other ROM's as well.
Thank you for the post. It worked wonderfully. It saved me from having to buy a sdMicro card that I would not need otherwise.
holzy99,
NVFlashing is most useful -- but it also is useful to have a microSD card handy.
In the Q&A forum you will find a similar post I did on how to install CWM using a
microSD card in a pinch. When you need it, you need it!!!
butchconner said:
Following is the NVFlash procedure for installing ClockWorkMod (CWM) for those
people who are having boot loop problems (or other problems) and need
to install CWM by flashing rather than by using /sdcard or a microSD card
via /SDCARD2. No apologies -- this is written so even the new folks can use it.!
1. You need to get a copy of ClockWorkMod v.8, which can best be done
by downloading through the following thread. Also, you might check the
thread for related info -- it's a good one:
http://forum.xda-developers.com/showthread.php?t=1010943
2. Once you have the CWM files, go to your NVFlash directory (or whatever
you call it) and make sure you have the right files in it.
-- Nvflash.exe and related files (nvflash_gtablet_2010110500.zip) from
the original NVFlash Recovery thread.
-- USB drivers (also from NVFlash Recovery thread. If you already are
flashing via APX you should have them installed.)
-- The file "nvflash_gtablet.bat" from the NVFlash Recovery thread.
-- The CWM .img file (next item will tell you how to get it.)
3. Next you will need to extract the CWM .img file from the .zip file you
downloaded. First, extract the files from the download -- you should get
a recovery folder and an update.zip. Now unzip the update.zip file and
you will get a file named recovery.img.
4. Rename the file "recovery.img" to "part9.img".
5. Now edit the file "nvflash_gtablet.bat to make the command line read:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
The command line above for the .bat file does require the quotes around
nvflash.exe!!!
Or you can simply leave the other .bat file alone and create a new
nvflash_cwm.bat file and put the cwm command line in it if you want to.
6. Boot your tablet into APX mode using power/volume - (you will have a black
screen). Connect the USB cable from your G-Tablet to your PC. If you check
the little USB/green check icon on the PC toolbar (bottom right corner of screen)
you see an APX connection listed.
7. Go to the NVFlash subdirectory on your PC and run the .bat file to load CWM.
8. When the flash is done, use the USB/Green Check icon to disconnect from
the PC and then disconnect from the G-Tablet.
9. Shut down and the boot the G-Tablet into Recovery Mode by pressing
Power/Volume + and hopefully you will see the word "Android" and then the
green CWM menu will appear."
Now you're ready to do whatever you need to do with CWM.
Hope this helps.
Rev
Click to expand...
Click to collapse
very nice!
just need some clarification..
where are we installing the NVFlash directory and APX drivers?
on the PC or on the Gtablet?
On your pc.
Help needed in NV Flash
Sticky thanks for putting such a detailed guide and appreciate that very much. I followed your guide and i am stuck at the NV Flash started. I believe that I had a confusion while editing the nvflash.bat. I edited the NV Flash.bat as following:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --download 9 part9.img --create --go
@set /p batuserinput=Press enter to continue:
Please let me know if I an making a mistake here.
punjabigator,
You were very, very close. The command line needs to be \
exactly what was in the Procedure:
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Change it to that and try again.
Rev
Didnt work for me stops on
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Nvflash started
and thats it
Same here
NVFlash starts, but doesn't go anywhere. I am trying to get back to CWM after an NVFlash that has left me with arecovery kernel boot image message switching me away from CWM. Any advise?
Thank you for all you have done for everyone using these! It has been a lifesaver!
Power off
Press Power And Volume-
Start NvFlash
I am going to receive my gtablet this weekend and the first thing I was planning to do was install cyanogenmod. According to the guide on the cyanogenmod website (http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide), they do not mention anything about nvflash. Is that really required. This is the first time I am modding. Thanks
still stuck in boot loop
Tried this .bat change, it did complete successfully but there were no changes.
Now I can turn it on and have SV birds/gtablet screen changing and shutting off at the end. I can use Nvflash but like I said, regular .bat or this modified didnt work.
anyone in the south Florida area , i cant get this to work right too many downloads g- tablet is driving krazy
Problems with NVFlash
Ok so I have CWM and BL 1.1 on my GTab. I would like to move to BL 1.2 so that I can install a 1.2 Honeycomb.
I also only have access to linux.
So I got the Linux NVFlash tool. I try to get into APX mode and that just boots me into the CWM recovery. NVFlash does not find my GTab.
lsusb shows:
Bus 004 Device 031: ID 0955:7100 NVidia Corp.
Then when I try ./nvflash_gtablet.sh I get:
Nvflash started
UnKnown device found
Done!
Nothing happens.
What am I missing? Has anybody found a good Linux how to?
Thanks
edit
Figured it out.
It is power and volume -
Djnasty18 said:
Didnt work for me stops on
"nvflash.exe" --bl bootloader.bin --download 9 part9.img
Nvflash started
and thats it
Click to expand...
Click to collapse
Yep same problem for me.
New gtab 2.1
Followed cyangen install instructions in the update guide and there was no mention of differences between 1.x and 2.x platforms. SO of course I put a 1.x CMW on my 2.1 platform. Cant boot into recovery. Can boot into the god aweful stock rom.
Followed the NVflash instructions. Installed drivers.
One interesting note is that after finding the apx device, pointing to the drivers, and completing the install (windows of course), there is no apx anything in my drivers lists.
Im in desperate need of getting CMW on this thing.
THanks for you help.
gtablet down
my gtablet will not boot up from any media pleeeease help
rvsuper8 said:
Yep same problem for me.
New gtab 2.1
Followed cyangen install instructions in the update guide and there was no mention of differences between 1.x and 2.x platforms. SO of course I put a 1.x CMW on my 2.1 platform. Cant boot into recovery. Can boot into the god aweful stock rom.
Followed the NVflash instructions. Installed drivers.
One interesting note is that after finding the apx device, pointing to the drivers, and completing the install (windows of course), there is no apx anything in my drivers lists.
Im in desperate need of getting CMW on this thing.
THanks for you help.
Click to expand...
Click to collapse
Go here http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm . Do the 1.2 branch (4349) Stock Rom 1.2 brach with CWM preinstalled. Follow the instructions. One you get back to stock 1.2 branch, go the Start Here page http://viewsonic-gtablet-for-dummies.webs.com/ and do code green.
hugdbear said:
my gtablet will not boot up from any media pleeeease help
Click to expand...
Click to collapse
Can you expound alot!!! What rom are you on, what were you doing, what do you mean by can't boot from any media, etc. Be as detailed as you can so we can assist you.
I think I might be missing something and I apologize if you feel like you are repeating yourselves but when you edit the .bat file what exactly do you put in the file? If someone could just paste into here what it looks like that would be really helpful.
Thanks for the help
EDIT: this post by Im_Gumby from this thread: http://forum.xda-developers.com/showthread.php?t=1058649
worked perfectly for me.
Thanks
My Transformer informed me of an OTA update, which I tried to perform. It stuck on the boot screen and wouldn't go any further. I managed to wipe it and get it going again by switching off and pressing power and volume down, so I rebuilt it and it again wanted to do the update - with the same result.
I tried side-loading the update and again, it froze, so I downloaded and ran NVFLASHTF and now I can't get anything on the display whatsoever. All I can do is connect it to my PC and it makes the familiar connection sound and I can get to the SD card, but nothing else.
I need someone to show me what to do step-by-step as if I was completely stupid (which I obviously am!).
Please help if you can.
TIA
the nvflash sticky in the dev section includes a youtube video.
although the most likely reason your nvflash didn't work, is you extracted the files in the wrong place. make sure they are in the same place as the download.bat file.
Sent from my Transformer TF101 using Tapatalk
I have all the nvflash files in the same folder as extracted from the .zip file. I even have Prime 1.6 in the folder.
All I seem to be able to do is press the power button and either Up-vol or down-vol (or both) and the computer disconnects and immediately reconnects. When I run the download.bat file, it seems to run and complete the formatting and then download something and the dos box disappears at that stage. The tablet is showing the following...
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 027c100040a0b2d7
Click to expand...
Click to collapse
That is the only thing I can get to display - and, of course, it stays like this until I try to reboot again.
copy and paste what you get when you run the batch file into here...once it finishes
Pretty sure the tf should reboot on its own if done right.
Did you also check the md5sum of the downloaded files?
I followed these instructions..worked perfectly
http://tabletroms.com/forums/transf...ock-3-1-stock-3-2-recovery-roms.html#post9968
The Dos box disappears when it finishes so I can't paste it here and yes, I checked the files. In fact, I tried it on three different PCs (W7 64-bit, W7 32-bit and XP Pro 32-bit), all without success.
Have you plugged it straight to power and switch it on?
Yes - no difference.
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
maybe try a different usb port, I have 4 ports on the front of my pc but for some reason only ONE port works when i try to nvflash,also have problems if I use a hub or extend the cable in any way
Malandro2011 said:
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
Click to expand...
Click to collapse
Ok, the second option got me a little bit of info. Bootloader.bin is installing but it is telling me that the file 'recovery.img' is not found.
you can prevent the dos window from closing by starting the command via command line.
start > run > cmd (enter)
dir c:\where\nvflash\is\located (enter)
download.bat (enter)
OK, it's official - I'm an idiot!
I had downloaded the nvflash version of Prime 1.6 but hadn't extracted the files! I now have a working version of Prime 1.6 and am restoring the data as I type.
Thanks for all your help, especially the suggestion of running download from a dos prompt, which let me see where I was going wrong.
Excellent!
Glad it's all sorted
This is what worked for my phone....i'm not responsible from what happens to your phone your responsible for your own action...DO THIS AT YOUR OWN RISK! THIS METHOD doesn't require XP
OK so your phone is bricked because of the update by lg and your are stuck at the s/w screen...and The other method of flashing the KDZ file and program keeps freezing and not working even on XP ...if you haven't tried that method first you should its much easier and faster if you have and it's FAILED then hopefully this will help.
EASIEST FIX!!! This is for KDZ just encase you havn't tired this first my method is below....
Credit to bullseye69....THIS WORKs FOR WIN 7 ....so i guess you could try vista...but i'm not sure.
http://forum.xda-developers.com/showthread.php?t=1183168
READ FIRST!!!!
FOR BULLSeye69 his phone was working SO he used DIAG MODE BUTTT
IF your at s/w screen OR HAVE NO BASEBAND and NO BATTERY and NO IMEI...DO everything the same EXCEPT!!!! change DIAG to CS_emergency AND IT WILL WORK...give it a couple tries ....if it doesn't work first 2 - 3 times it's ok go to task manager and Right CLICK on the LGUPDATE tool in the process list and change set priority to HIGH and it should go through. HOPEFULLY THIS FIXS IT GOOD LUCK G2x owners
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF the Above method Does not work after like a million tries LOL there one more at the bottom ...Scroll down
~
~
~
~
~
~
~
~
OTHER METHOD : ONLY use this IF KDZ methods did not WORK (again at ur own risk)
hopefully this method will help you....(tried to be noob friendly as possible) READ THE WHOLE AT Thing LEAST ONCE
(PS download all those files they tell you to download because you will need them and i take no credit for those programs and files just this method on how i used them)
OK my phone condition was (2.2) s/w update screen....and was able to boot into cwm(clockwork recovery but not stock) using the ONE CLICK RECOVERY (internal sd flash)
So on stock 2.2 stuck on s/w update screen
my first mission is to just get past the s/w screen since i tried flashing a nandroid backup which i downloaded and it didn't work. (ps download the nandroid file "LG-P999-V10f.rar" credit to the dude who uploaded it )
Extract it using winrar or whatever program.
Now once you have the nandroid file you should see one md5 file and 6 .img files like recovery, system, etc....
so we gotta flash each one at a time....pain in the *** but if it works you'll thank me
OK so i was thinking like this kdz flash thing didn't work for me so i want to do everything manually ...alot of work but i have a 500$ paper weight...tough to figure the language but give it a little time.
LIST OF WHAT YOU NEED
One click recovery
Drivers installed
Nandroid file
so (assuming you have all the programs downloaded and installed) take all the img files (not the md5 one) and paste them into the nvflash folder of
the one click recovery folder.
Now open command prompt (type in search cmd)
we will used Command prompt next take battery out and press and hold up AND down volume buttons together and plug in your phone
(Apx driver should be recongized if drivers are installed)
Command i found to use (again credit to who made the command)
normally command promt (cmd) it starts with "c:\user\user"
so change this to where you saved the oneclick file...(easier to save the one click and other file right on c drive not into other folders)
For example my file is save in C:\oneclick\nvflash
SO this means i saved the file in c drive, and i need acess to "nvflash" folder inside "one click" since the nvflash program is in that
folder...
So change the location to where you want to access type in
cd C:\oneclick\nvflash (this is my file location obviously)
command language
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
NOW UNDERSTAND THE LINE SO YOU CAN FIGURED IT OUT EASIER...i'll try to be noob friendly as possible
"nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --"
this line for you noobs out there (not trying to insult lol) is just copy paste ok BUT
the second part ""download 8 .android_secure.img""" download is standard so that's also copy that
but SEE the 8 that number is the partion number ...bascially divsions on a harddrive so the 6 img (image)
file goes in their own number...so i'll post where .img file went in which partition but you may have to play
with the number to find ur phone's particular number...i'll explain futher
SO partiton number 8 is where my android_secure.img flashed and went throught without an error
so now i'll post the command for each img file that worked for me hopefully works for your G2x
(REMEMBER!!! after each command goes through the phone will turn on to the S/w screen , Once it says SUCCESSFUL (on CMD) unplug and plug back in hold the 2 volume keys)
for the android secure img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
for the cache img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 9 cache.img
for the boot img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 11 boot.img
for the system img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 7 system.img
for the data img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 15 data.img
~**NOTE IT IS BROUGHT TO MY ATTENTION THAT its possible that by COPYING PASTING ADDITIONAL SPACES MAY have been enter into the line so double check there are no extra spacing because then the command line becomes useless and doesn't work~****
NOW if they show an error like NV 120000 000 or something like partition error... then the NUmbers of your partition of where
these files go are different on your phone So it's not the END OF THE WORLD just play around with the numbers they are usually
very close so if number 15 doesn't work for the data.img then try 13, 14 or 16 they should be just one or two numbers away from
mine. (sometimes if says nvflash started and nothing happens you just have to unplug and plug again holding the 2 buttons)
Trial and error is how i obtained these numbers.
once all these files are sucessful goes through do a test but putting in your battery and going into recovery or just try booting (you not suppose to be plugged in for this)
it normally if it shows LG logo and goes to another LG logo with a LOading bar at the bottom wait for it may reboot,
IF it doesn't reboot it's OK because (after the normal boot) the S/w screen doesn't show up you have SUCCESS because the nandroid file SHOULD
work.
(IF your S/w screen has not gone away YOU Might HAVE TO wipe everything using CWM(Recovery holding power and down) and i mean everything format everything for every option that
(you get in CWM (recovery) go through what i did ....but THAT's only if you cannot get rid of the s/w screen )
(and then try again from the begining REMEMBER WIPING = LOSS in BASEBAND aka calling connectivity so through CWM make a backup of your file and save to your computer you may need later)
OK so we don't need cmd (command pompt) anymore you got your s/w screen to go away.
Now use NVflash and click the "one click recovery" button
(plug in the phone again (no battery) holding 2 volume buttons) and flash CWM to INTERNAL SD (not external)
IT's the first Button on the left (you should see 3 buttons to click on )
once it goes successful you can close the window and unplug.
pop in battery reboot holding POWER AND DOWN VOLUME KEY ...KEEP HOLDING till you see ANDROID RECOVERY (has like pictures of apps falling or something)
then the menu should pop open go to the mounts and storage and then all the way at the bottom (use volume keys to go up and down) mount usb storage option
and (make sure usb plugged in now) hit power button to open STAYY!! in that menu to acess the Storage on the phone...don't exit or hit unmount
nothing will happen if you do by accient exit...just it's easier to explain this way lol
now you should see on the PC (in my computer or automatically open the drive storage for your phone) in there you should see your folders and one of them is clockworkmod
in that there should a folder called "backup" if not make one, all small letters "backup" in there copy the whole LG-p999-v10f file you extracted into the backup folder.
now on the phone (once it transfered the file) hit unmount or hit go back using power button and go back to the first menu
above the mounts and storage option there should be the "backup and restore" option ...open that and hit the restore option and
you should see the LG-p999-v10 file there and hit power on that and go down to yes option and hit open and let it run should take roughly 5 mins.
let it go till it comes to the menu again... now hit reboot system...phone should turn off...if it doesn't turn on within 2-3 mins you can turn it on
your self and android should up and running YAY!!!!
(This is for only people who did a full format when they couldn't get rid of the S/W screen)
Now i have had some battery/signal issues....Thats because i did the full wipe of everything some people may or may not have this same problem hopefully someone can post a radio file zip or something ....cyogenmod is another option but i haven't tested it yet
will post result of the battery issue later
EDIT:I have put cyanogen mod (credit to cyanogen mod guy lol) on and seemed to fix the battery reading issue.
EDIT:
IF NO BASEBAND AND NO BATTERY TRY METHOD 1 again at top of the page
KDZ in CS_emergency mode ...and if on windows 7 setup the KDz as in the link above (bulleye69) then proceed to flashing it in CS_emergency mode
HOPEFULLY THIS HELPS ALL THE REST G2x semi-bricked owners....DON"T FORGET TO HIT THE THANKS BUTTON!!!!!
kosh2thamax said:
This is what worked for my phone....i'm not responsible from what happens to your phone your responsible for your own action...DO THIS AT YOUR OWN RISK! THIS METHOD doesn't require XP
OK so your phone is bricked because of the update by lg and your are stuck at the s/w screen...and The other method of flashing the KDZ file and program keeps freezing and not working even on XP ...if you haven't tried that method first you should its much easier and faster if you have and it's FAILED then hopefully this will help.
EASIEST FIX!!!
Credit to bullseye69....THIS WORKs FOR WIN 7 ....so i guess you could try vista...but i'm not sure.
http://forum.xda-developers.com/showthread.php?t=1183168
READ FIRST!!!!
FOR BULLSeye69 his phone was working SO he used DIAG MODE BUTTT
IF your at s/w screen OR HAVE NO BASEBAND and NO BATTERY and NO IMEI...DO everything the same EXCEPT!!!! change DIAG to CS_emergency AND IT WILL WORK...give it a couple tries ....if it doesn't work first 2 - 3 times it's ok go to task manager and Right CLICK on the LGUPDATE tool in the process list and change set priority to HIGH and it should go through. HOPEFULLY THIS FIXS IT GOOD LUCK G2x owners
IF the Above method Does not work after like a million tries LOL there one more at the bottom ...Scroll down
OTHER METHOD : ONLY use this IF KDZ methods did not WORK (again at ur own risk)
hopefully this method will help you....(tried to be noob friendly as possible) READ THE WHOLE AT Thing LEAST ONCE
(PS download all those files they tell you to download because you will need them and i take no credit for those programs and files just this method on how i used them)
OK my phone condition was (2.2) s/w update screen....and was able to boot into cwm(clockwork recovery but not stock) using the ONE CLICK RECOVERY (internal sd flash)
So on stock 2.2 stuck on s/w update screen
my first mission is to just get past the s/w screen since i tried flashing a nandroid backup which i downloaded and it didn't work. (ps download the nandroid file "LG-P999-V10f.rar" credit to the dude who uploaded it )
Extract it using winrar or whatever program.
Now once you have the nandroid file you should see one md5 file and 6 .img files like recovery, system, etc....
so we gotta flash each one at a time....pain in the *** but if it works you'll thank me
OK so i was thinking like this kdz flash thing didn't work for me so i want to do everything manually ...alot of work but i have a 500$ paper weight...tough to figure the language but give it a little time.
LIST OF WHAT YOU NEED
One click recovery
Drivers installed
Nandroid file
so (assuming you have all the programs downloaded and installed) take all the img files (not the md5 one) and paste them into the nvflash folder of
the one click recovery folder.
Now open command prompt (type in search cmd)
we will used Command prompt next take battery out and press and hold up AND down volume buttons together and plug in your phone
(Apx driver should be recongized if drivers are installed)
Command i found to use (again credit to who made the command)
normally command promt (cmd) it starts with "c:\user\user"
so change this to where you saved the oneclick file...(easier to save the one click and other file right on c drive not into other folders)
For example my file is save in C:\oneclick\nvflash
SO this means i saved the file in c drive, and i need acess to "nvflash" folder inside "one click" since the nvflash program is in that
folder...
So change the location to where you want to access type in
cd C:\oneclick\nvflash (this is my file location obviously)
command language
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
NOW UNDERSTAND THE LINE SO YOU CAN FIGURED IT OUT EASIER...i'll try to be noob friendly as possible
"nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --"
this line for you noobs out there (not trying to insult lol) is just copy paste ok BUT
the second part ""download 8 .android_secure.img""" download is standard so that's also copy that
but SEE the 8 that number is the partion number ...bascially divsions on a harddrive so the 6 img (image)
file goes in their own number...so i'll post where .img file went in which partition but you may have to play
with the number to find ur phone's particular number...i'll explain futher
SO partiton number 8 is where my android_secure.img flashed and went throught without an error
so now i'll post the command for each img file that worked for me hopefully works for your G2x
(REMEMBER!!! after each command goes through the phone will turn on to the S/w screen , Once it says SUCCESSFUL (on CMD) unplug and plug back in hold the 2 volume keys)
for the android secure img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
for the cache img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 9 cache.img
for the boot img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 11 boot.img
for the system img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 7 system.img
for the data img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 15 data.img
NOW if they show an error like NV 120000 000 or something like partition error... then the NUmbers of your partition of where
these files go are different on your phone So it's not the END OF THE WORLD just play around with the numbers they are usually
very close so if number 15 doesn't work for the data.img then try 13, 14 or 16 they should be just one or two numbers away from
mine. (sometimes if says nvflash started and nothing happens you just have to unplug and plug again holding the 2 buttons)
Trial and error is how i obtained these numbers.
once all these files are sucessful goes through do a test but putting in your battery and going into recovery or just try booting (you not suppose to be plugged in for this)
it normally if it shows LG logo and goes to another LG logo with a LOading bar at the bottom wait for it may reboot,
IF it doesn't reboot it's OK because (after the normal boot) the S/w screen doesn't show up you have SUCCESS because the nandroid file SHOULD
work.
(IF your S/w screen has not gone away YOU Might HAVE TO wipe everything using CWM(Recovery holding power and down) and i mean everything format everything for every option that
(you get in CWM (recovery) go through what i did ....but THAT's only if you cannot get rid of the s/w screen )
(and then try again from the begining REMEMBER WIPING = LOSS in BASEBAND aka calling connectivity so through CWM make a backup of your file and save to your computer you may need later)
OK so we don't need cmd (command pompt) anymore you got your s/w screen to go away.
Now use NVflash and click the "one click recovery" button
(plug in the phone again (no battery) holding 2 volume buttons) and flash CWM to INTERNAL SD (not external)
IT's the first Button on the left (you should see 3 buttons to click on )
once it goes successful you can close the window and unplug.
pop in battery reboot holding POWER AND DOWN VOLUME KEY ...KEEP HOLDING till you see ANDROID RECOVERY (has like pictures of apps falling or something)
then the menu should pop open go to the mounts and storage and then all the way at the bottom (use volume keys to go up and down) mount usb storage option
and (make sure usb plugged in now) hit power button to open STAYY!! in that menu to acess the Storage on the phone...don't exit or hit unmount
nothing will happen if you do by accient exit...just it's easier to explain this way lol
now you should see on the PC (in my computer or automatically open the drive storage for your phone) in there you should see your folders and one of them is clockworkmod
in that there should a folder called "backup" if not make one, all small letters "backup" in there copy the whole LG-p999-v10f file you extracted into the backup folder.
now on the phone (once it transfered the file) hit unmount or hit go back using power button and go back to the first menu
above the mounts and storage option there should be the "backup and restore" option ...open that and hit the restore option and
you should see the LG-p999-v10 file there and hit power on that and go down to yes option and hit open and let it run should take roughly 5 mins.
let it go till it comes to the menu again... now hit reboot system...phone should turn off...if it doesn't turn on within 2-3 mins you can turn it on
your self and android should up and running YAY!!!!
Now i have had some battery/signal issues....Thats because i did the full wipe of everything some people may or may not have this same problem hopefully someone can post a radio file zip or something ....cyogenmod is another option but i haven't tested it yet
will post result of the battery issue later
EDIT:I have put cyanogen mod (credit to cyanogen mod guy lol) on and seemed to fix the battery reading issue.
EDIT:
IF NO BASEBAND AND NO BATTERY TRY METHOD 1 again at top of the page
HOPEFULLY THIS HELPS ALL THE REST G2x semi-bricked owners....
Click to expand...
Click to collapse
Thanks. it worked!!!!!!!!!!!!!!!!!!!!!!!!!!!
@ rapswiller no problem glad it worked
you my friend, are quite awesome indeed, this is the only thing that fixed my phone after nothing else did, so thanks... like really... you are badass for knowing this stuff
+1 awesomeness
saaif88 said:
you my friend, are quite awesome indeed, this is the only thing that fixed my phone after nothing else did, so thanks... like really... you are badass for knowing this stuff
+1 awesomeness
Click to expand...
Click to collapse
Hey no problem.... took me days to figure this out so i thought people can save some time and give this a shot if all else fails LOL Glad it worked and fixed your phone
I'm about try this method as i bricked my g2x after attempting to put cyanogenmod on it.. i got everything ready except nandoid. where can i find this file?
-done my phones working again im crying right now
omg omg omg i will love you forever kosh2thamax I can't be any happier right now! God bless you.
dokjon said:
omg omg omg i will love you forever kosh2thamax I can't be any happier right now! God bless you.
Click to expand...
Click to collapse
LOL thanks for the love ...happy it worked
I tried the command method cause KDZ keep force closing halfway and after that i flashed clockworkmod. When i restarted it still has the stock recovery, i got rid of the s/w but the problem now is that it gets stuck on lg logo with blue line and the menu buttons light up. I tried going into apx mode and s/w but the phone doesn't, it boots to the lg logo and the the blue lines.
Is there's any way to fix this?
Check the rom for recovery thread in Dev section, it will nvflash your phone to 2.3.3 gb rom. It will basically fix any brick and is our saving grace, huge props to iluha for creating it!
Sent from my LG-P999 using xda premium
Use --resume
it keeps using the running bootloader on your phone....
lilizblack said:
I tried the command method cause KDZ keep force closing halfway and after that i flashed clockworkmod. When i restarted it still has the stock recovery, i got rid of the s/w but the problem now is that it gets stuck on lg logo with blue line and the menu buttons light up. I tried going into apx mode and s/w but the phone doesn't, it boots to the lg logo and the the blue lines.
Is there's any way to fix this?
Click to expand...
Click to collapse
ok so you got passed the S/w screen at boot from my understanding and assuming that you manually flashed each file into it's partition...so now you used NVflash to flash and get clockworkmod recovery ? ok what happens when you pressed and held both the power and volume down what do see rather?
bigmixxx said:
it keeps using the running bootloader on your phone....
Click to expand...
Click to collapse
Ummm when does it say this exactly? like when manually flashing?
What did I do wrong? I tried the kdz method but it never worked after many, many, tries. My phone was stuck on the S/W Upgrade screen so I have to use the 2nd method.
I pressed the volume up/down buttons and put the usb cable in, waited for the driver to load (NVIDIA USB Boot-recovery driver for Mobile devices), let go of the two buttons, and I ran the first line "nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--" (without the quotes) and the cmd window stuck at "Nvflash started" but didn't budge and the S/W Upgrade screen didn't appear so I pulled out the USB cable and in the command window it stated "uid read failed"
Here's the cmd window info:
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>nvflash --bct 1108_Hynix_5
12MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--
Nvflash started
uid read failed
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
Now it doesn't boot at all, no S/W Upgrade appears, nada. *Update I got the S/W Upgrade screen back after reinstalling CWM.
Core Memory said:
What did I do wrong? I tried the kdz method but it never worked after many, many, tries. My phone was stuck on the S/W Upgrade screen so I have to use the 2nd method.
I pressed the volume up/down buttons and put the usb cable in, waited for the driver to load (NVIDIA USB Boot-recovery driver for Mobile devices), let go of the two buttons, and I ran the first line "nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--" (without the quotes) and the cmd window stuck at "Nvflash started" but didn't budge and the S/W Upgrade screen didn't appear so I pulled out the USB cable and in the command window it stated "uid read failed"
Here's the cmd window info:
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>nvflash --bct 1108_Hynix_5
12MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--
Nvflash started
uid read failed
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
Now it doesn't boot at all, no S/W Upgrade appears, nada. *Update I got the S/W Upgrade screen back after reinstalling CWM.
Click to expand...
Click to collapse
Ummmm usually the if it says that it started and nothing happens you just do it again (unplug it & close program (battery is not in) press up/down volume buttons plug it in ..then thingy pops up as verified let go...and open program and try) now I couldn't help but notice your file name...but just make sure your phone is LG G2x not LG optimus 2x.... right?
d12unk13astard said:
Check the rom for recovery thread in Dev section, it will nvflash your phone to 2.3.3 gb rom. It will basically fix any brick and is our saving grace, huge props to iluha for creating it!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
can u post the link plz
Awesome...
I registered at xda just to post that this is the best solution ever. Thanks a lot OP!
I'm still stuck at a boot loop but I'll figure it out from there!
Gryncc said:
can u post the link plz
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium
NP hopefully the manual single file flashing with the backup restore should get you out of the loop
this did not work still no baseband and no signal plz help plz
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
strakajagr said:
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
Click to expand...
Click to collapse
Confirm that your SBF file is not corrupt. Try downloading it from a different source and check hashes
I have tried 3 sbf's thus far. 2 .330's (from different locations) and 1 .290. The error message is always the same. I'm not sure if it matters, but I have clockword mod installed on my phone as well as Fission.
I'm not sure if having Mods and roms who affect your phone. But just incase have you tried clearing the cache,data,partition from the recovery menu?
I have... again, no luck. It just appears that rsd lite flat out can't communicate with my phone even though it definitely SEES the phone when it's connected. For the life of me I can't figure out why. I found ONE thread on another site where someone posted the same error and reported the same problem. Someone linked him to a boiler plate SBF installation instruction page, which obviously I have tried unsuccessfully several times. It's killing me knowing that there is so much more performance in my phone that I just can't get. My original Droid outperformed this POS. UGH
That certainly is frustrating. The only thing I can think of is trying a different USB cable that is shielded or otherwise, or another computer/OS maybe it's causing a error. If you've already tried that with no results, all I can say is sorry man and keep trying.
I was just reading this thread: http://forum.xda-developers.com/showthread.php?t=1236781 where the final poster said there are a couple of bad .330 sbfs circulating the web, and that the best way around it was to try to sbf a .29 and then ipdate from there.
BTW, op, I agree. My droid one can kick my D2G's ass blindfolded.
Good luck,
Dan
Hi mate, i have had this issue before, please try this as this is the way around my issue =
follow this link and download the rar file (http://www.multiupload.com/FIW8B8TJ7I), flash this file (using rdslite 4.9 , Make sure it is rds lite 4.9!) = http://www.mediafire.com/file/9c6u55c26e1h9y1/RSD Lite 4.9.rar
Being on clock work etc... wont make a differnce but to put your phone in boot loader mode, please do it this way and not the other loaders way.
turn off the phone, press and hold the up and down volume buttons together (make sure you are pressing and holding them down together keep them hold down and dont let go) press the power button while still holding the volume buttons and wait till bootloader comes and then let go, onces it says it in there
Launch RSDLite (make sure device appears in window)
Select SBF (doesnt matter where the file is, just point it to the right place)
click start.
Once it gets to 100% , pull it out and restart the phone (it should reboot it normally but I find it doesn't always do it) so either unplug and let it reboot or pull the battery out and reboot, fingers crossed it will boot in to stock and then you can upgrade from there.
"No such file or directory" help!
Hello,
I am having issues following these instructions as a part of the instructions from
droidforums' root-droid-1-regardless-os-version
after running this:
chmod +x sbf_flash
Then running
sudo ./sbf_flash update.zip
I get the following:
[email protected] ~ $ sudo ./sbf_flash update.zip
[sudo] password for gjohnhazel:
SBF FLASH 1.24 (mbm)
opticaldelusion
update.zip: No such file or directory
Usage: sbf_flash <filename>
My Droid is plugged in, with update.zip in the root of the SD Card and Bootloader 2C.7C with Transfer Mode set to USB.
Can anyone help?
Note: Where it says "opticaldelusion" it's actually the link, but I'm not allowed to have hyperlinks in this message.
sbf_flash is used to load an SBF image (which should be stored on your PC for sbf_flash to access it) into your phone.
It's not a tool to flash OTA/normal update packages.
To flash a normal update.zip you need to use either stock (for stock firmware updates) or ClockworkMod Recovery (for custom ROMs).