Develop Bugs

[Guide] Re-lock and Un-root WI-FI Xoom Build HWI69

This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com

first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse

HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally

I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while

I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?

Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work

I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update

what format are these imgs in?
I am trying to unyaffs them but it is not the right format

Your trying to what?

The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk

I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.

Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?

worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..

yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...

Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.

Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt

Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s

[GUIDE][FIX]Cant unlock bootloader? Read here for a Fix

Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.

That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k

I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?

cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.

edit: nvm...

Both download links link to the same file. splashscreen.img

Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love

jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...

MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.

This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)

I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated

PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.

rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?

error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830

im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?

Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.

Return LG Nexus 5X to original Google ROM

Hello,
I have an LG Nexus 5X (Bullhead?) running PA 7.3.1-RELEASE (Android 7.1.2). It had PA installed on it when I purchased it from ebay some six months ago.
I really would like to go back to the original Google ROM but am struggling to do this.
I've downloaded SuperSU but when I run it I get "SuperSU SU Binary is occupied" and a "HOW TO SOLVE" button.
Clicking "HOW TO SOLVE" takes me to www supersu dot com faq subinaryoccupied which reassures me that: "Only needs a coffee's time to make it happen" and a Community link and Message Us link. Community Link returns a 502 Bad Gateway response (not very reassuring!), the Message Us link goes to a facebook group (SuperSUofficial). Is this route even worth entertaining? I feel I'm only at the tip of the iceberg in getting my phone returned to factory/OEM status.
Any advise would be most appreciated. (Sorry ,not allowed to post links as I'm under the 10 posts requirement)
Thanks, BloodBaz

Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp, that looks like exactly what I need. I'll give this a go this week and let you know how I get on. Thank you.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp. I'm struggling at the very first step.
Here's where I'm at:
Step 10 (How To Flash The Factory Images (And Return To Stock)) has the prerequsite that I have to unlock bootloader (section 1).
Gone to section 1
Enabled Developer mode (was already enabled)
Enabled OEM unlocking
Enabled USB debugging
Powered off phone
Booted into Bootloader (Power+Volume Down)
Connected phone to PC via USB cable
Opened command prompt, gone to platform tools but as you can see, I'm not connecting here:
Code:
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>adb devices
List of devices attached
00cad250a0599972 device
C:\android\platform-tools>fastboot reboot
< waiting for any device >
My PC is the latest Windows 10 Pro (64-bit).
I have an LG Nexus 5X (Model LGH791).
And I'm guessing I've not got the right drivers installed but I'm struggling to find where to get them (I'm in the UK)
Here's where I've tried:
Attempt 1:
Followed the same guide to "Google USB Driver Install": https://developer.android.com/studio/run/win-usb.html
which takes me to: "Click here to download the Google USB Driver ZIP file (ZIP)" (latest_usb_driver_winodws.zip 8.3MB).
Downloaded, unzipped.
Gone to Device Manager but my phone doesn't appear under "Portable Devices" or anywhere else in device manager.
Attempt 2:
Gone to LG's website, entered model which lead to this page:
https://www.lg.com/uk/support/softw...00008356&subCateId=CT00008358&modelNum=LGH791
(but alas, no software!)
Can anyone advise on how to get the phone and PC to communicate?
Thanks
Chris

You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.

Jacquestrapp said:
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Click to expand...
Click to collapse
Thanks, yes it does! Sorry, I not good at this. So the pre-req for section 10 is already done.
(I'm assuming I will still need to get adb / fastboot working at some point though).
I'll start looking into section 10 now. Thanks.

Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.

Jacquestrapp said:
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Click to expand...
Click to collapse
No, directly onto USB port on top of PC. Tried both ports on top and a USB 3 port in the back. Still no sign of the phone in Device Manager.
I've got a laptop - I will try that next.
After that I will install the Android SDK manager (although I was hoping to avoid this for a one off job).
Thanks.

Okay, so I *think* my laptop is recognising the phone, however I still don't see the phone under Device Manager > Portable Devices or Device Manager > Other Devices (in fact, neither folder exists on my Laptop in Device Manager). However I have got "Nexus 5X" listed under Device Manager > USB Devices.
I'm now following instructions in section 10 of the guide you have given me:
"Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here (https://developers.google.com/android/nexus/images?hl=en)".
For me this is 8.1.0 (OPM7.181005.003, Oct 2018) under "bullhead" (https://dl.google.com/dl/android/aosp/bullhead-opm7.181005.003-factory-e23fac1c.zip)
I've done the appropriate unzips and copies and I have the following folder set up:
Code:
Volume in drive C has no label.
Volume Serial Number is 1202-7717
Directory of C:\android\images
19/10/2018 22:55 <DIR> .
19/10/2018 22:55 <DIR> ..
01/01/2009 00:00 101 android-info.txt
01/01/2009 00:00 12,068,070 boot.img
21/09/2018 12:04 4,731,396 bootloader-bullhead-bhz31b.img
21/09/2018 12:04 57,989,632 radio-bullhead-m8994f-2.6.41.5.01.img
01/01/2009 00:00 17,847,530 recovery.img
01/01/2009 00:00 2,002,471,632 system.img
01/01/2009 00:00 194,892,768 vendor.img
7 File(s) 2,290,001,129 bytes
2 Dir(s) 136,452,927,488 bytes free
C:\android\images>
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Booting up the phone and disconnecting and connecting the phone a couple of times re-established the device. This time I was able to run adb reboot bootloader but as soon as the phone starts to shut down for the reboot, the connection to the laptop is lost and the laptop shows an error popup (temporarily) (wish I knew how to keep the popup visible but it was something about an error with the USB device).
Q3) Should I select RECOVERY MODE before I can expect the USB connection to reconnect? Documentation just says to go into bootloader (with the menu)
Any more advice is appreciated. Thanks, Chris

BloodBaz said:
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Click to expand...
Click to collapse
That last command should be fastboot devices, not adb devices.
BloodBaz said:
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Click to expand...
Click to collapse
Yes, but using fastboot commands, not adb commands. With the phone in bootloader mode (the green screen with the big Start sign), you should see it listed after the fastboot devices command. Here's what I see:
Code:
C:\adb>fastboot devices
00bc94d02c6ab546 fastboot
BloodBaz said:
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Click to expand...
Click to collapse
The phone's type-C port can collect lint, and plugging the connector into the phone compacts the lint. Over time, the lint layer can build up to the point where the connector no longer makes full contact with the port. I don't think that's your problem though.

@Jacquestrapp, thank you for your replies. You've been a life line.
After a couple of hours I think I've now managed to do it. I've tried two laptops, multiple USB ports and two USB cables. Whatever is happening, the PC/Phone connection seems very tempremental and I have to unplug and replug in the USB cable after each reboot. However, as you say, the fastboot commands did work after I figured this out, and from the fastboot screen. Also, whenever the phone rebooted or I disconnected the USB cable, the error message was as per attached screenshot.
So, I ran the following commands:
Code:
C:\android\platform-tools>adb devices -l
List of devices attached
00cad250a0599972 recovery product:omni_bullhead model:Nexus_5X device:bullhead transport_id:5
C:\android\platform-tools>fastboot flash bootloader C:\android\images\bootloader-bullhead-bhz31b.img
< waiting for any device >
Sending 'bootloader' (4620 KB) OKAY [ 0.212s]
Writing 'bootloader' OKAY [ 0.238s]
Finished. Total time: 0.493s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\android\platform-tools>fastboot flash radio C:\android\images\radio-bullhead-m8994f-2.6.41.5.01.img
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 1.633s]
Writing 'radio' OKAY [ 0.543s]
Finished. Total time: 2.300s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.014s
C:\android\platform-tools>fastboot flash boot C:\android\images\boot.img
< waiting for any device >
Sending 'boot' (11785 KB) OKAY [ 0.538s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.786s
C:\android\platform-tools>
C:\android\platform-tools>fastboot flash recovery C:\android\images\recovery.img
Sending 'recovery' (17429 KB) OKAY [ 0.545s]
Writing 'recovery' OKAY [ 0.309s]
Finished. Total time: 0.900s
C:\android\platform-tools>fastboot flash system C:\android\images\system.img
Sending sparse 'system' 1/4 (508768 KB) OKAY [ 13.739s]
Writing sparse 'system' 1/4 OKAY [ 9.283s]
Sending sparse 'system' 2/4 (524230 KB) OKAY [ 14.787s]
Writing sparse 'system' 2/4 OKAY [ 8.650s]
Sending sparse 'system' 3/4 (501070 KB) OKAY [ 14.592s]
Writing sparse 'system' 3/4 OKAY [ 12.445s]
Sending sparse 'system' 4/4 (421469 KB) OKAY [ 11.842s]
Writing sparse 'system' 4/4 OKAY [ 16.174s]
Finished. Total time: 112.698s
C:\android\platform-tools>fastboot flash vendor C:\android\images\vendor.img
Sending 'vendor' (190324 KB) OKAY [ 5.424s]
Writing 'vendor' OKAY [ 5.682s]
Finished. Total time: 11.145s
C:\android\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
The pre-google animation too ages and eventually talked about corruption on the filesystem. This is presumably because it had Paranoid Android installed on it previously. So I took the option to wipe everything (I don't have anything precious on the phone that isn't already backed up) and I've got myself back to stock Google and I'm very happy!
Thanks again for your support @Jacquestrapp.
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks

BloodBaz said:
[MENTION=301158]
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
Click to expand...
Click to collapse
You're welcome. I *think* you are OK to re-lock the bootloader, but I've never done it, so I can't say with 100% certainty. Both of the 5Xs in my house have been running custom ROMs since I bought them. Also, if the USB connection is as temperamental as you say, take a toothpick (or something else thin and non-conductive) and poke around gently in the USB port to see if lint is the problem. It probably isn't, but it's easy enough to fix if it is: just dig all the lint out.

Moto Z2 force constantly bootlooping, Stock rom load but NO Wi-FI or Cellular network

I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.

sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.

41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------

sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?

41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance

You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?

sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked

Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>

sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?

Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!

sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?

I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit

sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash

Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse

Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s

sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.

Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.

I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.

sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B

Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.