Related
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
picklz said:
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
Click to expand...
Click to collapse
im having similar issues...im stuck in "waiting for device" in the bootloader.
I'm having the same problem and nothing I've found helps. Since I really want to unlock the bootloader, and doing so wipes the device, I'm stuck not being able to do anything with the phone until I get this worked out
I had this problem when I was unlocking the bootloader. I kept playing around with it and reinstalled the drivers multiple time. I would uninstall the driver and install the driver when the phone was in bootloader mode (I believe).
Make sure the drivers you're setting it to are new.
http://dl.dropbox.com/u/4174784/usb_driver.zip were the drivers I used. These are for GSM model, not sure if they work for the CDMA/LTE version!
Alternatively, you can install PdaNet for drivers.
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Some people also had luck by installing the windows pdanet which installs drivers that should work too.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks buddy!
Worked for me, I thought it was due to my HTC/Motorola device drivers, so uninstalled all of those and re-installed the Samsung...but these steps worked. Thank you again (I did also hit the thanks button too FYI!)!
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
It worked for me. Thanks!!
i have no idea why but it is just not working :/ in that last set of instuctions above...i dont even have android bootloader interface lol which is weird cause ADB is reading my phone just fine...but when in bootloader mode it just says waiting for device. Does anyone have the fastboot drivers?
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
That method didn't work for me either. I'm running windows XP professional and do not see 'Android Device' in the list of devices... any other ideas anyone?
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
RMarkwald said:
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
Click to expand...
Click to collapse
I did,
Tried the PDAnet method as well. Adb works fine. Once I get into the boot loader the device isn't recognized. I get the Android 1.0 install prompt and cant install it.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks! FWIW, I had to uninstall the Samsung driver and use the Google USB driver to find the Android Bootloader Interface one... if others are having trouble, try that.
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
samakbuchanan said:
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
Click to expand...
Click to collapse
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Petrovski80 said:
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Click to expand...
Click to collapse
op, if you just want to get the device to working state again, and dont care about any data:
1. get the naked driver package (see Efrant's guide)
2. boot device into bootloader and connect usb cable
3. open windows device manager, find your device and manually update the driver
5. flash 4.2 stock images using fastboot
step 3 is the same, the same procedure, the same driver; windows is dumb so you have to tell it again when device is in bootloader (which, btw, is NOT the same as download mode).
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
samakbuchanan said:
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
Click to expand...
Click to collapse
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
bk201doesntexist said:
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
Click to expand...
Click to collapse
Thank you for another helpful reply! Yes i am using windows 7 - i will try to perform the task now - results soon. In the meantime if anyone else knows instructions on how to do this i would love to hear
I am at work and dont have administrator settings on windows 7 so i went to an older computer and started fastboot.exe. I went to recover and there was the IP address of the computer went to that and recovered. From there i went to reboot and now i am just getting a Google in the middle of the phone (as before). I will wait some time to see if it will start up now. If not what is my plan?
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
samakbuchanan said:
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Thanks for that i had since found that and have printed it and will work through each step methodically. I have the stock image on download.
I have spent the best part of my working day on it now. Fingers crossed it all works out.
Thanks to all who have helped me through this far
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.
Update: 2nd post now has a way to update the Moto G7 without erasing user data. Method uses most of this tutorial but now you unzip image and select a file within in the unzipped image. Either way still backup your phone just in case. User MrCamby let me know about the "Lenovo MOTO Smart Assistant" for backup.
Yesterday I updated my US Retail version Moto G7 Power to the newest firmware build# PPO29.114-108 with the May 1st Security update manually. My previous build with the March 1st security update was PPO29.114-63-2. I have the Retail US Model with 3GB of RAM and 32GB of Storage. DO NOT flash the Moto G7 Power international version with 4gb RAM and 64GB storage, it will probably brick it.
This process will delete everything on the phone as it flashes all the phone's partitions. The phone will be as it was when you first bought it having to re-enter your account info and download all your extra apps not included with the stock phone. Please backup everything if you decide to update the phone using this method. On my phone most things were stored on the cloud but I did forget I had some unimportant things on the phones download folder.
Thanks to user MrCamby for letting me know bout the "Lenovo MOTO Smart Assistant" which will backup the phone on your PC (Windows only) before you flash it. I haven't personally used it but from it's .pdf guide it will backup your phone before you flash it preserving images, SMS, Contacts, etc... Link to Lenovo Moto Smart Assistant
https://support.lenovo.com/us/en/downloads/ds101291
The first step is to download Motorola RSDLite6.2.4.zip software used to flash the firmware file.
The software is available at: https://mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
Unzip and Install the RSDLite software and move to step 2.
Step 2 is to download and install the MotorolaDeviceManager_2.5.4.exe Software/Drivers at:
https://mirrors.lolinet.com/software/windows/Motorola/Drivers/
Step 3 is to download the 1.9GB firmware. Be sure the file downloads completely! Flashing an incomplete image could damage the phone. The MD5 checksum is 8bb8f13ec0fe23c977b57c86f2033db9 MD5 Checker attached.
Choose the Firmware dated 2019-06-05 and Named:
XT1955-5_OCEAN_RETUS_9.0_PPO29.114-108_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
With the two pieces of software installed and the firmware downloaded it's time to install the firmware.
Warning this process will completely erase your device and reinstall the new firmware. only attempt this
process if you have a US Retail G7 Power with 3GB RAM and 32GB of storage. Do not interrupt the process
once the flashing has begun or you may have a brick(dead phone). Please continue at your own risk.
1) You'll need a USB C cable and be sure the computer is plugged in to power if a laptop. The phone should have at least a 60% charge.
2) Shut off the phone. Once the phone is completely off, Hold the volume down and press the power button still holding the volume down button.
3) The phone should boot into the boot loader mode, release the power & down volume button. See bootloader.jpg attached to see what screen looks like.
4) Plug the USB C cable into the phone and into a USB 2.0 port(black colored) on your computer. On my computer the phone didn't show up in RSDLite program when plugged into a blue colored USB 3.0 port. Others online reported the same problem.
5) Launch the RSDLite program and click show device. (Figure_1 Picture attached to post)
6) If everything went right you should see your phone listed on line 1. The program doesn't list any specific info just that a device is connected. See Figure_1 Picture attached to post.
7) Click the box on the top and select the firmware image still zipped. (The RSDLite program will unzip the firmware) and then click on the start button. See Figure_2 picture attached to post for box to load firmware and start button.
8) This is your last chance to not ERASE your phone and load the new firmware. After clicking start in last step a menu will pop up with three options. Choose the middle option "Uncompress and Start Flashing" See Figure_3.jpg attched to the post. During the firmware flash DO Not unplug your phone or allow your laptop to sleep. The process took about ten to fifteen minutes. The program will update the files it's flashing i.e. flashing 1 of 32, 2 of 32, etc....
9) When the flashing is done RSDLite will reboot the phone and you'll be prompted to choose your language like a new phone.
Troubleshooting: If line 1 in the RSDLite program is blank after plugging in the phone and doesn't show a device then you'll need to try a different USB port on your computer. For some reason the phone only shows up on my black colored USB 2.0 ports and not my blue colored USB 3.0 ports. Also try a different USB cable if it doesn't show up. These are common issues with the RSDLite program from my research.
Update Moto G7 Power without erasing device.
Follow the steps in the post above but stop at step 6 and start here.
7) Unzip the firmware image you downloaded in a folder you create.
8) Open the RSDLite program and click the box on the top and then select servicefile.xml in the folder you created in step 7.
9) After selecting the servicefile.xml click start and flash your phone. This should not erase your data.
10) Some forums reported it is better to erase the phone per the top posts but no reason was given.
Update Moto G7 Power without using RSDLite.
Since some people have reported trouble getting to RSDLite to work so I decided to do it in a way similar to the way I updated my Pixel using Android Platform Tools.
1) Create a folder where everything will be kept. like a folder called android in C:\ like C:\android
2) Download the Android Platform Tools attached to this post and extract to the folder you created.
3) Download the Phone firmware in top post and UNZIP into the same folder you created with platform tools in it.
4) Download update_batfile.zip attached to this post and unzip into the folder you created with the phone firmware and Android Platform Tools in it.
5) Open a Windows command prompt in Start menu--> windows system or by holding the windows key + R and typing CMD.
6) Plug your phone into the laptop and go to Settings--> System-->Advanced-->Developer Options then toggle "USB debugging" to on. A screen should appear on the phone "Allow USB Debugging" press OK.
7) If you don't have developer options in your System-->advanced go to System--> about and tap the build number 7 times. Now try step 6 again. Developer options should be there.
8) Navigate to the C:\android folder you created or whatever folder you created with all the files in the Command Prompt. Something like cd \android
9) Turn off the phone, Once the phone is off, hold the volume down and then hold the power button. You should boot into the bootloader screen. Release the two buttons.
10) So you should have the phone in bootloader mode, all the files in one folder, have previously selected USB debugging when the phone was booted up, and the command prompt at the folder with all the files in it.
11) now type in the command prompt type either update_no_erase.bat or eraseandupdate.bat Obviously the update_no_erase.bat updates the phone without erasing it and eraseandupdate.bat erases the phone and then updates it. After typing the one of the two .bat filenames press enter and the .bat file will update the phone and then reboot it.
12) Good luck!
Man I was wondering why nobody was updated yet since that firmware has been available for a while.. I flashed it about last week or less all good..
Man I forgot about RDS Lite damn it.. . I flashed it manually and was PITA since it has Patition A and B and a few times I messed up the commands and installed parts of partition B on partition A since everything installs by default to Partition A unless you specify System_b because I forgot to specify the partition..
T
I weird thing about this May 1 lst Firmware and the one before after unlocking bootloader, in system updates it stated that my device is compromised so no more Ota but today out of nowhere that message changed back to normal System Up to date. So weird I did nothing at all.
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
thaessential said:
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
Click to expand...
Click to collapse
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
nucher said:
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
Click to expand...
Click to collapse
yeah I'm definitely getting it done soon. these unsuccessful update warnings are super annoying. i keep trying to hide more google and moto apps and some other things but nothing seems to have any effect
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Omar04 said:
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
Click to expand...
Click to collapse
nucher said:
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Click to expand...
Click to collapse
Yes I know that. Thanks anyway I been playing this game since Android 2.2 ? In my case are the ports 95% sure about it.
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
thaessential said:
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
Click to expand...
Click to collapse
Yeah man I test it in several laptops only being recognized on 3.0 Ports. Because of "USB Type C"
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Rondeau79 said:
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Click to expand...
Click to collapse
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always ?
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Omar04 said:
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always
Click to expand...
Click to collapse
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Good to know. I'm new to the Motorola / Lenovo ecosystem. I've had Nexus and Pixels for the last 4 years. I'll add a link to the Lenovo Moto Smart Assistant Software in the main thread. Thanks!
MrCamby said:
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
nucher said:
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Click to expand...
Click to collapse
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically. ?
My 2nd post below the top will be a .bat file to use with ADB tools. Basically put the unzipped firmware, .bat file, and the adb tools all in one folder and run the .bat file. I just finished testing it now to type the post up.....
2nd Post is up now....
Omar04 said:
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically.
Click to expand...
Click to collapse
so i noticed there are also linux and mac versions of rsdlite. i have a linux pc running debian 10. was gonna try stuff out on that and see if i get different results. personally when it comes to stuff like this i would much prefer to use gui software than term. i only have one phone... well that's not quite true... i only have one new phone lol