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.
Related
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
Returning to Stock
Hi guys, I want to recover my ZenFone 2 to stock to remove TWRP to do the OTA, but idk how to do it at all. I am complete noob, never before done this things. Someone can pls help me 100% step by step ty.
Whats your phone full name
Sent from my GT-I9300 using XDA Free mobile app
HIS YB said:
Whats your phone full name
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Z00AD. I have the 551ml 2gb.
Download an official ROM for your Zenfone 2 and the official recovery of the version of your rom.
Boot your phone on Fastboot mode
Start shell and type "fastboot devices"
If your device is detected, you're saved
Then type "fastboot flash recovery recovery.img" (with the .img in your recovery.zip)
Then boot in recovery mode -> Press power button + volume up button
"Apply update from adb"
Type "adb sideload UL-********.zip" on your shell
Wait and enjoy your stock rom
Cylae said:
Download an official ROM for your Zenfone 2 and the official recovery of the version of your rom.
Boot your phone on Fastboot mode
Start shell and type "fastboot devices"
If your device is detected, you're saved
Then type "fastboot flash recovery recovery.img" (with the .img in your recovery.zip)
Then boot in recovery mode -> Press power button + volume up button
"Apply update from adb"
Type "adb sideload UL-********.zip" on your shell
Wait and enjoy your stock rom
Click to expand...
Click to collapse
what is shell? and i can see the new update on gen, can I use that as stock rom? and about recovery is that what's in there too?
very noob sory.
Bump.
It's best you read and not get spoonfed for your answers. If you don't know what adb and shell commands then PLEASE don't install anything........
903tex said:
It's best you read and not get spoonfed for your answers. If you don't know what adb and shell commands then PLEASE don't install anything........
Click to expand...
Click to collapse
Oh yeah
903tex said:
It's best you read and not get spoonfed for your answers. If you don't know what adb and shell commands then PLEASE don't install anything........
Click to expand...
Click to collapse
I know what ABD is, just not shell. I rooted it in the first place after all.
In this context shell = command prompt
help
can i ask
my firmware version is (2.13.40.13) and my problem is that is has a problem in recovery when ive selecting recovery it rebooting only even ive hold power button + volumeup
how can i update it to higher version?
and does updating to higher ones replace the previous recovery?
and which is better higher version of lp or higher version of mm?
help how to update my firmware to that if that so?
sorry for bad english
hope somebody can help me !
beibyboy06 said:
can i ask
my firmware version is (2.13.40.13) and my problem is that is has a problem in recovery when ive selecting recovery it rebooting only even ive hold power button + volumeup
how can i update it to higher version?
and does updating to higher ones replace the previous recovery?
and which is better higher version of lp or higher version of mm?
help how to update my firmware to that if that so?
sorry for bad english
hope somebody can help me !
Click to expand...
Click to collapse
Do you know how to fastboot flash ?
timbernot said:
Do you know how to fastboot flash ?
Click to expand...
Click to collapse
yep ive already done that because ive recently bricked my zenfone 2 and now revive it using that procedure but sadly my firmware is at super lower 2.13.40.13 i want to update it to latest or to latest marmmallow ! but i didnt know the procedure yet ! im afraid of having bootloop again and again !
beibyboy06 said:
yep ive already done that because ive recently bricked my zenfone 2 and now revive it using that procedure but sadly my firmware is at super lower 2.13.40.13 i want to update it to latest or to latest marmmallow ! but i didnt know the procedure yet ! im afraid of having bootloop again and again !
Click to expand...
Click to collapse
So you must've flashed that raw file in AFT?
Then all you have to do is flash the latest raw instead .
Can I ask you a question.
Is your serial number correct in boot loader ?
timbernot said:
So you must've flashed that raw file in AFT?
Then all you have to do is flash the latest raw instead .
Can I ask you a question.
Is your serial number correct in boot loader ?
Click to expand...
Click to collapse
the serial that appeared in aft ? ive think (123456789abcdef)
dont know if thats the correct format
right know im searching latest raw file for ze551 then flash it to aft right then after that?
where do i get the images files that ive flash in cmd like what ive do in previous unbricking method?
and flashing thru aft with latest raw file of ze551 will required that cmd command?
Don't do anything just yet , you need your serial corrected , which if not will affect your recovery
collection of raw files on xda by realyoti.
I think .194 LP is the last one he got
You only flash it in boot loader...using AFT .
It is important to do the two part flash in AFT for restoring serial.
Check my unbrick thread , for video and AFT download...from 2:17 mins in .
Before it is xFSTK flash ..which you don't need cause you already in boot loader.
AFT raw flash from 2:17 mins in, follow procedure , at 5:56 mins in -- cmds in blue on phone screen stays on `RESULT=OK` . Shut down , force close AFT , open AFT again - load it up with raw again and press vol+ once , and finish the flash -- serial number will be corrected now ! DO NOT dislodge the data lead while doing this procedure -- let the 2nd flash finish , it will boot into system by itself , recovery will now work correctly too !
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
in short i will do aft two times? .. then my serial goes back to normal?..
and after flashing latest raw files will my recovery goes back to normal what i mean is i go to recovery when wipe and format belongs?
---------- Post added at 03:12 PM ---------- Previous post was at 02:45 PM ----------
im done thank you very much for this ive already done ... im just download the latest raw file then flash it to aft then it automatically reboot and done .. ive got it latest firmware next is how to safe root ..
beibyboy06 said:
in short i will do aft two times? .. then my serial goes back to normal?..
and after flashing latest raw files will my recovery goes back to normal what i mean is i go to recovery when wipe and format belongs?
---------- Post added at 03:12 PM ---------- Previous post was at 02:45 PM ----------
im done thank you very much for this ive already done ... im just download the latest raw file then flash it to aft then it automatically reboot and done .. ive got it latest firmware next is how to safe root ..
Click to expand...
Click to collapse
Is your serial corrected ? which will correct recovery problems too ?
If i helped you in any way ... dont forget to hit the thanks button where you think info was helpful for you and others in the future :good::good:
will u help me root ? ive search in here but the post is 2015 i dont think thats gonna work right now?
so ive wanna ask for help ! the latest and safe way ! thank you ! .. and also why some other online games getting lag ! in this zenfone 2
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
Please don't ask mods to delete threads because of successful outcomes - post your solution instead. Leave the threads up as they are a useful resource for others (at least those who search before posting! )
Thanks
Sent from my SAMSUNG-SM-G920A using Tapatalk
joesee said:
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Click to expand...
Click to collapse
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Can't flash stock ROM, can you do a detail installation log?
Pouni said:
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Click to expand...
Click to collapse
Is ur bootloader unlocked or not??
If not try unlock ur bootloader than try it ll work
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
jon7701 said:
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
Click to expand...
Click to collapse
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Vitxlss said:
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Click to expand...
Click to collapse
Did you only flash the stock rom or did you try to flash everything? If you didnt try to flash everything I would try that and make sure you have the correct stock firmware for your device before you do that. Theres not really much else you can do other than try flashing in twrp, but idk if twrp supports space chunks, but it does support images. If it really comes down to it, you can force flash the system partition in twrp, but you would need the whole system image and not space chunks.
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
The process here will work on all variants of 6X but you must use the Huawei Update Extractor Tool to get the necessary images from your devices initial firmware update.app. I have provided the images only for the BLN-L24 variant for which initial firmware is B110. Due to variants having different firmware the BXXX for the rollback might not be the same but the process is
When you attempt to rollback from Nougat/5.0 (B360) to MM/4.1 stock B110 firmware with successful updates using the dload method there is a good chance your phone will be bricked and fail to boot . The first update/downgrade from B360 firmware to B300 will boot the phone but when you do the second update from B300 to B110 firmware the phone will stay on the honor screen. This happened to me and after flashing firmware numerous times and using ADB to flash boot.img the phone was still not working but I was able to recover and get it working again thanks to the Huawei_Multi-Tool_by_Team_MT_v7.1.
Download Images and put them in the Unbrick folder of the Huawei Multi Tool.
System.img
Boot.img
Cust.img
Recovery.img
1. Put phone in fastboot by holding Vol - and connecting usb to computer
2. Unlock bootloader using command fastboot oem unlock xxxxxxxxxxxxxxx where x is your 16 digit unlock code
3. After automatic data reset put phone in fastboot again
4. Start Multi Tool and hit enter to get to main menu
5. Press U for unbrick and hit enter
6. Press 2 and hit enter to start the process
Downgrading from Nougat to MM will relock your bootloader so you must unlock it in order for the multitool to flash the files to unbrick your device. Once unbricked if you relock the bootloader your device will be factory fresh with initial firmware.
Credit to: Team MT for the multi tool and Update Extractor Tool
If this helped you give me a thanks!
No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
McRoberts said:
No luck for me had to return my phone and get a replacement
Click to expand...
Click to collapse
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.
McRoberts said:
No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.
Click to expand...
Click to collapse
Thank you. So you have another 6X now?
Yes I got today so I'm taking my time and reading a lil more. It's such a defeat taking that phone back it's my first real brick.
can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them
xSpartacusx said:
can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them
Click to expand...
Click to collapse
Look in a folder named TWRP (on your device's storage)
can you repost system.img, it doesn't seem to be available anymore. Thanks.
System. img link is error 404
Hi I wanted to take a shot and see if anyone is still on this thread that may have and is willing to help me out and relink the system.img for the initial release FW for the BLN-L24, any help would be great thanks in advance!
System.img
Boot.img
Cust.img
Recovery.img
Any chance someone has the System.img file and can reupload?
Thanks,
Greg