Motorola Moto G Power (2022)
XT2165-5 US Retail Variant
Codename: Tonga
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting GuideOVERVIEW:
This guide outlines simple step-by-step instructions for rooting the Moto G Power (2022). To alleviate some of the legwork, and to cater this guide to new and inexperienced members, I have provided boot images pre-patched for the Magisk v26.1 systemless root solution. In addition, for those members who prefer the Android 11 stock ROM over Android 12, I am providing patched boot images for both the Android 11 and Android 12 firmware builds. (It has been reported that upgrading to Android 12 breaks Widevine L1 and reverts to Widevine security level L3.)
When downloading a patched boot image per the below instructions, be sure to choose the boot image that corresponds with both your installed Android version and firmware build number.
COMPATIBILITY:
The supplied Magisk patched boot images in the downloads section below are from both the Android 11 and Android 12 based firmware builds for the XT2165-5 US Retail Tonga variant. In theory, these boot images may work on rooting other variants as well, but I have only tested them on the referenced retail variant. To ensure compatibility, unless you are rooting this particular retail variant, procure the boot image from your variant and firmware build. Tonga official firmware for all carrier models and variants is available from the Lolinet repo here Tonga Official Firmware: Lolinet Repo
PREREQUISITES:
In order to root your Moto G Power (2022), you will need an unlocked bootloader and a Windows PC or laptop with the ADB & fastboot tools installed. I have included a link in the downloads section below for the latest Minimal ADB & Fastboot tools for Windows. This procedure can be carried out on a Mac or Linux setup as well; however, for purposes of this guide, I will focus on a Windows setup. Windows 7/8.1/10/11 will suffice. You will also need the factory supplied, or a quality equivalent USB-A to USB-C syncing/charging cable.
If you have not yet unlocked your bootloader, head on over to this tutorial and do so.
Motorola Bootloader Unlocking Tutorial
Please be sure and thank XDA Recognized Contributor @sd_shadow for his comprehensive and easy-to-follow tutorial on bootloader unlocking Motorola mobile devices. It is, hand down, the most thorough and detailed guide on this procedure, and is highly recommended to those members who are unfamiliar with the topic.
Keep in mind that not all carrier variants of the Tonga are supported for bootloader unlocking. For example, if you own the Verizon, AT&T or TracFone branded Moto G Power (2022), among some other carrier variants, your bootloader is not officially supported for unlocking and, as such, rooting may not to be an option. However, it should be noted that most MediaTek chipset models can be exploited by a reverse engineering tool called MTK Client which, among many other things, can force the bootloader into an unlocked state. Whether the MTK Client exploit can be used on any of these locked down Tonga models & variants is unknown to me. It wouid, perhaps, be worth researching more if you own such a variant of the Tonga.
The tutorial link I provided above will help you make the determination as to whether your variant is officially supported for unlocking. If you own a Retail variant, your bootloader can be unlocked via Motorola's official support portal. Again, the link I posted above will guide you in this regard. Simply return here once you have successfully unlocked your bootloader.
ANDROID VERSIONS & FIRMWARE BUILDS
The boot images provided in the downloads section below have been patched with Magisk v26.1 for systemless root support. The Android 11 boot image corresponds with the last official firmware released prior to the Android 12 update rollout. The patched boot image for Android 12 corresponds with the latest firmware build available for the Tonga at the time of posting. Specifically,
The Android 11 boot Image corresponds with firmware build no. RRQS31.03-68-153-2
The Android 12 boot image corresponds with firmware build no. S3RQ32.20-42-10-9-4
To prevent boot loops, bugs and potential issues with compatibility, flash only a patched boot image that matches the firmware version presently installed on your Tonga. Hence, if your installed firmware build version differs from the version of the patched boot image referenced above, it is highly advised that you obtain a stock boot image that corresponds with your firmware version, patch the image with the latest Magisk app, then flash it to your Tonga via the fastboot commands outlined below.DISCLAIMER:
Rooting an Android-based mobile device is a task that encompasses inherent risks. Failure to follow the instructions as written, for example, could result in your device being rendered inoperable, stuck in a boot loop, etc. Rooting will also void any active Motorola warranty you may have on your smartphone. (However, as set forth on the Motorola support portal, your warranty is void once you complete the bootloader unlocking procedure.)
By proceeding further, you are assuming full responsibility and sole liability for the integrity and operability of your Moto G Power (2022). I am hereby absolved of any responsibility or civil liability in the event something goes wrong. Follow the instructions carefully, employ some patience, and things should go smoothly. I encourage members to read this guide in its entirety PRIOR to actually starting the steps.
INSTRUCTIONS:
Download the Minimal ADB & Fastboot tools from the link below and install it on your Windows PC or laptop. Next, open Windows File Explorer, open This PC and double click on your C: drive. Locate and open the Program Files x86 folder and locate the Minimal ADB & Fastboot folder. Copy the folder and paste it to your desktop. (Copying the folder to your desktop is not mandatory, but is recommended. This configures your ADB & Fastboot directory to a more convenient location from which to work.);
Download the Motorola Device Manager software from the link below, in accordance with your Windows OS architecture (32 or 64 bit), and install it on your PC or laptop. This software installs the most current USB device drivers for your Moto device;
Download the patched boot image below that corresponds with the Android OS & firmware build version currently running on your device. Save the image inside the ADB & Fastboot directory on your PC or laptop;
Boot your device into AP Fastboot Mode by first powering off your smartphone and then pressing Power + Volume Down simultaneously for about 8 seconds, or until AP Fastboot Mode appears on your phone display;
Connect your Tonga to your Windows computer using the OEM supplied, or a quality equivalent USB-A to USB-C data syncing/charging cable;
Open the Minimal ADB & Fastboot folder you copied to the desktop in Step 1. Double click the cmd-here file to launch a command window;
To verify proper fastboot communication between your phone and computer, execute this command:
Code:
fastboot devices
If properly connected, the command window will return with an alphanumeric string that corresponds with your device serial number;
If your serial number isn't displayed, or if you receive a Waiting message, there is an issue with fastboot mode communication between your phone and PC/laptop. Try changing USB ports, try another data syncing cable, and/or update the fastboot drivers on your PC or laptop. If your phone remains unrecognized by fastboot, skip down to the next section titled Fix Fastboot Recognition Issues, and follow those steps.
Once a proper connection has been verified, it's time to flash the patched boot image to your phone. Execute this command:
Code:
fastboot flash boot patched_boot.img
Take note that the patched boot images linked below are both named patched_boot.img. These instructions assume that you leave the filename unchanged.
Upon reboot to the Android OS, go to your app drawer and open the Magisk app or its placeholder stub. Grant any permissions requested, and follow any prompts to upgrade Magisk to the full version and complete setup of the root environment. Magisk may reboot your device to finalize the setup. If you do not see the Magisk app or the stub, download the Magisk v26.1 APK from the official Magisk GitHub repo I have linked below, and install it on your Tonga.
That's it. You should now be rooted via the Magisk systemless root solution.
FIX FASTBOOT RECOGNITION ISSUES:
This section is provided to assist members with troubleshooting device recognition issues via fastboot mode. If you have already tried a different USB-A to USB-C data syncing/charging cable, as well as a different USB port, and your Tonga persists to be unrecognized in fastboot mode, follow these steps:
Keeping your device connected to your Windows PC/laptop from Step 8 above, and ensuring your device is still in fastboot mode, right click your Windows Start icon and select Device Manager. Locate your Tonga in the menu. It will likely be located under either the Portable Devices or Android Device heading;
Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your Tonga in the Device Manager menu, the driver selection list can vary. If you see an option for Android Device or Android Phone, select either option, and then select either Android Composite ADB Interface or Android Bootloader Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface or, in the alternative, Android Bootloader Interface, and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. Return to the instructions in the previous heading and proceed to Step 9.
DOWNLOADS:
• Motorola Device Manager V2.5.4
• Minimal ADB & Fastboot Tools v1.4.3
• Official GitHub Magisk Releases
• Patched boot.img (Android 11 Stock OS)
• Patched boot.img (Android 12 Stock OS)
• Official Tonga Firmware / All Variants
THANKS & MENTIONS:
A big thanks to @sd_shadow for his excellent tutorial on Unlocking/Relocking Motorola bootloaders. Also, thanks to @jhjhjhjhjhjh for his comprehensive thread on the Moto G Power (2022), packed with specs, general info, mods & some other valuable resources for Tonga owners. Check out his thread here Moto G Power (2022)
Last but not least, a big thanks to @Needsimunlocked, for Magisk patching and sharing the stock boot image corresponding with firmware build S3RQ32.20-42-10-9-4. My Tonga is presently hard bricked, so this was of great help in my efforts to keep this guide up to date with a patched boot image from the latest available firmware package.
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Yeedatoy said:
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Click to expand...
Click to collapse
Great feedback. Thanks for sharing. I believe my next project will be fully debloating.a retail firmware package and then posting a guide for installing it via fastboot. Yes, I agree that flashing to boot_a & boot_b is not required. However, I have encountered instances where members are using way outdated fastboot binaries that don't automatically flash the active slot, so I got into the habit of instructing for both slots as a precaution. ( Even though I do provide a link for a fairly recent fastboot binary, not every member follows instructions.)
That's good info on Widevine L1 breaking on the Windows 12 update. I sure didn't know that. Thanks for the tip on a12 EX Kernel Manager as well.
Thanks again for your valuable feedback & input. I'll certainly use this info on my debloated firmware project, including that cursed live wallpaper app. Hate that RAM consuming thing.
In fact, if you could dump a super.img on your debloated setup, I would of course credit the work to you in my upcoming guide. Thanks again.
.im following everything to the T but when i flash patched_boot.img i get
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
how do i fix this?
keezeysqueezey said:
.im following everything to the T but when i flash patched_boot.img i get
View attachment 5878959
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
Click to expand...
Click to collapse
No such file
Viva La Android said:
No such file
Click to expand...
Click to collapse
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Viva La Android said:
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Click to expand...
Click to collapse
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
keezeysqueezey said:
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
Click to expand...
Click to collapse
I meant, did you install the Minimal ADB & Fastboot tools from the link I provided, or are you using another configuration of tools?
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
keezeysqueezey said:
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
Click to expand...
Click to collapse
You can't open an Android boot.img using the native Windows File Explorer. You need an image extractor such as Carliv Image Kitchen or SuperR's Kitchen. Also, both patched boot images have been thoroughly tested and verified with md5 checksums. I double-checked all files available on the links I posted. No files are corrupt.
I just downloaded and installed the Minimal ADB & Fastboot tools from my link as well with no problems.Not sure why it's showing corrupt on your system.
Ok, did you follow Step 1 entirely and copy the Minimal ADB & Fastboot folder from your C: drive and paste it to your desktop? This is the folder where you must save the patched boot image you downloaded from the link I provided.
While connected in fastboot mode, execute the following command and post the command prompt output here.
Code:
fastboot getvar all
This will let me know why fastboot is returning an Invalid partition name for the /boot partition.
< waiting for device >
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical: preloader_raw_b:no
(bootloader) is-logical: preloader_raw_a:no
(bootloader) is-logical: vendor_boot_a:no
(bootloader) is-logical : vendor_boot_b:no
(bootloader) is-logical: para:no
(bootloader) is-logical: misc:no
(bootloader) is-logical: boot_b:no
(bootloader) is-logical: metadata:no
(bootloader) is-logical: userdata:no
(bootloader) is-logical: mmcblk0:no
(bootloader) is-logical: boot_a:no
(bootloader) is-logical: md_udc:no
(bootloader) is-logical: super:no
(bootloader) is-logical: system_ext_a:yes
(bootloader) is-logical: product_a:yes
(bootloader) is-logical: vendor_a:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_ext_a-cow:yes
(bootloader) is-logical: product_a-cow:yes
(bootloader) is-logical: vendor_a-cow:yes
(bootloader) is-logical: system_a-cow:yes
(bootloader) battery-voltage:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:reloader_raw_b:0x3FF800
(bootloader) partition-size:reloader_raw_a:0x3FF800
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size: para:0x80000
(bootloader) partition-size: misc:0x80000
(bootloader) partition-size: boot_b:0x2000000
(bootloader) partition-size: metadata:0x2000000
(bootloader) partition-size: userdata:0xC26CF8000
(bootloader) partition-size: mmcblk0:0xE8F800000
(bootloader) partition-size: boot_a:0x2000000
(bootloader) partition-size: md_udc:0x169A000
(bootloader) partition-size: super:0x220000000
(bootloader) partition-size: system_ext_a:0x36CD4000
(bootloader) partition-size: product_a:0x13312B000
(bootloader) partition-size: vendor_a:0x1F6DB000
(bootloader) partition-size: system_a:0x3B5BF000
(bootloader) partition-size:system_ext_a-cow:0x132EB000
(bootloader) partition-size: product_a-cow:0x12DF6000
(bootloader) partition-size: vendor_a-cow:0x13FD1000
(bootloader) partition-size: system_a-cow:0x213B5000
(bootloader) version-vndk:31
(bootloader) has-slot: preloader_raw:yes
(bootloader) has-slot: vendor_boot:yes
(bootloader) has-slot: para:no
(bootloader) has-slot:hw:no
(bootloader) has-slot: prodpersist:no
(bootloader) has-slot: utagsBackup:no
(bootloader) has-slot: cid:no
(bootloader) has-slot: misc:no
(bootloader) has-slot:l ogs:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:utags:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:mmcblk0:no
(bootloader) has-slot:md_udc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot: product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext_a-cow:no
(bootloader) has-slot: product_a-cow:no
(bootloader) has-slot:vendor_a-cow:no
(bootloader) has-slot:system_a-cow:no
(bootloader) security-patch-level:2023-02-01
(bootloader) vendor-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) hw-revision: PVT
(bootloader) current-slot:a
(bootloader) serialno:ZY22GB5PSJ
(bootloader) product:tonga
(bootloader) version-os:12
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) version-bootloader:MBM-2.1-tonga_g-794044bf81-230129
(bootloader) unlocked:yes
all:
finished. total time: 1.691s
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Viva La Android said:
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Click to expand...
Click to collapse
awesome, thank u ! it worked , thanks again
keezeysqueezey said:
awesome, thank u ! it worked , thanks again
Click to expand...
Click to collapse
No problem friend. The problem was, the version of fastboot tools you were using does not automatically detect and flash your active slot. In such a scenario, the active slot must be specified during flashing. I realize you had trouble installing the fastboot tools I linked above and had to find tools elsewhere.
Anyway, glad you got it.
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
WoKoschekk said:
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
The Minimal ADB & Fastboot tools, while outdated, are fully sufficient for tasks such as bootloader unlocking and flashing Magisk patched boot images to achieve root. If this threat involved more in-depth command lines, such as those used in the newer dynamic FastbootD userspace mode, the platform tools would surely be needed. But for the rudimentary tasks encompassed in this guide, Minimal ADB & Fastboot works great.
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
WoKoschekk said:
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
View attachment 5880235
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your feedback and reporting the issue with the fastboot tools. I'll upload another copy and change the link.
Minimal ADB & Fastboot does indeed support A/B partitioning and automatically flashes your active boot slot without the need to specify boot_a or boot_b. That particular member had issues because he didn't use Minimal ADB & Fastboot. He used another fastboot tools implementation because, like you, he was unable to install the Minimal tools due to an error. @WoKoschekk , if you don't mind doing so, I would ask you to validate my position on this and flash your device using Minimal ADB & Fastboot using the exact instructions I have outlined. I'm 99% certain on my position but I need to be 100% sure when providing instructions in tutorials. I'm traveling and cannot test this myself or I would do it. I will post a new link for the tools shortly. Thanks again for your valuable feedback and for validating this, if you don't mind doing it. It would be a huge help.
Minimal ADB & Fastboot has been fixed and an updated link posted.
thx, can now be installed without problems
Related
Hi,
I have a HTC One M8 and I believe it is the international version (bought in Australia).
I wanted to return it to stock before selling, and it seemed to go well until I did a software update. After the update I cannot turn Wi-Fi on. The on/off switch is permanently greyed out.
I have a feeling it was because I could not match my version-main when picking the backup file. My CID is TELST001 and my version-main is 3.32.something (I don't have my computer on me).
However there was only one option to pick from which was something like 1.12
Any ideas?
Thanks, Mitch.
You can't use that very low version of backup for hboot 3.16.0000 when you have hboot 3.19.0000
The lowest you can go is one version below that is 2.23.841.1 that is for hboot 3.18.0000
Unfortunately I don't see any of Australian backup shared on XDA other than 1.xx
I have only OPTUS backup for all versions but not TELSTRA ... maybe if I have time I'll make some for TELSTRA this weekend.
Thanks for the reply.
Is there any way I could downgrade the android version such that I can use the very low version that is available for my Telstra HTC?
Not possible without S-Off.
Furthermore there's nothing much being shared for Telstra.
Would my best bet be to root the device again?
I found a "Stock Telstra WWE (Australia) ROM 2.24.841.1". Would this help? I can't link it yet.
Cheers.
If that's for M8 then that's the right one.
Yes you need custom recovery to restore backup
EDIT:
Just checked, that's for M7 not M8 don't use it.
I'll try to find time to make a backup for you.
Check back tomorrow
Meantime.. can you post your fastboot getvar all (minus serial no. & imei no.)
I need to make sure I make a right backup for your device version
Thank you, I really appreciate your assistance.
Is there anything I can do tonight that will be on the right track to fixing it? I have a buyer for the phone lined up and he wants it asap.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.841.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'll post 3.32.841.9 backup and its recovery tomorrow.
Nothing much to do now. Just flash TWRP 2.8.3.0 because you need it to restore backup
I'm having trouble flashing TWRP because it has changes since I last did it. Android Studio has come in?
Anyway I installed Android Studio but it threw an error "Failed to install Intel HAXM".
Haven't found a solution to this, and hence I cannot run Android Studio and thus cannot flash TWRP.
Or is there a simpler way to flash TWRP I am overlooking?
Thanks again.
Android Studio ? Intel HAXM ? What are those ?
Download TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
Put the downloaded openrecovery-twrp-2.8.3.0-m8.img in the same folder that you have fasboot.exe
(You have that right ? You did run fastboot getvar all before)
Put your device in bootloader/fastboot mode
Run command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
Android Studio is the package online when you wanna get the SDK, Google have hidden the normal SDK package!
OP, you want this is you need to update adb/fastboot - http://dl.google.com/android/installer_r24.0.2-windows.exe
EddyOS said:
Android Studio is the package online when you wanna get the SDK, Google have hidden the normal SDK package!
OP, you want this is you need to update adb/fastboot - http://dl.google.com/android/installer_r24.0.2-windows.exe
Click to expand...
Click to collapse
Ok .. thanks for info .. never use full SDK so don't know much about that
Okay all good, TWRP is flashed.
Haven't played with this stuff for a while so I am pretty rusty as you can see.
Cheers.
EDIT:
So theoretically all I need to do is restore from a GOOD backup which you are kindly working on creating?
Once I restore from that, should I re-lock bootloader and remove TWRP? Then do OTA updates to get it up to date software wise?
MitchellGray said:
So theoretically all I need to do is restore from a GOOD backup which you are kindly working on creating?
Once I restore from that, should I re-lock bootloader and remove TWRP? Then do OTA updates to get it up to date software wise?
Click to expand...
Click to collapse
Yes but no need to relock bootloader but it's your choice. If you do the bootloader will show RELOCKED instead of LOCKED. Unfortunately there is no update for TELSTRA currently. The last one as at today is 3.32.841.9
Gotcha.
Okay, well whatever the latest version is works for me. Or will updating the version conflict with the backup file you are going to share?
MitchellGray said:
Gotcha.
Okay, well whatever the latest version is works for me. Or will updating the version conflict with the backup file you are going to share?
Click to expand...
Click to collapse
No conflict as this is a clean non rooted stock backup for Telstra
Below is the general steps. You just skip what ever that already done.
1. Install TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
2. Download TWRP backup 3.32.841.9 - https://mega.co.nz/#!EJ4TxBYa!qtV7OUIBWmqtWD6KFlQcSUGkerLpNUsA5C4yj6QEQ7c
3. Download stock 3.32.841.9 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/3.32.841.9_recovery.img/download
4. Extract the downloaded 3.32.841.9_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.841.9 folder (not 3.32.841.9_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./3.32.841.9
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.841.9_recovery.img
12. reboot - check for OTA, download, install (if any)
13. done
Optional : to relock bootloader, boot to bootloader/fasboot - run command fastboot oem lock
Gotta go now ... be back in 3 hrs
ckpv5 said:
No conflict as this is a clean non rooted stock backup for Telstra
Below is the general steps. You just skip what ever that already done.
1. Install TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
2. Download TWRP backup 3.32.841.9 - https://mega.co.nz/#!EJ4TxBYa!qtV7OUIBWmqtWD6KFlQcSUGkerLpNUsA5C4yj6QEQ7c
3. Download stock 3.32.841.9 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/3.32.841.9_recovery.img/download
4. Extract the downloaded 3.32.841.9_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.841.9 folder (not 3.32.841.9_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./3.32.841.9
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.841.9_recovery.img
12. reboot - check for OTA, download, install (if any)
13. done
Optional : to relock bootloader, boot to bootloader/fasboot - run command fastboot oem lock
Gotta go now ... be back in 3 hrs
Click to expand...
Click to collapse
oh my god is that TWRP backup the one you built for my version? Thank you so much.
All done. Phone is up to date and everything is functioning perfectly.
Cannot thank you enough ckpv5.
Great :good::good:
Glad to help
ckpv5 said:
Ok .. thanks for info .. never use full SDK so don't know much about that
Click to expand...
Click to collapse
Its so much easier to install adb/fastboot with one of the "minimal" install packages available on XDA.
Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)
Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?
No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.
running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
The files from my guide should work with your device.
so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?
Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU
Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK
Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip
Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.
Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna work.
Dear all,
After I flashed my HTC One M8 with a custom ROM (btw I did everything by the book according to Hasoon's All in one kit.) WI-FI doesn't work, it won't turn on.
Recovery: It was TWRP at first, but then I tried clockworkmod as well, after several flashing with other custom ROMs it still won't turn on.
Can you help me find out what the problem is?
Note: After several flashing attemps, although it was rooted at first, my phone somehow got unrooted.
Your firmware is outdated.
You need a 4.xx.xxx.x or 6.xx.xxx.x firmware to have a working wifi.
Check your bootloader, you should see the OS- no. there. If it is blank because you used an outdated recovery, see the hboot version .. must have 3.19.0000
I checked and this is what I have found:
***Tampered***
***Unlocked***
S-On
Hboot : 3.16.0.0000
OS - this area is blank
But I also checked my firmware number it starts with 6.xxxxxx
6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.
ckpv5 said:
6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.
Click to expand...
Click to collapse
Getvar results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.153s
I added the getvar all results. Unfortunately I don't have the non-rooted backup :/
And I'm sorry I'm new to this all. What exactly is sn OTA or RUU and how do I do it?
ongunpitir said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.
ckpv5 said:
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.
Click to expand...
Click to collapse
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?
kiuqxy said:
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?
Click to expand...
Click to collapse
This is usually due to your PC's configuration. Win7 and USB 2.0 for the best chance of compatibility.
I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.
ongunpitir said:
I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.
Click to expand...
Click to collapse
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.
ckpv5 said:
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.
Click to expand...
Click to collapse
I tried what you said this is what gives me;
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>htc_fastboot flash zip rom.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 4.28.502.2
found large-zip header, file count: 6
processing file 1/6...
sending 'zip' (57600 KB)...
OKAY [ 2.748s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Process Process-1:
Traceback (most recent call last):
File "C:\Python34\lib\multiprocessing\process.py", line 254, in _bootstrap
File "C:\Python34\lib\multiprocessing\process.py", line 93, in run
File "E:\largezip\htc_fastboot\htc_flashzip.py", line 207, in _do_extract
File "E:\largezip\htc_fastboot\largezip.py", line 61, in extract
MemoryError
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 16.911s
htc_fastboot finished. total time: 18.191s
C:\adb>
BTW, i wouldnt rely on toolkits either to flash the M8, should always be done manually either thru recovery methods, RUU or Fastboot, i never use any of the avail toolkits to flash anything.
ongunpitir said:
I tried what you said this is what gives me;
FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)
ckpv5 said:
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
View attachment 3711349
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)
Click to expand...
Click to collapse
Thank you so much! After many failures, I have finally managed to make it work. After relocking my device and flashing with a RUU using command prompt option, it finally worked. Now I can use my wifi again. Now I will try to flash a custom ROM, but you said I need to update my firmware right? So how do I do that? Or have I just updated it already by flashing the latest RUU?
Thanks in advance
The RUU already updated your firmware to the latest ... but still a Lollipop as there is no Marshmallow update for AT&T yet but that should be enough for now, your wifi should work on any custom ROM.
Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.
Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU
ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.
I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help
Pardon
Now that saw the second message. I will perform this procedure now
Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again
ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.
I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?
In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM