Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
{
"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"
}
kvas said:
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
Click to expand...
Click to collapse
Pics wont appear in thread from hosting
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
I thought I came across a tutorial somewhere that allows USB debugging to be bypassed
Phalanx7621 said:
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
Click to expand...
Click to collapse
Is there an option to enable USB debugging mode in recovery or through ADB? I can't even remember if I had debugging mode enabled.... My device was shipped through Verizon in Oct 2016, so it is bootloader locked anyway... It seems to be communicating with my laptop in CMD adp sideload, but Im not 100% sure.
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Thanks for the reply!
altwu said:
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Click to expand...
Click to collapse
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
kvas said:
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
Click to expand...
Click to collapse
there are 2 methods to flash android to your phone.
flash the factory image. the factory image zip contains a script that takes care of the flashing. it's basically several fastboot commands. to prevent data from getting wiped, the script needs to be edited to remove the -w option from the last fastboot command. the instructions you've seen that mention this are ones for flashing a factory image. but your bootloader needs to be unlocked to do this. since yours isn't, this isn't an option for you.
flash the ota zip. this is done with an adb sideload command. according to google's ota page(http://developers.google.com/android/ota), "This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." unlike flashing a full factory image, no extra steps are needed to prevent data from getting wiped.
i don't think one option is better than the other. some people here prefer to flash the ota, others prefer to flash the full factory image. i've been going with the factory image route ever since nougat and i can confirm that the script edit needed to prevent a data wipe works. but for you, since your bootloader is locked, you have only one option and that's to flash an ota. the instructions for flashing an ota are on google's ota page that i gave a link to or in the guide i mentioned in my previous reply.
Yup, that explains it. I wasn't clear about the instructions of the OTA method because on the developers site for Google it both talks about sideloading and enabling usb debugging in the options menu. Since I can't access my setting because my phone is soft bricked I have to use sideloader through the ADB. What I am also not clear on is the OTA for my situation. I gathered that the OTA flash was for Pixels that wouldnt take and update in a non-soft bricked phone. At this point I have no choice but to try. I talked to someone at Google and he sat on the phone for over an hour and a half with me helping me research this method. (THANKS GOOGLE))). Although I read that after the last Pie update many peoples phones became bricked so at least it shows they care. I just hope the OTA flash is provisioned for a soft bricked device. But in this business I realize nothing is guaranteed. I just wish I could locate someone who tried this on thier device so they could give some pointers....
We can all agree, if your phone is bootloader LOCKED do not do a factory flash if attempting to retain any data. Editing the script (-W) will only work with a bootloader UNLOCKED device. Long live the Pixel
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
kvas said:
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
Click to expand...
Click to collapse
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
sb1893 said:
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
Click to expand...
Click to collapse
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
sb1893 said:
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
Click to expand...
Click to collapse
You guys make the XDA community look good.
kudos to each of you.
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
kvas said:
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
Click to expand...
Click to collapse
Bummer - that stinks. Sounds like we are close. Out of curiousity - can you post the exact/full text (or a picture if you have a camera or second device) of that screen that shows "Your data may be corrupt"...the only "corrupt" message I am familiar with is from the Bootloader unlocked warning screen. So - want to see what specific error message you are getting.
Sorry again you weren't able to recover your device.
I tried to post a all the pictures I have taken, but the hosting site wont show them. Is there a better way to show the pics?
I just attach pics using the reply screen...Like this....
sb1893 said:
I just attach pics using the reply screen...Like this....
Click to expand...
Click to collapse
Hopefully this works... Google Pixel XL flashing OTA
kvas said:
Hopefully this works... Google Pixel XL flashing OTA
Click to expand...
Click to collapse
So you power up the device and it works on booting for a little while and then immediately drops you into that recovery screen? It doesn't give you a message when the boot fails before launching recovery?
Also - that OTA file looks to be the August 2018 OTA file, not September 2018 - which is what I thought you were trying to sideload...
I did end up flashing the latest OTA.. It let both of them install. I flashed the same one on my phone, then I flashed the newest on on the list of google developers site. PPR2. 180905.006.A1. That is what is has now. I am still stumped as to why it won't work. I'm sure it needs a full factory flash, but I cant do it because its locked. So even if I wanted to recover the files I can't. Even if I could recover the files somehow without further flashing the files would be encrypted and useless. I could either wait to see if another option is available in the future, or factory reset it losing all my precious files. Extremely frustrating. Also, Why didnt google send me a notice about the September update? I never updated this month. Probably why it froze while in Hangouts
Disclaimer: This WILL void your warranty. I am not liable for breaking/bricking your phone, you losing your data, or any nuclear war/other catastrophe. This process WILL totally wipe all data on your phone. Make sure you have a backup! You will also forever see "bad key" displayed in the top left of your screen for a few seconds after a reboot after unlocking the bootloader. There is currently no way around this that I'm aware of (let me know if you have a way)
This guide was assembled from mingkee's G7 guide here: https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
You will need:
1. Your Moto G7 Power (Any hardware version, any carrier, but running Android 9 Pie)
2. A stock boot.img for your hardware version, here are the two that I have. You can just extract the boot.img from a stock ROM for a hardware version not listed, although I'm not sure it actually matters which one you use. Experiment at your own risk.
XT1955-5 US: https://mega.nz/#!L0sHzSKY!323GrDQ8BTsPmKvrSoU7DV-2kJuVris0cWN8Xt3u_6o
XT1955-2 LATAM: https://mega.nz/#!uk912I4B!12_EgPML2l5sIXDeDGVqiVDB2RwA6iF6-H-mivNecOo
(Full stock ROM's for both versions will be linked in the next post. )
3. A USB cable to connect your G7 to a computer
4. Motorola USB drivers: https://support.motorola.com/uk/en/...moto-g-family/moto-g7-power/documents/MS98028
4. Your bootloader unlock code from Motorola, more on that below
5. Android SDK
Step 1: Unlocking the bootloader
First we'll need to unlock the bootloader, to do this, you'll need your unlock code from Motorola:
https://support.motorola.com/us/en/bootloader
Note that this will require you to register your device with Motorola, and this WILL void your warranty.
Then, download and install the Motorola USB drivers (link above), you may need to reboot your computer after installation.
Next you'll need to download and extract/install the Android SDK
https://developer.android.com/studio/index.html#downloads
Note that you'll only need the "command line tools" for this guide, unless you really want the whole SDK (huge).
Extract the command line tools to anywhere really, C:\Android is fine for Windows. If you downloaded/installed the whole sdk, the tools you need will be in C:\Users\[your username]\AppData\Local\Android\Sdk\platform-tools
Once you have that, open up a powershell window in your tools folder by holding Shift and right-clicking in the folder.
Now, reboot your G7 to fastboot mode by powering off, then holding power+volume down until you're in the bootloader. Now, connect your G7 to your computer with your USB cable.
In powershell, verify your device is recognized by typing "./fastboot devices". Your G7 should show up by its serial number.
Now, type "./fastboot oem unlock [your motorola unlock code]". THIS WILL WIPE ALL DATA ON YOUR PHONE. After that, use the volume up and down buttons and then the power key to restart the bootloader. You should now see "flashing_unlocked" at the bottom of the bootloader screen. Now use the volume/power buttons to select "start" to boot the phone. You will see "bad key" displayed in the top left corner of the screen. This is normal. The phone should boot and bring you to the Android set up wizard. Go ahead and set up the phone as you normally would.
Note that at this time, if you go to "Update" in system settings, it may warn you that "system integrity is compromised" and that you will no longer receive OTA updates. This is also normal, we'll fix that in a bit.
Step 2: Rooting
Now that we have an unlocked bootloader, we can flash things to the phone through fastboot (at the time of this writing, TWRP or other custom recoveries are not available for the G7 Power. Once it is, you can use that to flash the Magisk .zip file instead of using powershell).
Copy the correct *_boot.img for your hardware version to a folder on your phone. I used the downloads folder. (not too sure if the version makes a difference; I was able to flash the entire US XT1955-5 firmware/rom to my Latin America XT1955-2 without a problem, but experiment at your own risk)
Download and install the Magisk Manager APK through Chrome or browser of your choice on your G7
https://github.com/topjohnwu/Magisk/releases
It will ask you if you want to allow [your browser] to install things from unknown sources. Say yes.
Then, open Magisk Manager and tap "Install". Then tap "patch boot image file". Select the *_boot.img you copied earlier and let it run. It will tell you when its done.
Once it completes, copy the patched *_boot.img back to your computer and place it in the same folder as your Android SDK tools (where fastboot.exe and adb.exe live)
Now power off the phone then boot to fastboot, again by holding power + volume down until the bootloader appears.
Now in powershell, type "./fastboot flash boot [the name of your patched boot.img].img" and hit enter. Alternatively, type "./fastboot flash boot" then hit space, then drag your patched *_boot.img into powershell and hit enter.
(Note, if you get an error saying "Invalid partition name boot__a" like I did, add a "_a" to "boot" ie "./fastboot flash boot_a [the name of your patched boot.img]" instead. )
Powershell should tell you "Image signed with key bad key". This is normal.
Now use the volume up/down buttons and power button to start the phone.
Once booted, load up Magisk Manager again. You should see all green checkmarks. Congrats, your G7 is now rooted! One last thing:
Tap where Magisk says "tap to start SafetyNet check". This tests to see if its able to fool Google's checks and let you install OTA updates or use Android Pay. If you did everything properly, this should all check out fine. Confirm by going into Updates in System Settings and verifying that you are up-to-date and it doesnt say anything about "device integrity compromised".
Thanks to everyone who's work I shamelessly paraphrased. I wanted to make a concise guide specifically for the G7 power as I didn't find much online regarding it. (And the stock US rom was ridiculously hard to find and acquire). I'll link stock US and Latin America G7 Power firmwares/roms in the post below in case anyone wants to go back to stock, once the upload finishes. Note: there is no known way at the time of this writing that you can ever get rid of "bad key" being displayed at boot once you unlock the bootloader (again, if anyone knows how, let me know! Thanks!)
gedster314 linked me to a site in another thread where stock ROMS for a lot of devices can be found, including the XT1955 (codename: Ocean).
https://mirrors.lolinet.com/firmware/moto/ocean/official/
"RETUS" on that page would signify "Retail, US"
until some good custom roms will pop out i don't have needs to unlick/root...
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Baby steps my friend.
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Got everything to work! Flashed Tethering Enabler too. Thank you!
nucher said:
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
Click to expand...
Click to collapse
There's one more reason to root: CF Lumen
I want all devices have same exactly same white tone.
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
turboyo said:
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
Click to expand...
Click to collapse
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
diversenerd said:
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
Click to expand...
Click to collapse
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
turboyo said:
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
Click to expand...
Click to collapse
I was wrong in my first thread, my -2 does NOT have NFC. Heres the newly minted LTE Band unlocking guide: https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-enable-lte-t3925246
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Darkstarsx said:
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Click to expand...
Click to collapse
What kind of issues? I haven't noticed any ill effects of rooting with this method.
my touchscreen is not working at all after the rooting step. how do i fix this?
jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Try rolling back to stock with my other guide. Then try again.
Thanks for the guide, phone is now rooted. Is it safe to do a factory reset to be able to start the phone set up again to automatically download apps, settings, etc from Google? If not, is there another, better way to do that?
diversenerd said:
Try rolling back to stock with my other guide. Then try again.
Click to expand...
Click to collapse
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Chickenaa said:
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
Click to expand...
Click to collapse
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Poto222 said:
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Click to expand...
Click to collapse
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Chickenaa said:
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Click to expand...
Click to collapse
Someone on the Telegram group has a working TWRP build, he said he'll be posting it soon.
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.