Moto C malfunctioning, reflash attempt - Moto C Plus Questions & Answers

Sorry but i see no common Motorola or C model subforum, it's a bit confusing for me so many sub forums..
Anyway, my Motorola Moto C XT1754 started to bild software issues right after 2 years warranty ended, first
the GUI keyboard ignoring my settings and after about 4 years the phone is full of deficencies, now
i want to reflash original ROM that i've found on Web, this is my first flashing attempt with a cellular,
i preferred to install RSD Lite 6.2.4 on my Win 7 Pro machine, the problems occurred soon, i have unzipped
firmware archive in a dir that contains "firmware" subdir, i have loaded the XML file named
"flashfile_config_namath_58.xml" into RSD lite but it wrotes:
"Please check input file. Either XML format is wrong or image files associated with it are missing"
the same end if i let RSD lite to unpack the zip by itself. I have tried to rename xml file into: "flashfile.xml"
but no go..
i have already installed previously Motorola drivers named: Motorola_Mobile_Drivers_64bit.msi and them works
for a normal connection (i see user files), but when i boot into fastboot (vol- + PWR, then scroll menu to
fastboot, then OK) Windows is unable to get a correct driver and in RSD lite if i click on Show Device i get
none..
Thanks 4 any help... bye.

is it possibile that i have to use an older version of RSD lite? my phone is from 2018

Related

Acer Liquid (A1) Offical ROM ??

I found the rom from acer-club.ru . It supported T.Chinese and English. Welcome someone has this machine can try update the rom by yourself.
http://download.acer-club.ru/garbage/ACER_A1_0.029.03_EN.zip
Rom + Flash tools
http://download.acer-club.ru/garbage/Acer_Liquid_1.004.00.zip
Rom Only
http://download.acer-club.ru/garbage/Acer_Liquid_Drv.zip
USB driver
How to flash:
1.) run the flash tools program
2.) push and hold the vol+/- & camera button then power only the machine.wait for the call in light is flash then release all button . at this moment the flash tool will show the device is connected .
3.) select the rom file then press start , it will start the flash process.
Sorry for my poor english.
[報價= wonderswans; 5118608]我找到了光盤的宏基,club.ru。它支持噸中文和英文。有人歡迎這台機器可以嘗試更新你自己的ROM。:)
[網址] http://download.acer-club.ru/garbage/ACER_A1_0.029.03_EN.zip [/網址]
光盤+閃存工具
[網址] http://download.acer-club.ru/garbage/Acer_Liquid_1.004.00.zip [/網址]
ROM只
[網址] http://download.acer-club.ru/garbage/Acer_Liquid_Drv.zip [/網址]
USB驅動程序
如何閃光:
1。)運行Flash工具程序
2。)推動並按住音量+ / - &相機按鈕,然後只machine.wait權力的呼籲光閃光,然後釋放所有按鈕。在這個時刻,Flash工具將顯示設備連接。
3。)選擇ROM文件然後按下啟動,它將開始閃光過程。
對不起,我的英文不好。[/報價]
我用過2個rom........都無中文版
Acer Neotouch
I have an Acer Neotouch and i would like to put Android OS on it. Now it has windows mobile 6.5 installed. Do you think that with this image it will be possible to do that?
Anyone have any success opening this bin file?
I tried converting the bin file to an iso, I tried creating a .cue file and using Daemon Tools, etc. Nothing I am trying is working.
Someone that is more knowledgeable about manipulating bin files please open it up and copy the extracted files into a .zip
Thanks! Shane
While trying to use an ISO converter I received the following error messages:
10:22:45 - Checking source image: C:\Users\Shane\Desktop\ACER_A1_0.029.03_EN\ACER_A1_0.029.03_EN_1930829086b441ed9606df778a27d862.bin...
10:23:34 - Error: cannot find ISO_9660 signature
10:23:34 - Error: This is not a valid CD/DVD image
I have tried to open the .bin file with some specific programs but no succees. Something is wrong with that file.
lol guys...you are trying to convert bin to iso...it's not a dvd or a game? bin files can upgrade you phone only with acer update tool. Read more before you might screw your phone's
also... heres's the flasher only file... so you dont have to download 70mb... but only 1.5mb
http://android.modaco.com/content/acer-liquid-liquid-modaco-com/299500/acer-download-tool-for-a1/
posted link out of date!!!!!

[STICKY][FIX][INFO] NVFlash USB Driver Solution...

When setting up to nvflash my G-Tablet to recover from an install problem, I couldn't flash because my computer couldn't find the driver to install that would let my Windows 7 64-bit PC talk to my G-Tablet. Turns out that the file set I was using for nvflash did not have the drivers in it.
Per Roebeet's sticky thread I went to:
http://db.tt/Wm25t7U
and downloaded the Windows files:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
The second file with "windows" in the middle has the nvflash program in it and also has an Android USB .inf file listed in it. After working with it, however, I found that it does not have the drivers to go with the .inf file. So I searched all over Nvidia's site and everywhere else looking for USB drivers.
Then I remembered that I had downloaded a copy of Advent Vega's USB files while researching one day. I extracted it and put it in my NVFlash folder and tried flashing again.
When I connected my tablet to the PC, the PC immediately tried to load a driver -- but since it didn't know where my files were it failed. I then went to Start/Control Panel/Device Manager and found APX listed in the devices with a yellow "!" (exclamation point) on the icon. I then selected the APX item and found the "Update Driver" button and clicked it. When it ask where to search, I took the local computer manual selection choice and told it to Browse.
I then pointed Browse (and the USB install) at the "USB" directory under "SystemUSB" in my NVFLash folder. (The SystemUSB folder actually has a "Flash USB driver" folder under it with the "USB" folder under it.) I suppose when you extract from the original you could just put the "USB" folder in the NVFlash directory.
When pointed at the "USB" directory, the driver installed and I was ready to nvflash.
I did this myself successfully. I have read posts from two other folks who also have used this successfully. So I believe it works fine.
But, of course, I urge you use caution and can't promise something could go wrong. (Disclaimer complete.)
The USB driver download is at:
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files.
I hope this helps.
Rev
I also posted the files in one of the nvflash related threads here.. if you have the msi you can do this:
msiexec /a %1 /qb TARGETDIR=%~d1NVtemp
move "%~d1\NVtemp\PFiles\NVIDIA Corporation\%~n1\usbpcdriver" %~d1usbpcdriver
thats a batch file.. and it extracts the msi without installing.. into <drive>\NVtemp\
%1 = file name
%~n1 = file name without extension
%~d1 = drive of file name
windows will fill in the blanks if you drag and drop the msi file onto the batch file you create.
fyi latest is tegra_ventana_froyo_20110207.msi .. well technically it is tegra_ventana_gb_20110222.msi - but they both have 01/31/2011 driver inf and 06/24/2010 dll files - so... not that new
this is the apx drivers rar'd up. from tegra_ventana_froyo_20110207.msi
http://forum.xda-developers.com/attachment.php?attachmentid=535715&d=1299488454
Listed below is a link from Blades which provides the USB drivers we need without
having to load the whole SDK to get to them:
http://forum.xda-developers.com/attachment.php?attachmentid=535715&d=1299488454
I hope he doesn't mind my moving the link over here since I have been trying to get
this info together where people having trouble can find it. Thanks to him for the info.
rev
I posted it here first.. but no prob.. those drivers worked right away.. make sure to point to the inf file and not the subdirs AMD64/i386.. as they only contain dll files
Blades,
hmmm. I would have swore your edit was not there when I wrote my post. Certainly you can see that there would be no reason to re-post otherwise!!! Your edit was way before my post
unless there's something weird with the time stamp. Or maybe my tired old head is just working weirder than usual today.
Either way, your work is appreciated and you should get the credit for it. Thanks,
Main thing for me is that I am trying to solve the problem that people didn't have the needed USB drivers. Now we have multiple sources.
Rev
All,
Otreblada posted the following message in a thread over in General. Since it provides a download source for the NVFlash stuff we are talking about, I have copied it over here.
His work, not mine. It contains the nvflash file, image files and USB subdirectory needed to nvflash your tablet back to stock. I have not used it. He says it works fine.
"Get this zip from mediafire.Instructions inside zip file. It does work I created this zip after struggling for almost 1 hr trying to flash back stock rom."
http://www.mediafire.com/?5op96ostv5w2qiy
butchconner said:
When setting up to nvflash my G-Tablet to recover from an install problem, I couldn't flash because my computer couldn't find the driver to install that would let my Windows 7 64-bit PC talk to my G-Tablet. Turns out that the file set I was using for nvflash did not have the drivers in it.
Per Roebeet's sticky thread I went to:
http://db.tt/Wm25t7U
and downloaded the Windows files:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
The second file with "windows" in the middle has the nvflash program in it and also has an Android USB .inf file listed in it. After working with it, however, I found that it does not have the drivers to go with the .inf file. So I searched all over Nvidia's site and everywhere else looking for USB drivers.
Then I remembered that I had downloaded a copy of Advent Vega's USB files while researching one day. I extracted it and put it in my NVFlash folder and tried flashing again.
When I connected my tablet to the PC, the PC immediately tried to load a driver -- but since it didn't know where my files were it failed. I then went to Start/Control Panel/Device Manager and found APX listed in the devices with a yellow "!" (exclamation point) on the icon. I then selected the APX item and found the "Update Driver" button and clicked it. When it ask where to search, I took the local computer manual selection choice and told it to Browse.
I then pointed Browse (and the USB install) at the "USB" directory under "SystemUSB" in my NVFLash folder. (The SystemUSB folder actually has a "Flash USB driver" folder under it with the "USB" folder under it.) I suppose when you extract from the original you could just put the "USB" folder in the NVFlash directory.
When pointed at the "USB" directory, the driver installed and I was ready to nvflash.
I did this myself successfully. I have read posts from two other folks who also have used this successfully. So I believe it works fine.
But, of course, I urge you use caution and can't promise something could go wrong. (Disclaimer complete.)
The USB driver download is at:
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files.
I hope this helps.
Rev
EDIT: Since this post I have found a post by CyHawk which has a direct link to the nVidia Android SDK:
http://developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
If you download and install this it looks like it includes the nvflash stuff in the "windows" files listed above --
and more importantly it has a folder in it called "usbpcdriver" which contains the same files as the Advent
Vega download above. I have not used the nVidia SDK stuff, though, so I can't vouch for it.
Click to expand...
Click to collapse
When you unzip those 2 nvflash zip files do they containany zip files within them? When icicles I see abunch of files and a zip file.
isu205,
I don't remember any .zip files. The "nvflash" file does start off with an .inf file, but that is the USB .inf file that does not have the drivers with it (which is one of our problems.
If you:
1. Download the Advent Vega USB files
2. Down load and extract the two .zip files roebeet suggested.
Then put those files in a NVFlash subdirectory -- your are ready to nvflash.
That's all you will need to restore to the older bekit stock version.
(I think if you download the otreblada file it has the above already in it.)
Rev
P. S. -- You can find, download and install the nvidia SDK, and it will give you
the same files plus more -- but it also adds some complexity.
You pays your money and takes your choice!!!
EDIT: I double-checked and the answer is NO. No zip files I could find.
I'm a linux guy but do have a Win 7 Starter netbook. A while back I installed everything (sdk and USB driver)? necessary to grab screenshots using adb and ddms or QtADB and everything works well.
Anyway, does this mean all I need on the netbook is:
nvflash_gtablet_2010110500.zip
nvflash_windows_20100500.zip
to get nvflash up and running?
joe2262,
Yes, I think you should be good to go as you have described. Once you install the
USB drivers, or once ADB is installed in the SDK with its drivers -- the drivers stay in
the system and are activated when you connect the tab and PC.
And actually, I've never done it this way, but if you have the SDK you should have
the nvflash_windows-20100500 installed. All you would need is the .img files from
nvflash_gtablet_2010110500.zip (and the ngflash_gtablet.bat file which runs the flash
which is in the other .zip file).
Rev

How to use SMGVER.EXE on stock roms (.SBF's)

I've found that several people on XDA-Developers are confused or asking, how to use it or even wondering why the black window keep showing when they try to apply the sgmver.exe to a SBF. Most of the instructions I've seen are something like: Apply SGMVER to SBF...
Well, we need the following tools:
MotoAndroidDepaccker: 4shared.com/archive/4OvekGU7ba/-_MotoAndroidDepacker.html
SMGVER: 4shared.com/rar/yKlGlwiCba/smgver.html
We can use RDS lite 6.x to decompress the SBF if is in .gz format.
1. We start MotoAndroidDepacker once we have the SBF we wanna analyze
2. Click open from file and select the desired SBF file
3. Click split to folder and wait 'till it finish
4. Open the folder named affer the original sbf filename with the "extracted" addition,you'l find there de contents of the SBF.
5. Place (copy paste) the SGMVER.EXE and the VER.BAT files in that directory
6 Click the VER,BAT file and you are done.
A window will show you the bl version of the SGM files, it is common some of them have no signature data and it is normal, will display "no signatured data found. Close the window to finish, you can delete the files you pasted if you are going to repack them to a sbf.
I hope this minitutorial helps you,
Visit and subscribe my YouYube as knomon youtube.com/user/knomon I will make some video tutorials there.
Thaks a lot,
Greetz

[Tutorial] - How to install any firmware using Windows Device Recovery Tool

It worked for me, it might work for you. Do it at your own risk.
Windows Device Recovery Tool (WDRT) will download and install only the latest version of the software available for your device.
This tutorial will show you how to use WDRT to install ANY firmware version you want on your windows phone device.
That is, you can upgrade or downgrade. For example, go from wp 10 to wp 8.0, or from wp 8.1 to wp 8.0, or whatever you want.
Here is how to use Windows Device Recovery Tool to install any firmware released for your model:
I try to ilustrate the process in this video: https://www.youtube.com/watch?v=gnLQ_u4kF7E
STEPS:
0) Download the firmware you want to install (only the .ffu file)
1) Let WDRT downloads the last firmware version for your model (that's what it does). When the download is completed, close the program before the installation starts. You don't have to have the last firmware version installed on your phone, but you have to have it on the WDRT folder.
2) Go to the location where WDRT stores the files: c:/programdata/microsoft/packages/products/
3) Duplicate the folder "RM-xxx" (your model) containing the files WDRT downloaded. You'll have two folders with the same content, like "RM-xxx" and "ARM-xxx", for example.
4) Go back to the place where the .ffu file you want to install is and copy it.
5) Enter the "ARM-xxx" folder and paste the .ffu file.
5) Now you have two .ffu files in "ARM-xxx" folder. Copy the name of the original .ffu file that was already there before you paste the other .ffu file and delete it (the original one).
6) Rename the .ffu file you've just pasted with the name you just copied.
5) Open WDRT, select your phone, and click install/reinstall. After the program checks the compatibility of the files, the message "switching the phone to flashing mode" will apear, as soon as it happens, go back to the "Products" folder and rename the folder "RM-xxx" to something else, like "RM-xxxA, and rename the folder "ARM-xxx" to "RM-xxx". This has to be done quickly, before the installation starts.
6) If everything is OK, the installation will start and you'll have your firmware installed.
With this method i finally got my lumia 620 working again, after the touch screen stopped working due to an accidentally upgrade. I couldn't use any other method because both my lumia volume buttons are broken, so the flashing process needed to be automatic.
If you have rm-1073 att lumia 640 it will not work because of the cid checks within the flashing. Otherwise any other one should work fine
cannot pass the checks

Android 7.0 on P9 lite

I found a site with a tutorial on how to install Android 7.0 on P9 lite.On version VNS-L31C636B361 there are 3 files, and acording to them, you need to follow these steps:
Extract the contents of the zip files you downloaded from above.
Create a folder named “dload” in the root directory of your device’s SDcard.
Copy all the extracted contents of the zips into the dload folder.
Open the dialer app and dial *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade > confirm the installation.
The firmware will begin installing and once that is done your device will reboot automatically.
But the problem is, if I extract all the contents from all 3 files, some of them have the same name and overwrite, and when I try to install by *#*# 2846579#*# *, it stops after 5% and gives me fail error.
What is the correct way to install and why are there 3 separate files ? (also, do I need to have some settings ? the phone should be connected to PC while installing ? )
Thank you very much!
What model you have?
Seems you have another oeminfo...
i have the same problem, it runs now on version vns-l31c432b161, if a want to install android 7 i get the same message as above
gtdaniel said:
What model you have?
Seems you have another oeminfo...
Click to expand...
Click to collapse
the omeinfo is 100% the same, otherwise if would have said its not compatible.The problem is there are 3 different files for this model to download, and if u extract them in the same folder, they overwrite ? What is the correct way to install them ?
erader said:
the omeinfo is 100% the same, otherwise if would have said its not compatible.The problem is there are 3 different files for this model to download, and if u extract them in the same folder, they overwrite ? What is the correct way to install them ?
Click to expand...
Click to collapse
EDIT: i tried again and it stucks on 5%, doesnt say anything.
Good to know!
If you are in MM 6.0 you can not go to Nougat 7.0 without some preparation until Huawei release official version.
I you are already in Nougat 7.0 (B3xx) you can go to B360-B361, directly with Sdcard upgrade or with three keys pressed method.
U dint answer my question though.Let me be more clear.
Here is a tutorial on how to install Android 7.0 on P9 Lite: http://www.droidviews.com/update-huawei-p9-lite-manually-official-android-7-0-nougat-emui-5-0/
On my model, there are 3 files:
4. VNS-L31C636B361
update.zip
update_data_full_VNS-L31_B360_hw_meafnaf.zip
update_data_full_VNS-L31_B361_hw_meafnaf.zip
and they say
Extract the contents of the zip files you downloaded from above.
Create a folder named “dload” in the root directory of your device’s SDcard.
Copy all the extracted contents of the zips into the dload folder.
But some of the files from these 3 .zips have the same name, and when I copy them in the same folder, they overwrite.
Is that tutorial sh1t ?

Categories

Resources