Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.
Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.
WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.
All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.
I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.
Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk
I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.
This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?
robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk
The files that I flashed I got from here. Don't know if that's where you are getting yours.
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help
Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk
Related
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
anton2009 said:
Try relocking bootloader then installing update. And then unlock again.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Redefined81 said:
Hello all, I am still fairly new to the root/Android scene and I've run into a problem.
Firstly, my Nexus' bootloader is unlocked and I'm running and older Franco.Kernel (4.0.1 and 1.4GHZ OC). Now, the problem is, my phone has notified me that a newer OS version is available. When I go to install it, the phone reboots but right after - the little Droid appears with a red caution sign and the phone stays that way until the battery is pulled.
What am I missing here? Any help is greatly appreciated.
P.S. I'm a n00b.
Click to expand...
Click to collapse
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
heifica 798.
martonikaj said:
No... He's not going to be able to update just because he locked the bootloader.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
In order to properly take an OTA and have it install you're going to have to be on the stock ROM, recovery, radios, everything. You can be unlocked and rooted, but you can't have changed anything else. Because you've flashed another kernel, you're probably going to have to flash the update manually.
Click to expand...
Click to collapse
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Redefined81 said:
Thanks! How and where would I go about doing this?
Sorry, but remember, I'm still really new to all of this.
Click to expand...
Click to collapse
I'd pass that question to someone more knowledgeable than I on the subject. I wouldn't wanna give you improper guidance. Not sure how your custom kernel comes in to play when flashing.
All I know is you won't be able to take the regular OTA in your current state.
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
Is this going to un-root and/or lock my bootloader again?
You should have learned how to go back to stock before flashing anything...
El Daddy said:
Here is your info on how to get back to stock.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
efrant said:
That is overkill. Just go here: http://code.google.com/android/nexus/images.html and download the version of Android you are using. Extract the boot.img file from within, and flash that with fastboot. Now you are back to the stock kernel, and the update will install automatically (assuming of course that you did not make other changes).
EDIT: You will not lose root, your bootloader will still be unlocked, and all of your data/settings will still be there.
Click to expand...
Click to collapse
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Redefined81 said:
Thank you so much!
I know I may seem a tad annoying, but I just don't want to mess up my phone, lol!
How do I go about installing this?
I DL Fastboot & it's drivers. Extract the IMG (just so you know, I'm currently yakjuxx, not yakju - does that matter?) to the same directory as Fastboot then enter my phone into Fastboot mode. The thing is, I'm unfamiliar with the command prompts to get it going. I'll be doing it on Windows 7. Help would be appreciated!.
I know I've asked a lot, and I thank you.
Click to expand...
Click to collapse
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
efrant said:
I'm not sure it matters if you are yakju or yakjuux (as I think all the stock GSM kernels for ITFL41F are the same), but just to be sure, go here and download my nandroid back up of yakjuux ITL41F. In the archive, you will find a boot.img file (which is the file you need). Extract it.
All you have to do it put the boot.img file in the same directory as your fastboot.exe file, reboot your device into fastboot mode, and plug it into your PC. Open a command prompt in that directory and type fastboot devices to make sure you PC recognizes your device. Then type fastboot flash boot boot.img
Done.
Now, obviously this assumes that you already have the drivers set up properly...
Click to expand...
Click to collapse
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
mudferret said:
Fastboot can flash boot.imgs, awesome, I likely would've been a muppet and made a CWM zip. I learn something new that I love about my GN every day.
Click to expand...
Click to collapse
The "fastboot flash" command is specifically for flashing full images to partitions on the device, e.g., system, userdata, boot, recovery, bootloader, radio, splash1, etc.
Hey Guys, My Zenfone 2 (Ze550ml) got soft bricked automatically after 3 days of rooting it. The Problem is not that 'I want to recover' the problem is that I rooted the device via a method displayed in the xda forum which is one-click root method.
The unbricking process is via ADB from cmd i did that but when i type " adb sideload <filename.zip>" and press enter then it shows
' error: Protocol Fault <no status>' So I tried to update the drivers and firmware and everything is up to date including drivers and all. But still it shows that, I don't know what to do now!! I consulted one of my friends he said that 'this because that while rooting none of the drivers were updated. ' So Now whats the solution for it.
Do you have the latest boot.img and droidboot.img files flashed via fastboot?
Saamyo said:
Do you have the latest boot.img and droidboot.img files flashed via fastboot?
Click to expand...
Click to collapse
I don't know much about boots and ROMs and fastboots. So i don't know what are they, and I haven't done that. if you have a link to describe the method to do that then it would be great!
http://www.android.gs/how-to-unbrick-asus-zenfone-2-and-go-back-to-stock-android-os/
Go here for the instruction. and for latest system img files go here,
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
fahimnewaz said:
Go here for the instruction. and for latest system img files go here,
Click to expand...
Click to collapse
Ok I will check that out and try it and see whether any improvement is done or not. Thanks You for The Links
I cant seem to find it in the forums, only for the 551ML... can someone help me? I figured out its via Asus flash tool...
Does it matter if i use WW or CN?
Don't go near raw unless you are bricked.
Just unroot, flash stock recovery, sideload stock firmware ...if you phone is working ?
timbernot said:
Don't go near raw unless you are bricked.
Just unroot, flash stock recovery, sideload stock firmware ...if you phone is working ?
Click to expand...
Click to collapse
That simple? But if i flash stock recovery, how can i do ADB sideload since i doubt i can boot into CM13 on stock recovery?
Anyway, do you have a concrete guide? something safe i can follow, i see many guides and its kinda confusing.
EDIT: Okay I found something, basically flash stock recovery... from somewhere? I guess its in the zip folder of the firmware im flashing (extract it out?)
then reboot into stock recovery mode, choose adb sideload...
enter commands to adb side stock firmware filename.zip?
profit?
Messing with phones is risky..nothing's ever concrete , the risks are outlayed when flashing custom roms and still applies. Heavens knows what might have happened trying to flash raw for a brilliant example !
That outta the way...
Yup , you going right so far except you need recovery.img if on ze550ml .latest recovery for an example for latest fw
Rename latest fw WW- BLA blah fw for example to MOFD_SDUPDATE and put it in adb fastboot folder.
ADB SIDELOAD CMD after booting in stock rec...>
adb sideload MOFD_SDUPDATE.zip
All risks are still applied to you and you only
Ps, if you bought this phone with CM already on...you need knowledge of running fastboot and adb before even contemplating.
timbernot said:
Messing with phones is risky..nothing's ever concrete , the risks are outlayed when flashing custom roms and still applies. Heavens knows what might have happened trying to flash raw for a brilliant example !
That outta the way...
Yup , you going right so far except you need .184 recovery.img if on ze551ml .184 fw for an example.
Rename latest fw WW- BLA blah fw for example to MOFD_SDUPDATE and put it in adb fastboot folder.
ADB SIDELOAD CMD after booting in stock rec...>
adb sideload MOFD_SDUPDATE.zip
All risks are still applied to you and you only
Ps, if you bought this phone with CM already on...you need knowledge of running fastboot and adb before even contemplating.
Click to expand...
Click to collapse
LOL true true, I dont disagree with ya... well i was the one who put that phone into CM13 but i gave it to someone, now im trying to revert it back to stock like since Feb as shes just a regular user and CM13 its kinda unstable for her usage...
Okay i downloaded from asus global website .... UL-Z008-WW-2.20.40.149-user.zip
but inside I only see boot.img and droidboot.img... there's no stock recovery image... there's a recovery folder though
\recovery\recovery-from-boot.p
\recovery\bin\install-recovery.sh
How can i extract the recovery img or... im lost at this part... And im also suppose to flash boot.img and droidboot.img right?
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
timbernot said:
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Click to expand...
Click to collapse
omg bro, where did u find this repository from? Its like exactly the same as the Official asus zip but... with recovery.zip and...root?!
From general thread above
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321
Lol
timbernot said:
From general thread above
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321
Lol
Click to expand...
Click to collapse
lol... i inspected the file contents...
I got a feeling i can just simply fastboot flash everything since its all in .img files...
flash recovery boot and droidboot... reboot... then flash system.img...
How did you do ?
For the benefit of others who may be in the same boat , what did you do ?
Thread Closed
Thread Closed
I don't know what SKU means, but I'm assuming this doesn't work on the XT1763 variant (MediaTek), right?
lucasdeeiroz said:
I don't know what SKU means, but I'm assuming this doesn't work on the XT1763 variant (MediaTek), right?
Click to expand...
Click to collapse
Setting < about phone < hardware info < sku ????
It works on any mediatek variant of e4.
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
yashburshe007 said:
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
Click to expand...
Click to collapse
Did you name the file "twrp.img"?
madbat99 said:
Did you name the file "twrp.img"?
Click to expand...
Click to collapse
No. The name of the file is twrp. Extension in .I'm
I just took the file out of the .zip given by op and flashed. But after flashing if I go into recovery mode, it just gives me "no command" screen. When I directly boot into the file, my device restarts to system
yashburshe007 said:
No. The name of the file is twrp. Extension in .I'm
I just took the file out of the .zip given by op and flashed. But after flashing if I go into recovery mode, it just gives me "no command" screen. When I directly boot into the file, my device restarts to system
Click to expand...
Click to collapse
Make sure the file is named twrp.img because that's what you're typing in your command.
Fastboot flash recovery twrp.img
Or fastboot boot recovery twrp.img
So either rename the file or change your command to match whatever the filename is of the recovery image you're trying to flash.
You're just telling it to flash, you have have to tell it which partition to flash it to. It's not fastboot flash twrp.img (especially if that's not the filename) its fastboot flash recovery twrp.img but the last part (twrp.img) has to match what the actual file is named.
Also make sure fastboot can find it.
madbat99 said:
Make sure the file is named twrp.img because that's what you're typing in your command.
Fastboot flash recovery twrp.img
Or fastboot boot recovery twrp.img
So either rename the file or change your command to match whatever the filename is of the recovery image you're trying to flash.
You're just telling it to flash, you have have to tell it which partition to flash it to. It's not fastboot flash twrp.img (especially if that's not the filename) its fastboot flash recovery twrp.img but the last part (twrp.img) has to match what the actual file is named.
Click to expand...
Click to collapse
Reread my comment. .img is put not because it's in the name of the file but because it's the extension. I've rooted my redmi 2 before using fast boot and I what I'm doing. If I rename the file twrp.img then I would have to type "fastboot flash recovery twrp.img.img"
yashburshe007 said:
Could you also provide a full guide to rooting the mediatek variant of the moto e4? Apparently the older guide isn't working and whenever i fastboot boot twrp.img, it just reboots the phone to the stock rom. I also fastboot flash recovery twrp.img but no luck
Click to expand...
Click to collapse
show us the fastboot command window
Francesco Franz said:
show us the fastboot command window
Click to expand...
Click to collapse
nah, i got it to work. But I have a new problem now.... check the questions thread :crying::crying::crying:
who built this recovery? & if you built it please put version and changelog etc
* please credit the maker if it is not your recovery and put link to original source
Help Boot Loop
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
people should stop flashing this recovery using this guide ....* just my opinion ...
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
Max Teodoro said:
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
Click to expand...
Click to collapse
read this thread from the top to fix your device and press the thanks button ..read it ALL
https://forum.xda-developers.com/mo...woods-xt1762-build-nma26-42-75-t3688609/page5
read this too where I explained to another user bricking from this thread
https://forum.xda-developers.com/moto-e4/help/help-boot-stuck-twrp-t3713486
Max Teodoro said:
my help moto e4 xt1763 went into infinite boot loop after blinking boot.bin and recovery.bin can help me with a stock room for it?
Click to expand...
Click to collapse
disable system verification. So you can boot into system like installing no-verity zip can help you
KevMetal said:
people should stop flashing this recovery using this guide ....* just my opinion ...
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
Click to expand...
Click to collapse
Even i can't figure whats the problem with you . There is nothing bad with installation guide it is same as older ones. The recovery is from RR zip file. Its a working recovery and for daily use. I really don't know if SKU versions matters. Its the variant what we need. Confirm that you have tried everything and the above twrp is not fit into your expectations . I have flashed several roms with this recovery.
Francesco Franz said:
Even i can't figure whats the problem with you . There is nothing bad with installation guide it is same as older ones. The recovery is from RR zip file. Its a working recovery and for daily use. I really don't know if SKU versions matters. Its the variant what we need. Confirm that you have tried everything and the above twrp is not fit into your expectations . I have flashed several roms with this recovery.
Click to expand...
Click to collapse
i don't have any expectations. i just think it is correct to state where you find the files you post. if the people brick using the files in your thread reply and help them ..or put a message in your OP with correct steps . a lot of noobs are coming for help after this thread ( that is not my doing , my expectation or my problem but i try to help them )
i don't know why you mirror other people's work without putting source and credits and without mirroring correct instructions but you go to other threads with full expectations of extra screenshots and changelogs and versions and sources and leave your suggestions
i think we are working around your expectations . keep the files here and help the people i enjoy that , that is cool for xda . but always tell the truth and give credit .
magisk and xposed official is working but you don't change your thread to tell the truth , you put other devs work without credit or thanks .
KevMetal said:
read this thread from the top to fix your device and press the thanks button ..read it ALL
https://forum.xda-developers.com/mo...woods-xt1762-build-nma26-42-75-t3688609/page5
read this too where I explained to another user bricking from this thread
https://forum.xda-developers.com/moto-e4/help/help-boot-stuck-twrp-t3713486
Click to expand...
Click to collapse
boot.zip & recovery.zip are stock file with no change theirs nothing new in it that you have to flash no-verity zip in a half custom and half stock Rom. i already dumped whole firmware through miracle tool. Theirs a guide already available in this forum on *how to dump firmware through miracle tool*. So they can extract their own.
here i help this guy PM from your thread after helping two other guys in last two days if you like i post screenshot here ...why you didn't help them bricking from your post
i don't have expectations ..these guys had expectations from your post but you expect other guys to help them fix or just to leave them hanging ..anyway peace and prosperity and i will stay away from your posts bro :good:
enjoy XDA but maybe you can see one day you request a lot stuff from other guys threads but just give nothing you request from other guys in your posts ..its just a thought ..you don't need to agree or change your ways
KevMetal said:
i don't have any expectations. i just think it is correct to state where you find the files you post. if the people brick using the files in your thread reply and help them ..or put a message in your OP with correct steps . a lot of noobs are coming for help after this thread ( that is not my doing , my expectation or my problem but i try to help them )
i don't know why you mirror other people's work without putting source and credits and without mirroring correct instructions but you go to other threads with full expectations of extra screenshots and changelogs and versions and sources and leave your suggestions
i think we are working around your expectations . keep the files here and help the people i enjoy that , that is cool for xda . but always tell the truth and give credit .
magisk and xposed official is working but you don't change your thread to tell the truth , you put other devs work without credit or thanks .
Click to expand...
Click to collapse
even i am a bit busy these days. i don't have my pc right now so i can update my thread. I already thanked the official thread. Some e4 users randomly throw pm everytime to upload a working recovery. I did. Ok so you want to be a king in this forum. Looks like xposed and twrp threads bother you. i will take these thread down.
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.
Doesn't XT1685 equal G5 Plus?
Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs
Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.
leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs
Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!
I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.
Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.
leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.