Related
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Some Help
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
still cannot flash
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Is your phone from Telcel Mexico originally?
I ask because on my case it is. The firmware you need to flash has to be the latest one based on your phone region, on my case I flashed the Brasil Retail. Because my phone is from Latin America. So it will depend on were your phone is from. This is all because your phone is acting up as LOCKED bootloader so flashing a version from another region is not possible.
Also because your phone got stuck on an OTA you need to make sure the version you flash is at least the same one as the OTA, newer if possible.
Rokwenelenya said:
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Click to expand...
Click to collapse
Worked but not completely
Ok, I flashed the rom that you recomended, the phone finally boots into android, but now is always on "emergency calls only" mode, with or without Sim card any suggestions?
Phone should be back as unlocked bootloader
If you flashed a version fine now, I'm sure that at least you should be able to go into fastboot and see your bootloader as unlocked.
If this is true, then you can go ahead and flash any version available, either being an older Stock version (downgrade) or any custom ROM of your liking, like CM 10.1. You should try them and see if you get a proper signal.
Also in your case, if your bootloader is unlocked again, I recommend you installing the version that you know worked fine for you. It won't matter that it's older than the one you flashed right now. It's just a matter of following the guide for unlocked bootloaders to downgrade versions.
Good luck! :fingers-crossed:
Phone almost repaired
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Honestly I have not faced this before it sounds very weird!
I can think of two possibilities, one your phone lost it's IMEI. You should check if it's still there, either by going through configuration and Phone Information or by the "secret code" on the dialer: *#*#4636#*#*
And in the following menu go into Phone Information. The first thing you should see is your IMEI. If it's not there, look for the how to restore your IMEI thread on here. I know it's there somewhere.
The second thing I can think of is to try to force your phone into your carrier, go into Cellular Networks area and manually choose your provider, this could force the registration.
Hopefully this will be of help!
Rokwenelenya said:
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Click to expand...
Click to collapse
Fastboot Error / Invalid GPT
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
adolfovm said:
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Click to expand...
Click to collapse
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
doctorwho2 said:
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
Click to expand...
Click to collapse
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Thanks
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
link
thanks
Click to expand...
Click to collapse
Thanks to you, it really work for me. My Motorola RAZR HD its now alive.
other possible solution that worked for me is
flashing this
http://sbf.droid-developers.org/download.php?device=6&file=119 (CLARO PR Jelly Bean)
Thanks!
suggestions for XT 925 please?
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
hbenz2008 said:
suggestions for XT 925 please?
Click to expand...
Click to collapse
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
unable to flash partition signed
Hi.
I downloaded the SBF from sbf.droid-developers.org/phone.php?device=6 for my region(canada).
I proceeded to try to do universal through the RSD:
Filename: UNIVERSAL.xml
Creation Date: 11/23/2014 09:11:58
File size: 1589
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
I got failed flash process 1/18 flash partition "partition_signed"
Before this, my phone was working fine. Got the kitkat update pushed to me and after update it was working fine. I was using it until my battery ran out so i turned it off. Afterwards, it just got stuck at the motorola logo. I tried to update it with xt926 didn't realize that my phone is xt925. Anyways, i got the bootloader unlocked. Tried the above but failed.
Any help is appreciated!
Thanks!
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
hbenz2008 said:
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
Click to expand...
Click to collapse
I just got help from another thread. Followed it and it worked!!
http://forum.xda-developers.com/showthread.php?t=2760840&page=72
bweN diorD said:
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
Click to expand...
Click to collapse
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
edwint290 said:
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
Click to expand...
Click to collapse
i dont really understand what you are asking.
you need to figure out which is the most recent partition table you have put on the phone successfully and flash that first. nothing will work correctly until you do. after you get a successful partition flash, you can flash whatever you want, just DO NOT flash the partition file again from any other version. old builds will work on the newer partition table.
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
MECH_TECH said:
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
Click to expand...
Click to collapse
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Rogers 4.4.2 OTA file
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
link to OTA file
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
will this work with spaces in it?
h t t p: // w w w. 4shared.c o m/zip/PUw0K63Ace/Blur_Version9821122002XT925RCI.h t m l
OTA file link
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
check the post now i put in a link with spaces and it posted.
Bootloader unlocked now
I have the bootloader unlocked now from Moto website. If I boot into AP Fastboot it is confirmed "Device is UNLOCKED. Status Code: 3" I am trying to flash a cmwrecovery.img to the phone. I get the following
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6824 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 1.997s]
finished. total time: 2.527s
I am not sure that the img is working. I execute the fastboot reboot and hold volume up/down and power select recovery and it stays on the boot logo for a long time then goes black logo comes back and boots normally. Not sure why its not working and do not know what i am doing wrong.
Any advise out there on this Rogers XT926 O.T.A. update fails
Now that the bootloader is unlocked I still cannot get the Rogers OTA to work. I got the 4.1.2 rooted again now and installed chainfire SuperSU onto the phone did a full unroot with SuperSU checked with root checker and now it says it is not rooted. I did a full factory reset wipe all data and downloaded the OTA update, let the OTA update try and it got 3/4 way through and failed. it keeps saying there is a critical update to run will download it and try but fails. I even tried to use the CWM custom recovery to run the update file and it gets error messages and fails. Not sure what to change in the OTA.img file to get this to take. Did anyone else figure out how to force it to complete?
Where is the Rogers stock 4.1.2
I found lots of 4.1.2 img files but I cannot be sure that any are for Rogers. How do I know that they are really plain stock files with now changes made to them, so that I can proceed?
RSDlite problems
CWGSM3VO said:
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Click to expand...
Click to collapse
I found the Rogers 4.1.2 file called
9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
I installed RSDlite 6.1.5
I ran the RSDlite and it sees my phone on USB port 1 info below
MEI/ESN/MEID: N / A
Technology: UMTS
Software Version: 9.8.2Q-8-XT925_VQL-12.2
Flex Version: N / A
Bootloader Version: 109b
DRM Version: N/A
I put the above zip file in the firmware folder
I pick it screen shows
Filename: 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml
Creation Date: 12/20/2012 21:34:28
File size: 2640
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
It asks to decompress or decompress and flash.
I picked decompress and flash
It says switching device to flash mode
phone reboots to ap fastboot I see device is UNLOCKED Status Code: 3
I get an error symbol and RSDlite says
Failed flashing process. Unknow fastboot command... Result FAIL
I cannot get the 4.1.2 to flash so I can continue with the OTA update.
What am I doing wrong
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
Here is the Link to 4.4.2 - Rogers Rom, been using it for some time, works flawless
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
prakash27091987 said:
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
Click to expand...
Click to collapse
Downgrading only boot and system caused messed up fingerprint. Used all commands except bootloader provided in other thread for downgrade and now everything's good.
I see that the bootloader is not being downgraded. Doesn't that mean OTAs might still brick your device?
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
this is not working means fingerprint problem comes
Silesh.Nair said:
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
So are you saying that the bootloader was updated and if we do the OTA we might brick our phone?
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
The point about bricks is regarding downgrade. In previous phones, downgrading from L to K, but keeping the L bootloader and then getting official L OTA would brick phone. Motorola has never supported downgrade on any phone. So if you downgrade, and later take OTA you could brick. Especially if running M with N bootloader.
The whole title of this thread is wrong - no way can anyone 100% guarantee no future brick.
Silesh.Nair said:
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Taking OTA to official N from soak test N is not an issue, the issue arises when someone took the N soak test, downgrade to M, OTA to official N.
tl;dr if i'm not wrong:
M -> Official N = No brick
M -> Soak test N -> Official N = No brick
Soak test N -> Downgrade to M -> OTA to official N = Brick
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
You can say what you want but go read the G And X2 communities. EVERY user that updated to M then rolled back to L and later took an OTA back to M bricked. The OTA doesn't take into a count that the bootloader was a newer version - I don't remember the mechanics, but the OTA expected a different version of the bootloader.
Search XDA or the Internet for "Blank flash files" . The problem is downgrade related. If you take any upgrade, be prepared to stay on it. Do NOT downgrade.
Well, it may be true. I don't just blindly flash files on my device. I go thru the zip file to see what files are patched to make sure that I don't get into trouble. That need not be the case with all users.
Let's wait for the official OTA to be released and then we'll see how it goes.
Sent from my Moto G4 Plus using Tapatalk
ok guys ive just done some testing and ive found that whilst on official android 6.0 my bootloader version was (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13
then after upgrading to 7.0 soak test the bootloader version changed to (moto-msm8952-b1.00) with the date 2016-06-24
so after i then did the downgrade back to 6.0 marshamallow and the bootloader version downgraded back to its original (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13 so moral of the story is the bootloader does infact downgrade too and doesnt stay with the new android 7.0 bootloader like many seem to claim on this thread if u guys want to try this for yourself run this command to get your bootloader versions before update and after u updateto 7.0 & then 1 last time when u downgrade to 6.0 u will need to run the below command via adb fastboot
fastboot getvar version-bootloader
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
chromedome00 said:
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
soo we cant take ota but we can install it manually that doesnt effect i think
does downgrading work if my device is brick??
does downgrading work if my device is brick??
sucssecfully downgraded from marshmallow after brick in nougat .........tons of thank
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
drdhaval1987 said:
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
Click to expand...
Click to collapse
dOWNGRADE process please
kemesh said:
dOWNGRADE process please
Click to expand...
Click to collapse
its already mentioned in this thread....simply follow the steps........
When I am trying to install the Nougat OTA zip file from within the stock recovery, it is giving me the following errors:
Code:
Verifying current system. . .
Mount count = 9
Last mount path = /system
Last mount time = 1479061757 -> Sun Nov 13 18:29:17 2016
Device was remounted R/W 9 times
Last remount happened on Sun Nov 13 18:29:17 2016
E1004: system partition fails to recover
E: unknown command [log]
E: unknown command [log]
E: Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I go about fixing this? I have followed your guide on how to downgrade and downgraded my XT1643 to -63 baseband.
Help please!
As the Nougat is rolling out for XT1572 devices, here's the guide for Flashing Stock Firmware using Fastboot for receiving Nougat OTA.
(Inspired by @acejavelin guide)
Prerequisites:
1) USB Drivers (Not needed for Windows 10)
2) Fastboot installed and working.
3) Stock Factory Images for Moto X Style (XT1572): https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
Procedure:
1) Open a terminal or command prompt (Shift + Right click) window into the directory that contains the firmware files you extracted above.
2) Reboot the phone in Fastboot Mode (Reboot to Bootloader) and connect the USB Cable.
3) To verify if everything is perfect type in:
Code:
fastboot devices
If it shows your device serial number then you can be sure that it's properly connected.
4) Read the 'Notes' below.
6) Before proceeding, flash this commands to clean up the previous system's mess. This will get rid of the '(bootloader) Preflash validation failed' error when flashing gpt.bin (partition table).
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
5) Here's the actual commands to Flash the Stock Image. Please Enter them One-by-one, Don't create any .bat files or copy and paste the entire section.
Code:
[STRIKE]fastboot getvar max-sparse-size[/STRIKE]
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Make sure you read whatever is happening on the prompt, do not miss any errors. (Scroll up the prompt and re-check everything before booting)
Notes:
1) This won't Lock your bootloader but you will be able to get OTA's.
2) For receiving Nougat on RETASIA Dual Sim, download: XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
There will be a 44mb update already queued when you boot the device. It will update the device to December 2016 Security Patch.
Reboot and you will be able to get Nougat OTA (911mb), if eligible.
3) If you didn't get the OTA Update, Flash this Nougat OTA after updating to December 2016 security patch: https://forum.xda-developers.com/moto-x-style/general/ota-nph25-200-15-retasiads-t3636765 (Credits: @Sagar_1401)
4) Different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have nine, 6.0 has eight, and 6.0.1 has eleven sparsechunks.
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
There is no need to do fastboot getvar max-sparse-size, that is just for RSD Lite to check your maximum system chunk size, when doing it manually it does nothing.
Not really sure why this guide is needed, there are already a few out there that are basically identical.
Nice guide @antariksh thanks for this.
i will be flashing from my current version 6.0.1_MPH24.107-58 (seemingly higher version) tomorrow.
will update once i attempt this.
Quick tip if you can't get SafetyNet passed with Magisk V13.1 or V13.2
For Stock Nougat as we don't have boot.img
1) Backup boot with TWRP
2) Restore boot with TWRP
3) Flash Magisk zip
4) Reboot and Install Magisk Manager v5+
This won't get your SafetyNet passed.
5) Open Magisk Manager and once again press 'Download and Install'
This will automatically download and install the latest Magisk and after a reboot your SafetyNet will be passed.
antariksh said:
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
Click to expand...
Click to collapse
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
trannamcloud said:
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
Click to expand...
Click to collapse
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
trannamcloud said:
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
pradeepvizz said:
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
Last week I flashed the MPH24.107-58-5 (6.0.1) thinking that this was the latest version. But then I TWRP restored back to my Custom ROM as there was no Nougat OTA.
On this Saturday I was able to flash the MPHS 24.49-18-8 without any issues.
Try flashing the gpt.bin twice and don't try to lock your bootloader.
trannamcloud said:
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
Click to expand...
Click to collapse
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
Click to expand...
Click to collapse
I have upgraded to Nougat successfully with no problems.
pradeepvizz said:
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
I have upgraded to Nougat successfully with no problems.
Click to expand...
Click to collapse
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
Same me, the only way is back to 6.0.1 now
titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
hi, guys
What is your Bootloader version, mine is BL: A0.4C for 6.0 Retasia DS. I see 6.0.1 Retasia DS has BL: A0.4A. Which versions is higher? With BL: A0.4C for 6.0 Retasia DS, I cannot flash to 6.0.1 with GPT.bin and Boot.img.
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
duttandy said:
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
Click to expand...
Click to collapse
We don't have either... The best you can do is hope someone can do a TWRP backup of recovery you can restore, it needs to be the same variant and version.
pradeepvizz said:
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
Click to expand...
Click to collapse
Confuse now. As you said, 6.0.1 build 107-58 is not official release, so maybe not receive OTA Nougat?
My version is Asian - retapac, 6.0.1 - build 107-58 with security patch 1-Mar-2016. It's unable to downgrade to any stock 6.0, as preflash error.
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.