So it seems that we are having the first (hope soft...) bricks here... :crying:
I think it could be interesting for ALL sharing HOW you brick it with details, so others can avoid to do same errors.
Eventually would be even more interesting how you have recovered from your brick status (if you...:fingers-crossed with detailed guide...
I think that having all in a single thread could be very useful, so... share your (bad) experiences...
Flashed the rogers firmware on my retapac moto z then updated to us version nougat. Root didnt work so flashed back to rogers mm. Not booting anymore. Not flashing anything nor side loading since cant downgrade bl and gpt. Nougat sideload refuses because it sees device as already on new firmware.
So edited the flashfile.xml on rogers mm firmware. Removed the bootloader and gpt flash and reflashed partial mm system. Sideloaded nougat again and everything went perfect.
i23u8 said:
Flashed the rogers firmware on my retapac moto z then updated to us version nougat. Root didnt work so flashed back to rogers mm. Not booting anymore. Not flashing anything nor side loading since cant downgrade bl and gpt. Nougat sideload refuses because it sees device as already on new firmware.
So edited the flashfile.xml on rogers mm firmware. Removed the bootloader and gpt flash and reflashed partial mm system. Sideloaded nougat again and everything went perfect.
Click to expand...
Click to collapse
Can you help me? I tried installing twrp and when I finally got it, it started looping on the unlocked bootloader screen, I already tried everything, I installed custom roms by twrp and even the stock rom by commands I saw in another topic (http: // forum. Xda-developers.com/moto-z/help/help-phone-bricked-t3499573) but it seems that nothing happens and I still stay on the screen or bootloader or on that warns that the phone has been unlocked and can not be trusted .
I had upped some images to show my problem
http://imgur.com/Zm1Mja5
http://imgur.com/bgoGwQQ
Sorry for my bad english, I really need help
rogerxcamargo said:
Can you help me? I tried installing twrp and when I finally got it, it started looping on the unlocked bootloader screen, I already tried everything, I installed custom roms by twrp and even the stock rom by commands I saw in another topic (http: // forum. Xda-developers.com/moto-z/help/help-phone-bricked-t3499573) but it seems that nothing happens and I still stay on the screen or bootloader or on that warns that the phone has been unlocked and can not be trusted .
I had upped some images to show my problem
http://imgur.com/Zm1Mja5
http://imgur.com/bgoGwQQ
Sorry for my bad english, I really need help
Click to expand...
Click to collapse
The warning message is normal. So what happens when you go to Recovery mode. When you installed twrp, you executed both fastboot flash recovery twrp.img and fastboot boot twrp.img? So it boots directly to twrp.
So if you're upgrading to nougat, the sequence should be:
Go to bootloader screen.
Flash rogers MM firmware thru rsd lite.
Go to bootloader screen again and select recovery.
Choose adb sideload.
Type the command to sideload the nougat firmware.
Optionals are install twrp, install the odexed custom nougat firmware from the other thread, and root.
i have no more access to fastboot or recovery after flashing retmx nougat on my device. my pc recognizes the qualcomm device and i've already installed drivers for it. but i need the files to flash the stock rom including bootloader. (please also have a look to my post in the other thread http://forum.xda-developers.com/showpost.php?p=70014076&postcount=21)
M!tch said:
i have no more access to fastboot or recovery after flashing retmx nougat on my device....
Click to expand...
Click to collapse
Could you explain better what steps have you done exactly (to brick...)?
i came from latest marshmallow with unlocked bootloader and rooted. because the ota didn't work i flashed stock marshmallow reteu via fastboot and loaded the ota again via the update menu in settings. it failed again. therefore i flashed stock nougat retmx via fastboot. the result was a black screen and only an unknown device named "qusb_bulk" at the windows device manager. meanwhile i've installed qualcomm drivers and qfil but still need the right files for my xt1650.
M!tch said:
i came from latest marshmallow with unlocked bootloader and rooted. because the ota didn't work i flashed stock marshmallow reteu via fastboot and loaded the ota again via the update menu in settings. it failed again. therefore i flashed stock nougat retmx via fastboot. the result was a black screen and only an unknown device named "qusb_bulk" at the windows device manager. meanwhile i've installed qualcomm drivers and qfil but still need the right files for my xt1650.
Click to expand...
Click to collapse
Is rsd lite still seeing your device? There are full firmware files somewhere here in the forums. Or do you only need bootloader and boot img files?
rsd lite is just using fastboot. i need the files for qfil. (rawprogram0.xml and patch0.xml)
I came fresh out the box xt1650-03 and was trying to get twrp (which worked) and then root which failed. So installed on of these ROMS that had root and maybe even the 7.0. Now I just get the your devices is unlocked screen and nothing else. I just want to get back to the way it came but cannot get RSD to see my phone. Any help or ideas?
i23u8 said:
The warning message is normal. So what happens when you go to Recovery mode. When you installed twrp, you executed both fastboot flash recovery twrp.img and fastboot boot twrp.img? So it boots directly to twrp.
So if you're upgrading to nougat, the sequence should be:
Go to bootloader screen.
Flash rogers MM firmware thru rsd lite.
Go to bootloader screen again and select recovery.
Choose adb sideload.
Type the command to sideload the nougat firmware.
Optionals are install twrp, install the odexed custom nougat firmware from the other thread, and root.
Click to expand...
Click to collapse
I managed to get into recovery mode, if I remember correctly I had upgraded my nougat before this whole problem.
Unfortunately I do not know why but I can not get my phone to be identified by rsd lite, is there any tutorial by xda?
I tried installing odexed custom nougar firmware and root by twrp but it is restarting in looping in the screen of "your device can not be trusted"
i23u8 said:
Is rsd lite still seeing your device? There are full firmware files somewhere here in the forums. Or do you only need bootloader and boot img files?
Click to expand...
Click to collapse
I can get RSD to see it now so I need a full firmware but cannot find it my search skill must be week
OK i can see it in fastboot but cannot do anything else
this is what i see
ryanwv24 said:
OK i can see it in fastboot but cannot do anything else
this is what i see
Click to expand...
Click to collapse
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
rogerxcamargo said:
I managed to get into recovery mode, if I remember correctly I had upgraded my nougat before this whole problem.
Unfortunately I do not know why but I can not get my phone to be identified by rsd lite, is there any tutorial by xda?
I tried installing odexed custom nougar firmware and root by twrp but it is restarting in looping in the screen of "your device can not be trusted"
Click to expand...
Click to collapse
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.
i23u8 said:
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.
Click to expand...
Click to collapse
I do not know what I did but it is working now.
build MPL24.246-45
Baseband M8996_1227.36.01.115.01R SRS
kernel 3.18.24-perf-g0c28d32
[email protected]#1
Why the lack of updates on this phone?
Wed Aug 31
As Peter Griffin says - if they're not giving it to you, you probably don't need it. Remember these large groups of men know what's best for you.
Seriously though, there might be tons of unique adoptions to the phone that need time to port?
CM14.1 was out a week ago but Moto Mods aren't working and that's 50% of the phone not working.
i23u8 said:
Your BL (90.xx) is still in MM, Nougat is 91.xx. You can still rsd the MM firmware for your region.
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Can you look at BL version? 90.xx and you are still on MM and you can rsd to stock MM. 91.xx and you will have to sideload the nougat firmware.
Click to expand...
Click to collapse
BL on bootloader is showing 91.05, sorry but how i sideload nougat firmware?
rogerxcamargo said:
BL on bootloader is showing 91.05, sorry but how i sideload nougat firmware?
Click to expand...
Click to collapse
You should be on the roger firmware, goto bootloader and select recovery mode. Select adb sideload from the recovery menu.
i23u8 said:
You should be on the roger firmware, goto bootloader and select recovery mode. Select adb sideload from the recovery menu.
Click to expand...
Click to collapse
When i try to use adb sideload appears a error "loading Blur_Version.24.21.46.griffin.retail.en.US.zip" and then "* cannot read Blur_Version.24.21.46.griffin.retail.en.US.zip"
when i try to update from SD card appears a error "Internal and external memory cannot be mounted"
rogerxcamargo said:
When i try to use adb sideload appears a error "loading Blur_Version.24.21.46.griffin.retail.en.US.zip" and then "* cannot read Blur_Version.24.21.46.griffin.retail.en.US.zip"
when i try to update from SD card appears a error "Internal and external memory cannot be mounted"
Click to expand...
Click to collapse
Can you try and open the zip on your pc and extract all contents in a directory? Just to make sure it isnt corrupt? Also, there are 2 versions of the file, one international and the other US, I used the international variant file.
Related
Here is TWRP for the Mediapad X2. TWRP lets you back up your stock ROM or flash custom Roms. You must already be on B112 or higher to flash this or you'll bootloop.
TWRP:
https://www.androidfilehost.com/?fid=674106145207489444
CHANGELOGS:
12-3-15: Changed over to English and added cool new Splash Screen
7-23-16: Updated to TWRP 3.0.0-2. (Android 6.0 compatible) and added a black & blue Theme and bunch of languages. You can now back up your cust in twrp as well.
9-16-17: TWRP updated to 3.1.1-0.
5-26-18: Updated to TWRP 3.2.1-0. Battery charge level now shown in status bar. You can flash OemInfo images now.
ajsmsg78 said:
Here is the latest TWRP Recovery for Android 5.1.1. TWRP lets you back up your stock ROM or flash custom ROMS.
1) You must have an unlocked bootloader to flash this. Once flashed you can root easily. You can follow my guide here:
http://forum.xda-developers.com/mediapad-x2/general/mediapad-x2-unlock-bootloader-root-guide-t3212325
2) To use. extract the files then flash the twrp_cn.img in Fastboot (fastboot flash recovery twrp_cn.img) or double click the run.bat and follow the instructions.
I am not responsible if anything happens to your device or if your house burns down This has been tested on the 703L only. Use it on other models at your own risk.
https://www.dropbox.com/s/uqbkskpz8niqyzm/X2_TWRP_CN_5.1.1_kangvip.rar?dl=0
Click to expand...
Click to collapse
This is what I was looking for.
ajsmsg78 said:
Here is the latest TWRP Recovery for Android 5.1.1. TWRP lets you back up your stock ROM or flash custom ROMS.
1) You must have an unlocked bootloader to flash this. Once flashed you can root easily. You can follow my guide here:
http://forum.xda-developers.com/mediapad-x2/general/mediapad-x2-unlock-bootloader-root-guide-t3212325
2) To use. extract the files then flash the twrp_cn.img in Fastboot (fastboot flash recovery twrp_cn.img) or double click the run.bat and follow the instructions.
I am not responsible if anything happens to your device or if your house burns down This has been tested on the 703L only. Use it on other models at your own risk.
https://www.dropbox.com/s/uqbkskpz8niqyzm/X2_TWRP_CN_5.1.1_kangvip.rar?dl=0
Click to expand...
Click to collapse
I'm on b106 stock now.... how do I get my phone into bootloader or fastboot now? Update won't let me do incremental updates either... No incremental update button to manually update to 107 and 108. Thx for any help you can give me...
Steamer2499 said:
I'm on b106 stock now.... how do I get my phone into bootloader or fastboot now? Update won't let me do incremental updates either... No incremental update button to manually update to 107 and 108. Thx for any help you can give me...
Click to expand...
Click to collapse
Put the B107 update on your sdcard in a folder called dload. Make sure you rename the B107 Update to update.zip before you do this or it won't see it. Go into settings--->Updater---->Hit Menu at the bottom and go to Local Update. It will see it and you'll be able to install it. Any incremental update that you do make sure to rename the file to update.zip. Do the same process for the B108 update.
ajsmsg78 said:
Put the B107 update on your sdcard in a folder called dload. Make sure you rename the B107 Update to update.zip before you do this or it won't see it. Go into settings--->Updater---->Hit Menu at the bottom and go to Local Update. It will see it and you'll be able to install it. Any incremental update that you do make sure to rename the file to update.zip. Do the same process for the B108 update.
Click to expand...
Click to collapse
Thx... That worked. I'm on stocked 108 now.... How do I get my phone in fastboot or bootloader mode to update to "X2_TWRP_CN_5.1.1_kangvip"? I want to install "X2-B108SP01_Kangvip". Again... Thx for all your help... Very much appreciated! Also, holding volume key down and power button at the same time does nothing...
Steamer2499 said:
Thx... That worked. I'm on stocked 108 now.... How do I get my phone in fastboot or bootloader mode to update to "X2_TWRP_CN_5.1.1_kangvip"? I want to install "X2-B108SP01_Kangvip". Again... Thx for all your help... Very much appreciated! Also, holding volume key down and power button at the same time does nothing...
Click to expand...
Click to collapse
I finally got both installed!
Steamer2499 said:
I finally got both installed!
Click to expand...
Click to collapse
Great, how's the ROM?
ajsmsg78 said:
Great, how's the ROM?
Click to expand...
Click to collapse
Running pretty good... Got some system parsing errors... Mainly Huawei pre-installed stuff errors Getting rid of some of the chinese stuff...
Update: Updated the OP with a guide on how to install TWRP.
After install, I refresh finished, not start a recovery. My Model 702L.
ajsmsg78 said:
Update: Updated the OP with a guide on how to install TWRP.
Click to expand...
Click to collapse
Why it keeps on giving me in the CMD:
'Failed Remote command not allowed'.
Is your bootloader Unlocked ?
I used to have similar error even though my bootloader state was shown as "phone unlocked". So I re-unlock the bootloader and then I managed to flash the twrp custom recovery
kpcheang2 said:
Is your bootloader Unlocked ?
I used to have similar error even though my bootloader state was shown as "phone unlocked". So I re-unlock the bootloader and then I managed to flash the twrp custom recovery
Click to expand...
Click to collapse
Yes it is, at the bootloader screen it shows the Phone Unlocked.
BTW.How to re-unblock it? In case needed.
hagba said:
Yes it is, at the bootloader screen it shows the Phone Unlocked.
BTW.How to re-unblock it? In case needed.
Click to expand...
Click to collapse
Just type in fastboot oem unlock xxxxxxxxxxx where x is your unlock code.
Yes - as "ajsmsg78" stated just reboot into bootloader mode and type in "fastboot oem unlock xxxxxxxxxxxxxxxx"
After that try to flash the trwp - it worked for me.
5.1.1 ROM on 702L
eennap said:
After install, I refresh finished, not start a recovery. My Model 702L.
Click to expand...
Click to collapse
You mean you managed to install the 5.11 ROM onto your 702L ?
kpcheang2 said:
You mean you managed to install the 5.11 ROM onto your 702L ?
Click to expand...
Click to collapse
I install TWRP 5.1.1 on my 702L.
Dont worry I fixed it now... but can you please update the link for the TWRP english theme? it seems broken.
OP updated with a working link to the TWRP English theme.
Flash 5.1.1. twrp onto 702L
eennap said:
I install TWRP 5.1.1 on my 702L.
Click to expand...
Click to collapse
May I know how you managed to flash the 5.1.1 twrp onto your 702L ?
When I did "fastboot flash recovery twrp_cn.img" and tried rebooting into recovery mode, it went into a boot loop ?
I wanted to use it to try flash the B106 703L ROM
Im still on 5.1.1 official version and my device is bootloader unlocked and twrp installed help me how to install official 6.0 version
First just flash 6.0 image through fastboot process in this twrp will be replace with stock recovery, Second flash someone's 6.0 Nandroid backup through TWRP...
Sent from my Toilet using Moto G3....
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
beworld16 said:
I have also same query, having xt1550 with 5.1.1 and unlocked bootloader with root access.
Also receiving OTA notification but can't install the same.
Tried to install OTA manually but could not go into recovery mode stuck on "No Command" screen.
Please guide....
Click to expand...
Click to collapse
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
That's very much true.. Don't flash ota with TWRP with having root access..
Sent from my Moto G(Osprey)
Thanks for the reply
I have downloaded Official Firmware of 6.0 for XT1550 from here.
So Now, can i process with this using fastboot command.
If yes, will it look the bootloader ?
Tel864 said:
You can't flash OTA with root. You can look at the other thread on factory firmware and flash a Marshmallow factory image if one is available for your model. That is safer than flashing an OTA anyway.
Click to expand...
Click to collapse
I thought OTA's worked fine with root installed, although you often lose root in the process, it was custom recovery they burped at?
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Diamantes said:
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Click to expand...
Click to collapse
U should use dload method
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
U should use dload method
Click to expand...
Click to collapse
I forgot to mention: dload not working. Always error.
That's why I think TWRP is the only solution
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Dazed No More said:
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Click to expand...
Click to collapse
but you mean that I have to downgrade from Nougat to MM again?
And before doing it I have to flash the stock recovery?
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips.
With the files you provide I should "dload"?
I do not understand your post.
please explain better.
Thanks.
Diamantes said:
but you mean that I have to downgrade from Nougat to MM again? Yes
And before doing it I have to flash the stock recovery? No
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips. Like I said they did half of the rollback process which is why you are on B300 firmware that you cant find available for download
With the files you provide I should "dload"? Yes
I do not understand your post.
please explain better.
Thanks.
Click to expand...
Click to collapse
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Well, I will try this weekend. Now the risk to stay without phone during working days is too high
Ah, BTW, thanks for suggestion.
Dazed No More said:
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Click to expand...
Click to collapse
Well, I changed my mind and tried anyway now. I was just too curious.
result:
Software install failed.
Incompatibility with current version.
please download the correct update package.
As usual. Huawei sucks. Full stop.
Diamantes said:
Well, I changed my mind and tried anyway now. I was just too curious.
Click to expand...
Click to collapse
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
As usual. Huawei sucks. Full stop.
Click to expand...
Click to collapse
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Dazed No More said:
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Click to expand...
Click to collapse
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Diamantes said:
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Click to expand...
Click to collapse
Have you tried the Team MT huawei multitool to flash the images from the firmware? Use the Huawei update extractor tool to get the boot,cust,recovery,system and userdata.img from the firmware you tried to flash and then put them in the unbrick folder in the multi tool. Put phone in fastboot and run the Multi tool and use the unbrick option. I know your phone is not bricked but this way it will flash all 5 images in order through fastboot. You could actually try and flash the most current firmware with this method and avoid having to system update from MM to Nougat.
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Diamantes said:
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Click to expand...
Click to collapse
Thats me i guess :silly:
---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
I am still learning and everytime its different result . Someitmeit works and sometimes it doesn't
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
When I go to multitool "unbrick", it asks for custom.img, but in no update.app of my firmware is present.
Moreover now I just can enter erecovery. It does not boot. I can enter fastboot only. Multitool is now not recognizing the phone. Do you know how to proceed?
I put in dload the firmware .app, but it says "software install failed"
Pheew...I managed to have again that fuc..ng C900B300.
I entered fastboot and repeated the unlock bootloader process. That way the phone got a hard reset and started over. Believe me when I say I tried all the methods I knew.
I think there is something locked somewhere in my partitions (I am not an expert of course) that prevent me to do deep modifications. Now I just can TWRP data but not the core. And again I have no update option. I think I am stuck forever at this stage with 1st march patches and nougat 7.0.
I do not think I will be ever able to have Oreo.
Amen. I am really tired to waste my time with this s**t. Next phone will be again a Samsung or One+. Full stop. Stop chinese brands.
Where are you located, Europe?
Yes
Ok bro I really hope this is it. Full firmware BLN-L21C432B151. I already downloaded it myself and checked with extractor tool it has all the images you need. Since you have fastboot back use the multi tool unbrick again and now that you have all the necessary images cross your fingers it will work.
And I agree with you about the phone. Made up my mind im giving this turd to my sister and getting the OP5T in a few weeks.
Thanks. I will do it this weekend. Today I spent 5 hours to get back my configuration after the hard reset with the apps I use for work. Cannot risk again tomorrow.
In another thread, sashank suggested to change OEM file because probably phone doesn't recognize the firmware I want to install.
It didn't work and lead me to start from scratch with the same strange build.
I will try your method but first I must study better the procedure because I don't want to mess up everything and risking to throw the phone in the garbage (where it belongs in the end...).
Thanks.
How to Flash Factory Firmware
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Youtube Video :- https://www.youtube.com/watch?v=eCGB-yxC09w
Text Guide
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in factory firmwares section).
Extract factory firmware to a folder.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Copy all contents of ADB fastboot folder and paste it in factory firmware folder.
Download flash-all.sh(Mac & Linux) or flash-all.bat (Windows)
Place flash-all.sh/flash-all.bat file in factory firmware folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt/terminal window, navigate to factory firmware folder.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
flash-all.bat
Mac & Linux
Code:
./flash-all.sh
Once everything is flashed.
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
Motorola Bootloader Unlock - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Downloads
Motorola drivers for Windows & Mac :- https://support.motorola.com/us/en/drivers
Setup ADB and fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
flash-all.sh (Linux + Mac) - https://mega.nz/#!OYFiRKZC!2CjMLxpoEAqpFyB_q1Q1FncC9a1oNofh9Hjm99PwiGo
flash-all.bat (Windows) - https://mega.nz/#!DF1XwSjC!tkHhb9H9-1piNr1AbKaPJK_yLuv4rpIxw1AWicD1I94
Factory Firmwares
https://mirrors.lolinet.com/firmware/moto/payton/official/
US Retail Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android One Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Twitter Account to Follow for latest firmware uploads
https://twitter.com/motofirmware123
you da man!
Your tutorials are very helpful .Thanks
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
jpolster2005 said:
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
Click to expand...
Click to collapse
you should be able to flash the latest firmware listed above as long as you can boot into fastboot.
but my locked boot loader says preflash validation failed
jpolster2005 said:
but my locked boot loader says preflash validation failed
Click to expand...
Click to collapse
unlock the bootloader.
I can't, because OEM UNLOCKING is set to off
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
michael28056 said:
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
Click to expand...
Click to collapse
rooted?
No -unrooted, stock rom from this thread, locked bootloader.
michael28056 said:
No -unrooted, stock rom from this thread, locked bootloader.
Click to expand...
Click to collapse
well, i never stay on stock long enough to check that ..sorry cant help with that.
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
jpolster2005 said:
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
Click to expand...
Click to collapse
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
same peeps thread
aw man... well, I meant to post specifically to the last post in the thread but was on the mobile app.
:good::good: Just wanted to say thank you for this post, the links to the image files and the flash-all BAT file. This really saved my butt with a Project Fi Moto X4, which I had rooted using Magisk before checking on the availability of factory firmware images from Motorola. (of course there are not any available from Motorola ) The phone was continuously prompting for an OTA update, which would fail. I first tried the Magisk uninstaller, which ran successfully in TWRP, but the OTA update was still failing. After some digging on Google I found your post and used the Project Fi image to flash the phone, it worked perfectly! There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully. I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
g3m1n1 said:
I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
Click to expand...
Click to collapse
glad to be of help :highfive:
g3m1n1 said:
There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully.
Click to expand...
Click to collapse
Hello!
I understand you have Android One version. If that's the case, anyone catching the URL to OTA for the Android One 28.2 update? I've been looking for it for days, and the OTA link generator is not working (at least with the data I'm providing which should be correct).
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.