Hi i recently tried to install a recovery from rom manager, but it installed one for g2x so then nothing could mount in recovery and when i tried to flash, something failed and now my device is bricked. I then found this guide http://forum.xda-developers.com/showthread.php?t=1229407&page=5 which i was able to recognise my device as a NVIDIA usb boot recovery drive but every time i press flash-recovery.bat and chose the partition, it says nvflash is not recognised as a command.... and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
You need to flash an entire rom with nvflash, because you messed up the partition table (p990 and p999 have different partitions). With this guide you'll flash only the recovery...
After that you need to flash a proper baseband
Have you a g2x or an o2x?
iliatay said:
and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
Click to expand...
Click to collapse
I have the same problem as him. Anyhelp?
I think you may try to reflash your device with the original firmware (KDZ file) which you can download from LG. Whole process is described in here:
http://forum.xda-developers.com/showpost.php?p=18946763
Please note that recently LG has changed something in their tools and now you have to "fool" them to do what you want them to. Please see this thread for details:
http://forum.xda-developers.com/showthread.php?t=1473781
Hope this will help you.
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
langhaardack said:
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
Click to expand...
Click to collapse
u can try this http://forum.xda-developers.com/showthread.php?t=1498021
i have tryed to ease the things to understand.
i had the same problem.
i downloaded these files:
http://uploaded.to/file/dkq74mlh
http://uploaded.to/file/2azotnvs
unpacked the files (important is that you put all files from the driver zip in one folder)
click volume + and volume - while connecting to your computer and it will recognize it
You go to device manager, right click on the apx ,update driversoftware, search on the computer for driver software, choose the folder you've put the driver files
then you can start flash.bat
Related
Hi guys,
I tried to update my 2x from 20e to ICS today but it was unsuccessful (http://forum.xda-developers.com/showthread.php?t=1959545). I tried to do recovery from the CMW as recommended but it fails. Error/ mounting system. When I reboot its stuck on LG logo. I have tried do recovery using NVflash but not successful either (http://forum.xda-developers.com/showthread.php?t=1975274&page=5).
My previous setting: v20e. CWM 5.0.2.7.
Its been months since my last update for the 20e. I am not sure I am on the right driver. CMW version etc. and I have just use win7 from vista last two months. I am not sure if that affect too.
Any help are much appreciated. Thanks in advance.
Use nvflash to flash cm10 (old BL) and then recover nandoid
Sent from LG 2X using Tapatalk 3 Beta
Rayman96 said:
Use nvflash to flash cm10 (old BL) and then recover nandoid
Sent from LG 2X using Tapatalk 3 Beta
Click to expand...
Click to collapse
I have downloaded Homero2 nvflash. tried to follow the instruction. When I open the nvflash I dissapear as soon its open. Any step missing?
It should just open right? Sorry for my noob question, what is nandroid? I am on win7
ary820 said:
When I open the nvflash I dissapear as soon its open. Any step missing?
It should just open right?
Click to expand...
Click to collapse
Do you click on the batch file, or on the nvflash .exe file? You should use the batch file, not the .exe. Also, open command prompt first, and run the batch file from there -- you will see all the errors and other messages. (I should probably put this in my signature, as I already mentioned it probably half a dozen times in different topics...)
what is nandroid?
Click to expand...
Click to collapse
It's the backup that you create in CWM.
ary820 said:
Hi guys,
I tried to update my 2x from 20e to ICS today but it was unsuccessful (http://forum.xda-developers.com/showthread.php?t=1959545). I tried to do recovery from the CMW as recommended but it fails. Error/ mounting system. When I reboot its stuck on LG logo. I have tried do recovery using NVflash but not successful either (http://forum.xda-developers.com/showthread.php?t=1975274&page=5).
My previous setting: v20e. CWM 5.0.2.7.
Its been months since my last update for the 20e. I am not sure I am on the right driver. CMW version etc. and I have just use win7 from vista last two months. I am not sure if that affect too.
Any help are much appreciated. Thanks in advance.
Click to expand...
Click to collapse
reflash or flash it using nvflash!!
kt-Froggy said:
Do you click on the batch file, or on the nvflash .exe file? You should use the batch file, not the .exe. Also, open command prompt first, and run the batch file from there -- you will see all the errors and other messages. (I should probably put this in my signature, as I already mentioned it probably half a dozen times in different topics...)
It's the backup that you create in CWM.
Click to expand...
Click to collapse
Thanks for the feedback..how do I run batch file from command prompt?
Isit goto window-->cmd-->type: c:\nvflash\nvflash? I have created the "nvflash: folder in C.
Back to the source, I tried to follow as the instruction:
-Download the attached file and unzip it. The pack includes the APX driver (folder driver)
1.- Remove the battery to the phone.
2.- Press and hold Vol- and Vol+ and without releasing the 2 keys connect the USB cable to the PC
3.- Go to the NVFlash folder and run:
3a.- Windows should detect a new device APK, cancel the installation and install the driver which includes the ROM.
3b.- On Linux not ago missing driver.
4.- Browse to the folder where you unzipped the RAR and typing CMD in the breadcrumb bar, Linux opens the console.
- Type:
Windows
Code:
flash.bat
When I extract the file, the driver folder amd64 folder, i386 folder and nvidiausb file. I didn't see APX folder/file.
I am not clear abot step #3 open nvflash & run: (I am not sure what to run)
# How to go about in step 4? This is what I have tried. Go to the folder, type cmd, then type "flash.bat"
I see this:
c:\nvflasf>echo "flashendo lg optimus 2x" flashendo lg optimus 2x......
c:\nvflasf>nvflash.exe --bct star.bct --bct -- configfile android_fastboot_emm
c_ful.cfg - create -- bl.fastboot. bin -- go
Nvflash started
rcm version 0x20001
command send failed (usb write failed)
c:nvflash\ scho "listo!" listo!
Need help, I am sure where I do wrong.
Update: Somehow I made the recovery, same procedure as above. (Big thanks to Homero2 for the tools)
I wanna ask some question:
1-I have redo the ICS update (ICS extended by TonyP and Harsh). I encounter same problem as before (error 7). Any tips where might go wrong or what I should check before flashing.
2-Where I can flash from here (from Homero2 ROM)? GB only or I can flash to ICS or JB?
3-I try update the ROM manager via google play..but I think its only 5.2.0.7 version. Does higher version (v6) for ICS and do I need to do recovery before flashing via ROM manager?
Thanks in advance.
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.
ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!
Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install
Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.
Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you
Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg
timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.
What am I suppose to do about it saying wiating for device, its not detecting it
timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.
Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result
Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
fran1563 said:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Click to expand...
Click to collapse
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
fran1563 said:
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Click to expand...
Click to collapse
Just say what you do not understand, I can explain
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
Mis012 said:
Just say what you do not understand, I can explain
Click to expand...
Click to collapse
Thank you mate, I'm going to try. I'll write you wherever going to happens. I aprecciate!
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
christelle868 said:
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
Click to expand...
Click to collapse
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Mis012 said:
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Click to expand...
Click to collapse
i think he got lost on your tutorial XD
fastboot starting
Please, Please advice ..
And I'm one of those tablets which displays a message starting fastboot 1,2,3. I tried almost everything. Well at least I think that everything is okay or if vv. Please advice how to try it changed. Thank you in advance for answers
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download either of the firmware from here
Download the support files (Firehose/rawprogram0.xml/patch0.xml) here
Extract the firmware and support files to the same folder so you can easily access them like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash individual partitions you can edit your rawprogram0.xml to only include the ones you want. (patch0.xml stays the same) I have linked below 2 examples, one of them flashes just a boot.img and one that just flashes the recovery.img. But you aren't limited to those.
Recovery
Boot
Mine just in case
Awesome, thanks for this post! it will really help us in upcoming projects!
Managed to revive my phone using the B12 files but it crashes after completing system.img, I think the problem is userdata.img, my phone boots but I lost the imei and I don't know how to get it back, I'm still trying.
ZTE 971 not recognized by either QPST or QFIL
Thanks for all the detailed instructions. But my ZTE 971 is not visible to either qpst or qfil eventhough the phone shows in windows 8.1. In the Developer Options menu, I noticed Select USB Configuration, RNDIS (USB ethernet) option cannot be enabled. I wonder if this has anything to do with it. OEM unlocking, USB debbugging are already selected. Any suggestions, please? Thanks.
ps. I live in Turkey. I got this phone last year from AT&T and have unlocked the sim.
My PC is not detecting my ZTE MAVEN 3
I have installed all drives but still facing the issue. I am using it on Windows 10.
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Mega says that link for the driver is invalid, but the driver is included in your QPST download anyway.
000Nick said:
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Click to expand...
Click to collapse
solucionaste hermano
Mod edit:
you solved brother
Click to expand...
Click to collapse
it says qhsusb_bulk when I connect the the software is not working in the mobile and it is stuck at bootloader screen but I used the press both buttons to go to edl mode method and it said in the device manager a device connected with name : qhsusb_bulk
help pls
Hello All.
I am not able to get the following files
rawprogram.xml and patch.xml for LG G8xPlease help me to get this files ASAP as i have hard bricked the mobile, all partitions deleted