Related
OK, to be fair I don't know whether to blame LG or Microsoft, but in the middle of upgrading my G2X it looks as if the crappy Windows drivers quit talking to the phone.
The LG software instructed me to do a battery pull and try again, but the result is the phone is now stuck in "S/W Upgrade" display. It won't not respond to the Windows update program. Reinstalling drivers does not help.
It won't boot Android. It's useless.
Rebooting with the sound buttons depressed gives me a black screen, no recovery program.
I have the Android SDK on my Linux laptop, but it doesn't find any USB devices, regardless of whether I do a straight boot or attempt recovery mode.
I have a Linux version of nvflash, which also can't find the device, so http://forum.xda-developers.com/showthread.php?t=1610562 is no help.
What next?
If you have a Windows computer accessible:
http://forum.xda-developers.com/showthread.php?t=1180331
404 land
Sadly most of the links in that thread point to 404s, so I am not able to find the Windows one-click CWM flasher, but I found this
http://search.4shared.com/postDownload/9h4mmcSp/nvflash-cwm_recovery-5027.html
which is a Linux nvflash binary, script, and CWM package. With enough fiddling around I managed to get Linux to detect the device and nvflash to install Clockwork, so I'm at least that far.
Now to figure out how to get rid of that upgrade screen ....
You ran into the exact same thing I ran into about 6 months, literally to a "T".
The link posted above by another member is what I followed, and it fixed the problem for me.
I hope you are able to find the various non-dead files/links!
Good Luck!
Scott
Here is the One-Click NVFlash for windows:
[RECOVERY][APP] 4-28:One-Click NvFlasher ClockWorkMod Touch 5.8.1.3/5.0.2.0/4.0.1.5
Also the KDZ flasher is probably the only way you're going to get the update finished, and you'll have to do that on XP.
XP
I have an XP laptop, but the KDZ flasher crashes when I try checking the phone configuration, and I have not been able to locate a KDZ file for the GX2. Pretty much everything in that thread resolves to a removed file, or a dead domain.
Oh, here's the V21y kdz.
You shouldn't need to check phone configuration, just open the kdz flasher,select the kdz file, and hit go.
EDIT: Yup, from the other thread:
speedsk8x said:
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)
Click to expand...
Click to collapse
Partial success
I had partial success with these instructions
http://forum.xda-developers.com/showthread.php?t=1248644
... except that the device drivers were not Win7 compatible and I had to chase down the correct drivers by Googling for Nvidia APX drivers. Once that was done, I was able to nvflash back to a stock system and get out of the LG "S/W Update" bootloader problem.
However, the phone radio isn't working. The cited thread recommends updating using either the KZ loader or the LG Update tool after flashing, so I guess that's my next stop.
Decoding the instructions:
Removing the battery, holding down BOTH volume controls, and plugging in USB puts the phone in to "APX" mode. It will show up as an unknown device in Windows, which allows you to install the device driver. After that the nvflash utility can reflash all the phone's memory.
try this
This happend to me a month ago and took me till 4am to solve...
disclaimer this worked for me but your mileage may vary
First update your lg drivers here
dropbox.com/s/8hibwel69plml4w/LG%20_USB%20_Drivers_All_4.9.7.zip
The only way I found to get it out of the s/w update mode was to use this custom nv flasher that restores it to stock V21E over apx mode
dropbox.com/s/g2eli2mjapfhd0k/G2X_V21E_00_NVFlash.zip
it also includes the nvidia apx drivers
you get to apx mode by taking the battery out and holding both volume buttons down while pluging the usb cable in ... you can let go of the buttons after you see the update screen
after that your phone should boot up normal...skip syncing google account... now with your drivers updated try the lg update tool again... to me the lg tool is the most straight forward way to get the updated baseband... after this works you'll be on stock V21Y with new baseband Mar 11 2012...
now for recovery and backup use this and pick CWM 5.0.2.0
dropbox.com/s/odypked2aqha11i/One-Click-G2x-recovery-flasher-04-28-12.rar
after you have that done you can then flash this stock rooted V21Y via copy it to your sd card
dropbox.com/s/4db1h60uj7gmvpq/p999_2.3.4_v21y_4142012.zip
Thanks...
Thanks for the links! I'll try again with those versions and see if I can get the LG updater (which caused all this trouble in the first place) to work properly. I am still getting failures when it is connecting with the phone.
While I do have nvflash working (on the win7 laptop) and am able to flash CWM and install ROMs, the phone still doesn't seem to know it's a phone. The T-mobile wifi calling app says the SIM is bad.
I flashed Eaglesblood ICS, which was easy and looks like it's a great ROM, but the phone still doesn't work.
Check the "Rom for Recovery" thread in the Dev Section. Follow the instructions. It should get you up and running in no time.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Massive fail...
delete please, I post in wrong thread.
I have read all types of forums to Reboot Bootloader. Yeah, I know stuck at the beginning, not a good sign.Any way I went to Developer.android and got SDK. Followed various suggestions and have it on machine. However the windows 7 won't recognize device. I downloaded Motorola Device Manager for the drivers (I beleive this may be the issue) and it found no updates. I have debugged checked on Xoom, but jellybean icon shows up intermittently. When I type in CMD prompt to adb reboot bootloader, it doesn't recognize the device.
Other CMD commands suggested during instruction video worked verifying I had ADB installed coirrectly. I checked the device in control panel and it is unidentfied.Device properties has this error" Windows has stopped this device because it has reported problems. (Code 43)"
Please, can someone assist. I think that I need the drivers, but the motorola Device manager is the only tool I can find and I dont think it has the drivers, I could be wrong, but this is what I'm guessing.
Ok. I found online that the new USB 3.0 has issues with this process. I plugged into a 2.0 USB and I'm in business. I've gone through unlocking. Now I can't locate the Universal Xoom Root Zip. All tutorial links that I could find go to a link that no longer has the file. can someone point me in the right direction or send me a link to the file- Thanks for the help
Ok status update. I was able to find the file and have successfully Rooted. The question, now is I restarted and I have an Green Android robot on my screen with Tiamat engraved on front stomach area. I believe I was in recovery last. IS the Xoom doing anything in the background. I don't want to interrupt something if it is running. I have downloaded BiGPART and Omni 4.4 components but I seem to be stuck
Wow... Not one response. I was able to figure it out and now am the owner of 4.4
I have a L925 (RM-910, Code 059S9S8), it stuck while upgrading to win 10 TP. I used WPRT to revert to win 8.1. Initially, WPRT detected the device and tried emergency driver or something which failed and since then my phone is not detected by WPRT, no response if the power and vol- buttons are held, but windows key flashes randomly.
I tried the un-bricking method mentioned in the original post, at the point where they suggest to uninstall the QHSUSB driver, i uninstalled it and continued the procedure until FLASHING THE BOOTLOADER step. It gave me the subject error and code, i retried several times and found two reasons suggested by people for the said error:
1. Incorrect drivers
2. Incorrect files (.hex)
When i retried the step of uninstalling the QHSUSB drivers, i found out that my system doesn't have these installed nor is my phone detected as QHSUSB device.
I have been trying to find if any solution for the above mentioned error has been stated anywhere but i couldn't find one. I have been trying to flash the bootloader (i am an accountant by profession and i don't even know the ABC of programming and this stuff but i learned quite much when WPRT bricked my L925), the subject error appears every time. I have made my .bin file, my own .hex file, .mbn file all for my model but i am still unable to figure out the real issue.
In the original post of un-bricking L925 without JTAG, it was mentioned that the subject error means that wrong drivers are installed. I am using windows 10 on my laptop, and the drivers available for win 7 & 8 are older than the ones on win 10 and when i try to install the drivers downloaded from the link provided in the original post, i got a prompt from win 10 that NEWER VERSION ALREADY INSTALLED.
I kept searching the forums and found someone mentioned that the subject error also appears due to incorrect .hex files and the also mentioned a way to correct the download-available .hex for my model, so i corrected the downloaded ones and even double checked it with my .bin files and i am now sure that i am using the correct files.
So,
1. My drivers are updated versions of those suggested in the post.
2. My .hex file matches with my .bin file (.bin was created using cmd prmpt and from my model)
I cannot find anyother solution or reason for the error which appears.
Any help or guidance from you guys will be really appreciated.
P.S. After failure on windows 10, I have also tried the whole procedure on win 8.1 and the results were no different.
Hoping to get some guidance or help
Yasir H. Qureshi
i wanted to post the above prob to the relevant thread so that the people who are already solving or facing such a problem could help me out but i have to post 10 posts/replies before i can go there so this is my first reply . i hope moderators will understand my desperation.
this is my reply number two.
this is my third reply.
fourth one.
5th.
6th
7th
8th
10 lol
y m still unable to even post it to the relevant forum? :|
LG OPTIMUS ZONE 3 - UNBRICKING GUIDE AND 5.1.1 FACTORY FIRMWARE
This guide has two main objectives: (1) for those with a bricked device who want to restore to the latest factory firmware image; and (2) those who need .kdz Stock 5.1.1 Factory Firmware files.
1. UNBRICKING THE LGVS425PP:
The Verizon LGVS425PP comes, pre-installed on the device, a Windows compatible LG Software Upgrade and Repair utility. When connected via micro USB cable, your device will connect to your PC as an installer and, if you look in your PC directory, you will see an installation directory for the Verizon LG utility. Inside that directory is an .exe file that will install the upgrade/repair utility on your PC. When launched, the utility will auto detect your device, determine if a firmware update is available, and give you an option to repair your device. The repair option will backup your existing userdata (depending on the level of damage to the firmware), download the most recent firmware build for your device, and flash your device to complete stock condition.
Of course, there are those who bricked their devices before being able to install the Verizon LG Upgrade/Repair utility on their PCs. And this utility appears difficult to locate for download on the internet. So, below is a download link for the utility:
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2elpGQ3JEbzF4Q0E?usp=sharing
The Verizon LG utility should install the correct USB mobile drivers on your PC. But just in case any driver issues arise, download and install the following LG United Mobile Driver package:
DOWNLOAD LINK
https://drive.google.com/file/d/0B1Sfod4HWfk2RHY2c29mTWg1Rkk/view?usp=sharing
Once the utility is launched, make sure your PC is connected to the internet, put your device in download mode by holding +Volume while connecting your micro USB cable for your PC connection. The utility will then detect your device. Select the REPAIR option and follow the on-screen instructions.
2. STOCK 5.1.1 FACTORY FIRMWARE
The following link is for four software versions of stock 5.1.1 Factory Firmware .kdz files for the Optimus Zone 3: VS425PP2, VS425PP4, VS425PP7 & VS425PP8. Also in the link is the LG United Mobile Driver, the LG-UP flashing tool, and the LG-UP .DLL for the VS425PP. Use these tools at your own risk. I am not responsible for bricked or inoperable devices. I want to thank each and every member in this thread who has tested and reported their findings and issues. That narrows it down greatly. And thanks guys for your patience.
As to rooting the Zone 3, several recent advancements have been achieved and full root access is now possible. Thanks to @Astr4y4L, a comprehensive root package is available for download. http://astrayalslanding.dynu.net:88/Android_Development/ Click on this link and scroll down the the bottom and click the projects link. His package includes precise instructions and alI the files you will need to root this phone. I am currently drafting a concise tutorial for downgrading this phone. Instructions for downgrading can be found within this thread, albeit somewhat scattered. I will update the OP accordingly as further progress is made. Guys, please be sure to thank @Astr4y4L for his unceasing hard work and development on this device. If you like his work and benefit from it, donations are always nice, even if just a couple bucks.
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2MUwxNk1oeXJCZEE?usp=sharing
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
wperdigon said:
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
Click to expand...
Click to collapse
I just hold volume up and keep it help while connecting the micro USB
Metalchic said:
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
Click to expand...
Click to collapse
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
MotoJunkie01 said:
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
Click to expand...
Click to collapse
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Metalchic said:
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Click to expand...
Click to collapse
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
MotoJunkie01 said:
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
Click to expand...
Click to collapse
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Metalchic said:
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Click to expand...
Click to collapse
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
MotoJunkie01 said:
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
Click to expand...
Click to collapse
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Click to expand...
Click to collapse
OK. Let me know..
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Click to expand...
Click to collapse
Yeah tell me about it. The good ol' Nexus days were much simpler. I'm like you....I think its a Red Herring of some sort you are dealing with. Something so obvious and so simple that it is hiding behind a thin wall.
I'm searching right now trying to help too.
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
roscoemctavish said:
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
Click to expand...
Click to collapse
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
MotoJunkie01 said:
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
Click to expand...
Click to collapse
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Metalchic said:
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Click to expand...
Click to collapse
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
MotoJunkie01 said:
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
Click to expand...
Click to collapse
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Metalchic said:
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Click to expand...
Click to collapse
OK. So both you guys having the stop at 9% please try this. Rename the VS425PP2 file to the filename VS425PP6. Then flash the .kdz.
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
MotoJunkie01 said:
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
Click to expand...
Click to collapse
No worries man and I appreciate just having this as a potential option. If it matters I have tried to root my phone with Kingoroot. Of course it fails but the software status has changed to "modified". Current software version is VS425PP5.
I did try changing the filename "VS425PP2_02_ARB00.kdz" to "VS425PP6.kdz" and flashing with the same result (Stops at 9% with unsecure image error). There is a log file in the "\LGUP\model\common\LOG" folder which when opened in notepad produces unreadable text. Let me know if I can provide anything else.
Thanks!
I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/
Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.
Thank you so much, worked like a charm.
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs
mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse
MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs
Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!
I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!
Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english
switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue
Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.
Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.