Related
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Rooting itself doesn't modify anything besides installing an app called Superuser.
You deleting/disabling apps that were not meant to be disabled does.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
smoza said:
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
Click to expand...
Click to collapse
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
dr.pythagora said:
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
Click to expand...
Click to collapse
- As far as I know, you can receive updates but you cannot apply them. It will show in the notifications "Software Update, Click to download" when you download it, it will reboot to recovery and stop there. Again, I'm not 100% sure about this but this happened to me once.
- If you flash a custom kernel like Prometheus Kernel, then you will have to flash the stock boot.img if you wanna go back to stock completely. But if you never changed your kernel from stock, then you don't need to do anything. I have provided the link to stock kernel and stock recovery as well, in the Index thread. (Link in my signature)
PS - As far as Custom ROMs go, you should try the Sense Roms. All of them are based on the stock ROM so all of them are completely stable. You can always put the 'Stock theme' on these roms to make them look like the Stock ROM and you will end up with a ROM that looks exactly like Stock but performs much better and has increased functionality
Hope this was helpful. I'll be glad to answer any further questions.
It will not definitely modify your system it will add a folder to your system to access the system... and also it adds app called Superuser or SuperSU ....
Features of Rooting:
Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem.
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Most of the time,[citation needed] rooting a device voids its warranty.
From Wikipedia ...
Frequently Asked Questions
Motorola Droid 4
This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Q1: How can I tell if I have a Motorola Droid 4?
1. In the software Menu>settings>about Phone>system version will include XT894.Verizon.en.US2. If you install RSD Lite on a PC, connect phone(In AP Fastboot Mode) to PC via usb, and open RSD Lite, The Droid 4 will be listed as Maserati in RSD Lite. see [Video]How to Use RSD Lite to flash a .XML Stock Rom (firmware)
Q2: What is the newest Stock Android Version and System Version?
Android: 4.1.2System Version: Blur_Version.98.72.188.XT894.Verizon.en.US
Q3: Where are the Custom Bootloaders, Recoveries, and Kernels?
Because of the Locked bootloader, the stock bootloader and Stock recovery can not be replaced, But using Safestrap the boot process can be hijacked allowing Custom Recovery, and KernelsFor more on Bootloaders see XDA Wiki: Bootloaders
Q4: Where do I find information on how to root the Droid 4?
[Root] Droid 4 (XT894) Jellybean with SafeRoot
Q5: Can I root the Droid 4 without a computer?
No
Q6: How do I restore the stock rom?
1. DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!)2. [Video]How to Use RSD Lite to flash a .XML Stock Rom (firmware)3. Unbrick Moto device with moto-fastboot.exe
Q7: I have a question about a particular ROM but I can't post in the Development section. What can I do to get the help I need?
The Development forum is for sharing ideas on development. If you have a question about a particular ROM, ask it in the Q&A section.
Q8: How Do I use the Droid 4 on GMS?
[PATCH][GUIDE] Patch to fully enable GSM on Verizon CDMA Android phones
Q9: How Do I Install a Custom Rom?[/SIZE]
See [How To][Video]Installing Rom with SafeStrap
Q10: Where can I find a Custom Rom For the Droid 4?
see [INDEX] Motorola Droid 4 Development for List of Droid 4 Roms and more
Q11: What is a Factory Cable and why would I need one
A Factory Cable aka Motorola Factory Programming Cable or Fastboot Cable. Allows Many Motorola Devices to be flashed without a battery or Low battery for more see Motorola Fastboot/Factory Programming CablesQ12: What is a SBF?
Quote by cellzealot "SBF is a file type and stands for Single Binary File that is the older format of Motorola flash files for use with RSD lite or other flash tools.They include all of the code groups, header files, and checksums as well as a RAM Downloader for all of the device partition images in a single file and flashed from the legacy boot loader enumerated as a flash device.The new format for all dual core Motorola devices is zip archive of fastboot images and an XML file that can be used with RSD lite to flash in a single operation or flashed as individual images using the fastboot binary and DLLs in the Android SDK from the fastboot boot loader and enumerated as an ADB device.These are entirely different modes of access and operation and SBF is both wrong and a misnomer for the firmware files for current devices.The fast boot interface provides far more flexibility and safety for flashing than the old flash interface and avoids all kinds of problems that would arise from managing and updating the firmware on newer chipset devices.It is an extremely important distinction to make and understanding to have about how these phones work.Please stop using SBF when referring to XML.zip files.The current acronym for Motorola firmware files is FXZ and means Full XML ZIP file.".SBF, XML.zip and tar.gz" are Offical Motorola file extensions
Q13: Can I use the Droid 4, without activating with a carrier (WiFi only)?
Yes, see Bypassing the JB Activation Screen of any Motorola Device*Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
added [SIZE=+1]Q11: What is a Factory Cable and why would I need one[/SIZE]A Factory Cable aka Motorola Factory Programming Cable or Fastboot Cable. Allows Many Motorola Devices to be flashed without a battery or Low battery see
Motorola Fastboot/Factory Programing CablesAdded:[SIZE=+1]Q12: What is a SBF?[/SIZE]Quote by cellzealot "SBF is a file type and stands for Single Binary File that is the older format of Motorola flash files for use with RSD lite or other flash tools.
They include all of the code groups, header files and checksums as well as a RAM Downloader for all of the device partition images in a single file and flashed from the legacy boot loader enumerated as a flash device.
The new format for all dual core Motorola devices is zip archive of fastboot images and an XML file that can be used with RSD lite to flash in a single operation or flashed as individual images using the fastboot binary and DLLs in the Android SDK from the fastboot boot loader and enumerated as an ADB device.
These are entirely different modes of access and operation and SBF is both wrong and a misnomer for the firmware files for current devices.
The fast boot interface provides far more flexibility and safety for flashing than the old flash interface and avoids all kinds of problems that would arise from managing and updating he firmware on newer chipset devices.
It is an extremely important distinction to make and understanding to have about how these phones work.
Please stop using SBF when referring to XML.zip files.
The current acronym for Motorola firmware files is FXZ and means Full XML ZIP file.".SBF, XML.zip and tar.gz" are Offical Motorola file extentions
Added:
[SIZE=+1]Q13: Can I use the Droid 4, without activating with a carrier (WiFi only)?[/SIZE]Yes, see Bypassing the JB Activation Screen of any Motorola Device
Thank you!
Thanks
I have a problem at any moment after reboot it is me in the logo of CM11, install the stock from apfastboot with utility and I left after motorola logo, which could be the solution. thanks.
Enviado desde mi DROID4 mediante Tapatalk
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Google Nexus 6[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I'm new to Nexus 6, where do I find a thread with guides and useful information?[/SIZE]The sticky roll up thread in the general forum has all of the guides and important information. You can find that HERE.
[SIZE=+1]Q2: Where can I find tools such as USB drivers[/SIZE]You can find the universal Google driver inside of the Android SDK found HERE. Or you can install ADB/fastboot and universal drivers from HERE.
[SIZE=+1]Q3: What does "flashing" my phone mean?[/SIZE]Well, there are a couple of meanings here. "Flashing" a custom ROM means to overwrite your current OS with a new one. "Flashing" can also mean, changing from a carrier to a pre-paid carrier. Example: I need to flash my phone from AT&T to Cricket.
[SIZE=+1]Q4: Bootloader.. What is this?[/SIZE]For an easy explanation of what a bootloader is, look HERE.
The most recent bootloader and radio can be found here : Here is a recovery flashable zip of the 6.0.1 bootloader and 32r radio
[SIZE=+1]Q5: How do I root my device?[/SIZE]There are a few options. The most recommended way is to unlock your bootloader, flash custom recovery, flash superSU zip, install superSU app. Also there are more automated methods, such as toolkits and auto root. HERE is a great place to get that information.
[SIZE=+1]Q6: What is a factory image?[/SIZE]A factory image for Nexus devices is provided directly from Google. They are used to return your device to the state it was in when it was put in the box. They can be found HERE.
Most recent is 6.0.1 (MMB29Q)
[SIZE=+1]Q7: How do I backup my device in case I bork it?[/SIZE]TWRP recovery has the feature of allowing you to backup your device. It is highly recommended to backup your stock image after installing TWRP and before flashing anything else. Simply use the backup option in TWRP. Think of this as a restore point to go back to when things get borked. Also, you can backup all of your files to your PC before beginning the root process because unlocking your bootloader will wipe your device. There are also apps available that will back up your apps and app data Titanium Backup is a great choice if you already have root. Helium is an option for non-rooted users.
Latest recovery is [RECOVERY][shamu] TWRP 3.0.0-0 touch recovery [2016-02-06]
[SIZE=+1]Q8: How do I flash a factory image?[/SIZE]Flashing a factory image is a fairly easy process. You can use the fastboot method or a toolkit. Toolkits can be found in the development section and an excellent guide to the fastboot method can be found HERE.
[SIZE=+1]Q9: Do the carrier versions matter in deciding on root or ROM?[/SIZE]No. there are no carrier specific ROMs or root methods. There are only two versions of the Nexus 6, Domestic (XT1103) and international (XT1100). Device wiki can be found HERE.. Bootloader unlock method is universal as well.
[SIZE=+1]Q10: What is encryption and should I disable it?[/SIZE]First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out.
[SIZE=+1]Q11: What are fastboot and ADB and should I learn how to use them?[/SIZE]You should absolutely have at least some knowledge of fastboot and ADB. These simple yet powerful tools can save you from trouble and do wonders for your device. The basic principles and commands are extremely easy to learn and thankfully, there are plenty of guides that will help you understand and learn how to use them. Fastboot and ADB aren't exclusive to Nexus either, you can use them with Android as a whole. You can find my favorite guide to using fastboot and ADB right HERE.
[SIZE=+1]Q12: Can I install an OTA if I'm rooted/unencrypted?[/SIZE]No. Since the onset of lollipop, absolutely no system or boot img modifications can be present in order for the OTA to flash. HERE is a thread dedicated to OTA related Q&A and instructions for sideloading. HERE is a thread for OTA files available for sideloading.
[SIZE=+1]Q13: What is a toolkit and should I use one?[/SIZE]First, a toolkit is a program that auto runs and makes changes to your android device. Those changes can be very significant and difficult to recover from when things go wrong. With a toolkit, you can obtain root, return to stock, flash recovery, etc. However, once you start to run the program, you have no idea what is happening to your device. It comes highly recommended to have the basic knowledge of ADB and fastboot even if you are using toolkits. So, should you use one? Sure! No one will tell you not to try, just know what you're getting into and that most experienced users will not use them at all. Therefore, you are more likely to get helped quickly if you have a basic understanding of fastboot, and a tested and working fastboot/ADB environment on your PC, should an issue arise where you need help. Toolkits are absolutely awesome and highly useful in some situations, so don't underestimate their usefulness. It is just that with a Nexus, and a few simple fastboot commands, you can obtain root, return to stock, flash recovery, etc. While typing those commands, you can be 100% certain of what is happening to your device.
[SIZE=+1]Q14: What is CMTE(cyanogenmod theme engine?[/SIZE]Here is a better explanation here And please take note, This is only supported by ROMS that has already adopted CMTE instead of Layers.
[SIZE=+1]Q15: What is Layers (RRO)?[/SIZE]Layers is a extension of runtime resource overlay.
RRO is a framework created by sony for use as a way for them to create xperia themes but also for internal quick prototyping. More explaination from the original thread here. And take note, this is only going to work with ROMs that has adopted to use layers instead of CMTE. Stock roms natively support layers. Just need to download necessary apps and your good to go.
[SIZE=+1]Q16: Systemless Root?[/SIZE]A new way of getting root without modifying /system. More news here.
[SIZE=+1]Q17: Android Pay?[/SIZE]If your running stock and not rooted, no doubt its gonna work out of the box. There was a previous discussion on how to run the feature on rooted devices. It was fun while it lasted. And here is the latest story about android pay.
[SIZE=+1]Q18: I'm trying to search for something specific but I'm having trouble. How do I use XDA Search?[/SIZE]Look HERE for a detailed guide on how to use XDA Search to it's fullest capabilities.*
And here are some terms to ponder
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Thanks to @benjamingwynn for the glossary of terms
Click to expand...
Click to collapse
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
This thread is an ongoing process. This will be a WIP for a period of time
Click to expand...
Click to collapse
This is not intended to be a Q&A help thread. Please only post suggestions for content that should be added to the OP. Post the relevant links to accompany your request.
If you need help or have a general question, consider using these links:
Ask any question/Noob friendly: http://forum.xda-developers.com/nexus-6/help/noob-friendly-qa-help-thread-t3068327
General question and off topic: http://forum.xda-developers.com/nexus-6/general/google-nexus-6-t3077130
Otherwise, create a new post here: http://forum.xda-developers.com/nexus-6/help
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Excellent suggestion, I will get something together tomorrow. Thank you.
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
rootSU said:
"is there a thread with links to important guides and information ?"
"yes, general > sticky roll-up"
Or maybe reword question 1 a little so people know that's where guides are.
Click to expand...
Click to collapse
Done. Thanks!
elevatorguy said:
A suggestion. Maybe have some info on encrypted vs decrypted, what it is how it works,how to decrypt and stay that way. This thread has a file that you flash in recovery to make sure encryption does not get forced while flashing a ROM or kernel (don't know if I broke any rules by linking without permission if I did let me know this is NOT my work all credit goes to the dev) http://forum.xda-developers.com/showthread.php?t=3000788. Also maybe a link to the noob question thread (though it looks like it's one post above for now) thanks for this thread always nice to just read something to find an answer and not have to make a useless post.
Click to expand...
Click to collapse
Done, thanks again.
rootSU said:
One day we'll rebel
Click to expand...
Click to collapse
Question 18 added to build the rebel forces.
Question 19 added.
Question 20 seems to be a frequent flyer.
Thread has been cleaned per OP request.
Please only post questions with answers, you feel would help your fellow Nexus 6 user.
All other conversion... please bring to a new thread or the lounge:good: Keeping in mind this is not a Q&A thread.
Thank you @Evolution_Tech for continued updates.
Questions 21 and 22 added since we have a new update.
Question 23...toolkits.
Post #2 updated with links to general help threads.
cam30era said:
@Evolution_Tech,
While responding to a thread this morning, I was "asked" to change to the New 2015 XDA thread view (web view). Not sure I like it, but that's not why I'm here. What's the difference between "commenting" on a post and "posting a reply"?
Update: Weirder still, some on the comments aren't even viewable in the XDA Premium app. Just shows a web link....... @danarama 's Black Screen thread.
Click to expand...
Click to collapse
I specifically chose a new template for that thread which allows answers to be "up voted" as you may have seen on many technical sites, most prominently, Microsoft technet.
The apps can't handle it so they make you use a browser.
Reply is an answer or solution. Comments are to a particular answer, so for example, I can say "tried that" without creating a response that is seen as a votable answer.
Question #24 added. How to use XDA Search.
updates coming.. stay tuned
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Any version will work but all marshmallow builds are unified and 29q is the latest factory image
MassiveDynam1c said:
Hey guys I'm new here and hope this is the correct forum. I recently purchased a nexus 6 off amazon and when it arrived I was surprised to find it had been rooted already. I want to set it back to original stock image but I'm not sure which version to download. I don't know which provider it was originally on. It is on Verizon now. Can I just download mmb29q and expect it to work? System info says I have mmb29u but there is no option for that version. Thank you.
Click to expand...
Click to collapse
this is not q&a thread. this is for the most common FAQ's..
but to answer ur question. go with 29q. this is the latest stock firmware .
how did u ever got 29u as a stock rom? thats the latest aosp. nexus 6 never had a 29u stock firmeware
Hey folks. I got a new Moto G7 Plus (XT1965-T) and wanted to install TWRP and custom ROM, as done on my G5 Plus. Long story short... I accidentally flashed a recovery image for my G5 Plus, and hard-bricked the phone. I managed to unbrick, thanks to luiz_neto's "[ULTIMATE GUIDE] How To Unbrick your Moto G7 Plus" post (BIG shout out). However, when in drop to Recovery Mode, TWRP v3.2.1-0 as was installed on the G5+, is displayed. The screen then locks up requiring a hard reset. I can boot to the Factory ROM and the phone functions normally, however am unable to figure out how to reinstall the OEM recovery. All procedures to revert back to full OEM seem to reference flashing a factory "Image". I can only find .zip files on the stock ROM. Any clues out there as to how I can fix this problem would be greatly appreciated?
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
and incompleteMy recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
My thoughts too, but stock ROMS are in xml.zip fromat, and I have no idea how to install. Some guidance indicates that extracted files are manually flashed in sequence. This seems odd and instructions are incomplete. Where can the stock ROM, what will be the format, and where can I find accurate and complete instructions?
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
flash713 said:
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
Click to expand...
Click to collapse
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
cliffgi said:
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
Click to expand...
Click to collapse
RETUS is retail US model device. On my G7 Power there were multiple firmwares that could be used. Idk if this is it but check out "RETAIL" from here: https://mirrors.lolinet.com/firmware/motorola/lake/official/RETAIL/
I didn't see a RETUS firmware. G7 Plus is codename "LAKE" correct ?
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
cliffgi said:
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
Click to expand...
Click to collapse
I think RETUS means Retail US. Again, just wagging.
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
flash713 said:
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
Click to expand...
Click to collapse
A BIG THANKS FOR ALL THE HELP.
Did what you suggested. Extracted and located a "Flashfile.bat"... runs a long list of fastboot cmds, as I'm sure you are familiar. Similar to but more involved than the mannual I ran last night(did not work, broke to boot-loop. Also located a file called LAKE_QPWS30.61-21-18-7-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt Contents are as follows:
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-210129
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-18-7-3/284d4d:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.201.3.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPWS30.61-21-18-7-3
SW Display Build ID: QPWS30.61-21-18-7-3
Build Date: Fri Jan 29 08:46:03 CST 2021
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.201.3.lake.retail.en.US
Version when read from CPV: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keys
AB Update Enabled: True
Full Treble Enabled: True
Seems obvious that RETUS stand for Retail US, and all appears to be all correct for my device.
As for a the IMEI it is printed on the box. I have no softcopy.
Very familiar with dd. Excellent idea. Will do, as well as get a full TWRP backup, when get it running.
The unzipped ROM file creates directories: Driver, Firmware, and RSD Flash Tool, as well as credits.txt and How to Flash.txt. How to Flash.txt simply says to install drivers, I have already done; connect device which I know how to do (fastboot devices confirmation), and run the previously mentioned flashfile.bat from the Firmware directory.
Questions:
What It does not say is that this zip was designed for Windows, not Linux (as I ran last night). I also assume that it should be run as administrator. The Windows machine already has Adb Tools and Fastboot installed. I haven't really touched a Windows machine in ten years (TG), but from what I recall, unlike Linux/UNIX, the current working directory is automatically added to the search path. Is this stil the case for Win10 and will the current working directory be searched first, or is there a possibility that there might be a cmd/file version mismatch between the two installs? I have no idea what the directory of RSD Flash Tools is for. ? Any additional thought before I take the pill? A BIG THANKS FOR ALL THE HELP.
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Well tried to flash stock ROM and got error messages/failure. See attached screenshot.
jwoegerbauer said:
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
flash713 said:
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Click to expand...
Click to collapse
Got it 100% fixed. Principle problems in recovery from this zuck-up were scoping the problem, locating the proper Stock ROM, figuring out fastboot, and lastly, identifying a defective adb fastboot install on the Windows 10 system I was using. Switched to my primary Linux system and life got a whole lot better.
MANY MANY THANKS to you ( flash713) for suffering through my stupidity without insult, and helped me ID the correct ROM and provide good links that helped me figure out what to do with it once I had it. Seriously, I could not have done without your help. For the Moto G7 Plus XT1965-T, the stock ROM is LAKE_RETAIL_10_QPWS30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. The image below was from my first attempt with the correct ROM. I discovered that ADB Tools and Fastboot install on my Windows10 system was corrupt. GO LINUX!!!
I use Lubuntu (a lightweight Ubuntu) on Chromebook. My regular laptop died so I use my CB all the time now. Linux most definitely #1 always imo!! Really glad you got it going!!
Hi,
I managed to soft brick my Edge 20 Pro and needed to install a stock ROM... It was quite a hassle, so I ended up creating a tool that enables it without the official RSA tool.
Thomas Hastings / motorola_flash_xml · GitLab
GitLab.com
gitlab.com
I hope it'll be useful.
There has long been an excellent utility for installing firmware on Motorola phones - TinyFastbootScript
Or did you create this for Linux?
ilia3367 said:
There has long been an excellent utility for installing firmware on Motorola phones - TinyFastbootScript
Or did you create this for Linux?
Click to expand...
Click to collapse
Hey, thanks for letting me know about TinyFastbootScript! I googled up and down, but only found Motorola-XML-To-Batch-Script, and I had to make changes to the output to make it work.
This should theoretically work both on Linux and Windows though, but the latest fastboot version in Ubuntu and Debian didn't work with my phone, so I had to use Windows to flash it. With a goot fastboot though, it would work on Linux, yes.
[Index] Flashing Motorola Firmware (2021)
[Index] Flashing Motorola Firmware If your device has its own section please post in that section. You can ping me with @sd_shadow There are a few options for flashing stock Motorola firmware. Linux and Mac flashing options are posted in my...
forum.xda-developers.com