Hi, i used to have nougat "forced", when i flashed MM stock rom, the gpt.bin line showed me an error, but i think this error is normal due the downgrade, but also it showed me in the boot.img and recovery.img lines the error: image not signed or corrupted
It's that normal due the downgrade? Or what's wrong? I have the xt1621, unlocked bootloader.
Regards.
Maybe it is not yours boot.img and recovery.img ... Did you do it via fastboot?
lerg96 said:
Maybe it is not yours boot.img and recovery.img ... Did you do it via fastboot?
Click to expand...
Click to collapse
Hi, thanks for the reply, and yes i did it via fastboot, i think it's because the nougat rom was not for my device (now i know), but nougat worked very well, i suspect the boot.img and. recovery.img can't flash due the upgraded nougat bootloader?
Well, really i don't know. But i guess you can do everything with your phone if you have unlocked the bootloader.
lerg96 said:
Well, really i don't know. But i guess you can do everything with your phone if you have unlocked the bootloader.
Click to expand...
Click to collapse
Thanks anyway, i will wait for the N stock rom for my device, and then relock the bootloader. Regards.
Related
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have a locked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
lollo64 said:
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have an unlocked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
Click to expand...
Click to collapse
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
panart said:
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
Click to expand...
Click to collapse
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
lollo64 said:
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
Click to expand...
Click to collapse
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
panart said:
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
Click to expand...
Click to collapse
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
lollo64 said:
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
Click to expand...
Click to collapse
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Sickaxis79 said:
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Click to expand...
Click to collapse
Yes, I've tried both. With and without the first two commands (fastboot flash partition gpt.bin / fastboot flash bootloader bootloader.img), but it fails in every case. Purposely I get the errors when I launch this commands:
Code:
- fastboot flash boot boot.img
- fastboot flash system system.img_sparsechunk.*
All the other instructions work fine.
http://forum.xda-developers.com/showpost.php?p=65423306&postcount=475
24.65-33 Full EU
You can flash it directly On any XT1562
So I've got Zenfone 5 A501CG. As you may know, all cyanogens/roms are made for A500CG. It works on A501CG aswell, but once you unlock bootloader on this model, camera will stop working. It's caused by incompatible .bin files for motherboard. But when you relock bootloader, camera is working again, just fine. I did this like 5 times and it always worked.
Now I reverted from Resurrection 5.5.9/TWRP 2.8.7.0 to Stock android (.87 - last update)/Stock recovery with relocked bootloader (like always) and the camera is still not working. I tried using different ifwi/dnx and tried to re-flash stock rom (ADB sideload) with formating cache/data. Camera is still not working.
I even tried to go back and flash 2.22.40.53 (KitKat 4.4.2). Still the same, camera not found.
Can someone help me? Do someone face the same issue?
u have to downgrade all the way back to KK, and then use this http://forum.xda-developers.com/android/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704
I already did this, like mentioned. It didn't help at all.
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
dgadelha said:
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
Click to expand...
Click to collapse
Okay and then I can flash the newest fastboot then firmware right?
Masterfellow said:
Okay and then I can flash the newest fastboot then firmware right?
Click to expand...
Click to collapse
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Alright, I'll get home and I'll try. Thanks for now.
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Masterfellow said:
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Click to expand...
Click to collapse
Glad it helped! Thanks.
Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
steakhutzeee said:
Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
Click to expand...
Click to collapse
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
leonardohenrique10 said:
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
Click to expand...
Click to collapse
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
steakhutzeee said:
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
Click to expand...
Click to collapse
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
leonardohenrique10 said:
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
Click to expand...
Click to collapse
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
steakhutzeee said:
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
Click to expand...
Click to collapse
Yes, same on my device. I think it's normal.
Yes, fastboot mode of lollipop firmware on ZenFone 5 / 6 is able to flash custom kernel / recovery, but it won't boot until bootloader unlocked.
Guys, I have managed to downgrade the first 7.1.1 soak test firmware back to the 7.0.
For now, you need flash the 7.0 system firmware(without flash the bootloader.img and gpt.bin) via:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
UNLOCKED BOOTLOADER IS NEEDED!
Code:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.9
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
When you finished flashing, you will have 7.0 with April security patch
If you want upgrade to the latest official released 7.1.1 build, just sideload the May security patch, then final 7.1.1 OTA again:
Blur_Version.25.231.4.addison.retail.en.US
http://motorola.erfanabdi.ir/index.....25.211.10.addison.retail.en.US&carrier=retbr
Blur_Version.26.51.21.addison.retail.en.US
http://motorola.erfanabdi.ir/index....n.25.231.4.addison.retail.en.US&carrier=retbr
Now, everything works like a charm.
Thanks for doing this. I was hoping it would work.
:good:
EDIT:
In case anyone is waiting for more confirmation, I did this last night and it worked perfectly for me.
Yes you will need your bootloader unlocked. And No you won't be able to re-lock it afterwords because there doesn't seem to be any official signed firmwares for the Moto Z series.
Is it really final update?
invisible.nsk said:
Is it really final update?
Click to expand...
Click to collapse
Hopefully, not (Hint, 8.x...)
But without a full image one cannot relock bootloader..
b00tbu9 said:
But without a full image one cannot relock bootloader..
Click to expand...
Click to collapse
As i know there is no signed images from lenovo to relock bootloader.
anyone has the NPN26.118-10 last soak update?
I need this to update to NPN26.118-22.
My version is NPN26.107, soak test applied via adb sideload.
Tried to update to NPN26.118-22 and get an error...
OTA?
nintendo22 said:
Guys, I have managed to downgrade the first 7.1.1 soak test firmware back to the 7.0.
If you want upgrade to the latest official released 7.1.1 build, just sideload the May security patch, then final 7.1.1 OTA again:
Click to expand...
Click to collapse
After flashing, won't be able to receive OTAs? Or you sideloaded just to rush things?
Can confirm this method works on RETEU as well.
I can confirm that this method works fully tested on a moto z play AT & T Mexico
Thank you it's working ?
hello in RETEU working? very thanks
regards
With unlocked bootloader we can't get any ota right??
Maxbmwe53 said:
With unlocked bootloader we can't get any ota right??
Click to expand...
Click to collapse
You can still get OTAs if your bootloader is unlocked. I *think* , unless Moto has changed something.
Maxbmwe53 said:
With unlocked bootloader we can't get any ota right??
Click to expand...
Click to collapse
Not entirely true. I've flashed NPNS25.137-24-1-4 last month, and got NPNS25.137-24-1-9 OTA. But since then, the next OTA resulted in "Error". Still trying to figure out why.
Anyone??
rickbosch said:
Can confirm this method works on RETEU as well.
Click to expand...
Click to collapse
From first soak test? I haven't tryed, but I think it's not possible without first flashing second soak test. I need the link for second one, can't find. Nobody over the world has this file. That's crazy.
I would downgrade and all do this, but I want not lost all my date
allrightlite said:
From first soak test? I haven't tryed, but I think it's not possible without first flashing second soak test. I need the link for second one, can't find. Nobody over the world has this file. That's crazy.
I would downgrade and all do this, but I want not lost all my date
Click to expand...
Click to collapse
I'm in the same situation than you. RETEU sideloaded npn 26.107.
If the downgrade works and we can continue getting ota's in the future, i think it worth it.
On the other hand, is there a step by step to flash to 7.0?
Thanks
No downgrade method 7.0 without unlocking?
BeetoCarvalho said:
No downgrade method 7.0 without unlocking?
Click to expand...
Click to collapse
No.
Read the first post, it says right there. Bootloader unlock is required.
FanDroid09 said:
No.
Read the first post, it says right there. Bootloader unlock is required.
Click to expand...
Click to collapse
With bootloader unlocked i will still be able to receive ota updates? Or i will be stuck on the official 7.1.1?
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery