Develop Bugs

[Q] How do I root the Epic4G w/ the new EI22 using a Linux Netbook with Heimdall?

I am getting very frustrated, I have looked all over Google but see no definitive guide, just fragmented pieces of information on a very risky procedure.
I put my phone into Download mode by pressing '1' key and hitting the Power button. it reads "Downloading..." " Do not turn off the Target!!!"
1) I have heimdall but I get this when the phone is plugged in via the stock thin usb cable:
Code:
[email protected]:~/Downloads# heimdall detect
Failed to detect compatible download-mode device.
[email protected]:~/Downloads#
2) Where and WHAT files do i download? Explicitly? I will put them in ~/android-root-files
3) heimdall-frontend also does not detect a 'download mode device'
4) I cannot root the fricken phone, I am very lost and confused on this procedure, I've watched a ton of Youtube videos, but I have Linux, not windows so I cannot run the Odin tool, only the heimdall tool will work for me.
So to summarize, (very frustrated here) how do I root the Epic 4g with 2.3.5 Gingerbread EI22 using Heimdall, Explicitly what files do I need, where DO i get them, explicitly what commands do I issue with heimdall from the commandline? And if I need to get a new usb cable, please let me know.. I read somewhere maybe my cable isn't good enough, but I know that 'adb' does detect my device.

Try a different cable or usb port, also reboot your computer.
I personally would try flashing back to ec05 first, then rooting, then flashing new roms.

Any updates on whether or not you were able to root your phone?

[Q] Questions about Auto-Root "e4gtauto-sfx"

Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!

Are you trying to say it didn't install CWM? Did you try to boot into recovery yet and see what happens?

Try uninstalling drivers then reinstall and reboot computer
Sent from my SPH-D710 using Tapatalk 2 Beta-4

Honestly, sfhub is a great guy, very helpful with all of his stuff, I might even pm him with that same post and info.
Sent from my calculator watch.

da8vii said:
Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
Couple things to try. Were you able to boot into the rooted FC24 you flashed via Odin? If that won't even boot you will need to reflash that. That has to be working. If it doesn't boot you might want to re-download the tar/exe that says 'RESET user data' option - you can't/shouldnt use the 'NoData' when going from GB to ICS. Run that and make sure the phone boots. Also maybe re-download the e4gtauto package, possible a bad/incomplete download. Then once your sure you phone boots turn it off and go into download mode and run the e4gtauto package again.
Also and this is so freaking important I can't overstate it: Try a NEW AND GOOD USB cable. I personally have had problems that I could have solved in seconds (by using a different cable) take me hours! Just had a 'good' amazon cable fail me this week - trying to get my nandroids off my SD card to my PC and copy over new ROM zips; device would not be recognized. I resinstalled samsung drivers, kies, rebooted systems (phones and computers) and other crap. Then took my own flippin advice pulled a new USB cable out of my drawer and BAM device recognized. Sometimes simple should be done first. Good luck!

da8vii said:
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
I don't think your issue has to do with USB Storage since as you noticed, there is no UI to enable mass storage mode and by default it is off (actually it can't be turned on by default on FC22/FC24 because the USB port is set to MTP mode and the USB utilities UI is removed)
I've actually never seen it pass the "Found Device" stage and then later on come up with an "error: device not found" Usually it will stay waiting for the device if there is something wrong with the connection.
Can you get an "adb shell" session started? If you can get that working, then everything should work. If you don't know how to start "adb shell", use Option E (Extra Options) followed by Option G (adb shell)
Once you start the adb shell session, also verify the /sdcard is mounted properly by typing
Code:
ls -l /sdcard
and making sure the contents look like what is on your /sdcard (ie it shouldn't be an empty directory)

Alternative: Buy Mobile Odin from Android Playstore, aka the market...put el26 cwm tar here: http://db.tt/rIxjBIk8 on your sdcard. Flash cwm el26 using Mobile odin and at "First Samsung screen " after boot hold volume up and power button until you see recovery... Then, flash your choice of ics rom.. (at your own risk of course) I do this daily and I have had to go back to gingerbread a few times from ics, and omw back to ics this is what I do... Works perfect! Just make sure you have whatever zips you want to flash on sdcard previous to this.. Sure you know all that...You can repeat this method every time you flash another ics rom... I do, and have about 100 times already. Lol. For real!
I know this is a little late, but Happy flashing!!
You can read about Mobile Odin here: http://forum.xda-developers.com/showthread.php?t=1347899 and here: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
Sent from my SPH-D710 using Tapatalk 2 Beta-5

There is some driver or USB issue where "ADB" cannot see your phone. This is a standard android sdk tool that Auto Root is using to copy files to your phone.
There are various things you could try. Personally I think you should figure out why adb isn't recognizing your phone as it will help you in the future, especially if you get in some binds, but the quickest way to get CWM installed is to just download the Auto Root zip file to your phone. Then use Mobile ODIN to flash one of the zImage files contained in the copy2sd-img/000root directory in the zip file. You are basically treating the auto root zip file as a complete archive of every stock and cwm recovery that was released for this phone.
Alternatively you could also use the manual instructions in the 2nd post of the auto root thread. The only thing ADB is really being used for in the case of installing cwm is copying files to your phone. Everything else is being handled by scripts that run on the phone itself, which can be done on a terminal running on the phone.
If you want to figure out what is wrong with adb, I can help with that also and I'm sure you'll eventually figure it out, it'll just take a little more time.
First thing I would go over is this troubleshooting post:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Also make sure you are booted into Android rather than Recovery. Stock recovery doesn't enable the ADB interface. Also make sure USB debugging is enabled.

Ok a couple of things. first of all make sure you have your drivers working properly. I'm sure they're good since you rooted..but you never know. Next make sure that when you connect the USB that you don't go into USB mode on your phone. Just plug it up but when your phone asks if you want to connect the USB to share files don't press ok. Make sure system debugging is enabled and accept unauthorized software is checked. Then it should recognize your device.

[Q] Soft bricked i9250 international

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

[A] Solved: KDZ factory flash stuck at about 15%

Hello guys,
I am so happy that I wanted to share this with you. As I still have headache from googling how to flash back your stock rom (which didn't work out because the flash tool gave an error every time at 15%), I can save you a lot of headache with this very very simple fix.
For some people the tool works just fine, but when you have some google bootloader or a newer freegee unlocked one and you want back to stock, lots of people cant follow this thread because of the error at 15%.
The fix is EASY and I found it on the Optimus L9 section, thanks to that guy on XDA.
Follow exactly Davevinci's great thread except for one thing:
http://forum.xda-developers.com/showthread.php?t=2498102
Step 4 is now:
4.GO TO DOWNLOAD MODE POW+BOTH VOL BUTTON PRESSED+CONNECT USB
But step 4 should be:
- Boot up your phone in any stock based rom, for example SAVVY Rom V5
- Enable USB debugging and connect your phone through USB using the LG PC Suite option (make sure to kill PC suite in tast manager).
Now you should see the driver installation of LGE Android MTP device as usual and then just run the flash tool from the guide. Also de mode DIAG is now the right one. The flashtool will reboot your phone to download mode automatically when it's needed.
Still an error? Don't worry, disable virus scanner and firewall and just reconnect your phone. I got an error one time, during flashing, but I followed the steps the flashtool suggested me and now everything went fine.

Manually Update US Retail Moto G7 Power to May 1st Security Update.

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