I bought this phone 2 weeks ago and it came with multi lang. MIUI 6 ROM. I flashed TWRP normally, flashed eu.developer ROM. After that 2 new updates came out and after last update i tried to flash TWRP to install and try AOSP ROM but when i install TWRP it reverts to Mi Recovery. Tried installing from updater app, fastboot, Mi Recovery and nothing works, always goes back to Mi Recovery.
Stock recovery is restored by stock rom on boot. To get into twrp:
* flash twrp from stock recovery
* reboot phone from recovery and hold vol up to get into recovery again
Hey mate had the exact same problem.
Solved it by flashing this particular TWRP as per instructions (direct link to the file)
Very annoying problem, easy fix tho
Solved it before but thanks for help. (feel dumb now haha)
I must be doing something wrong. Each and every time I try to use the updater app to install the update.zip (the renamed twrp287.zip) I get a "Install update.zip failed!" update.zip signature verification failed. So then I attempt to fastboot boot recovery.img and it fails with FAILED (remote: unknown command).
I've read somewhere that the latest update makes it impossible to go backwards (i.e downgrade to a previous ROM) using the stock recovery which would probably explain why the update.zip failed but not why the fastboot boot recovery.img failed.
I'm using linux and the normal adb/fastboot stack installed with Android Tools. Any guidance please? Note I don't want to replace the stock recovery at the moment, I just want to install gapps.
Using fastboot:
fastboot oem unlock
fastboot flash recovery recovery.img
Using MiRecovery:
Did you signed the .zip file? Is it a flashable .zip file? Which version of miui have you?
Or maybe use flashify
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
Using fastboot:
fastboot oem unlock
fastboot flash recovery recovery.img
Using MiRecovery:
Did you signed the .zip file? Is it a flashable .zip file? Which version of miui have you?
Or maybe use flashify
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
Unfortunately that doesn't work.
sudo fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.002s
The zip is the very same one in the linked post above, so yes it is a flashable zip , I have miui 7 5.10.16 on the redmi note 2.
I'll try flashify. No luck with flashify either!
blairpoodle said:
Unfortunately that doesn't work.
sudo fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.002s
The zip is the very same one in the linked post above, so yes it is a flashable zip , I have miui 7 5.10.16 on the redmi note 2.
I'll try flashify. No luck with flashify either!
Click to expand...
Click to collapse
Downloaded the file from post #3 above, unzipped it and copied the recovery.img file to either phone sstorage or external sd card, then flashed by fleshify. Hope it help.
Sent from my 2014817
...
Related
Edit: The official ATT 4.4.2 sbf has been released, and this rom was built from that.
This CWM/TWRP flashable zip is from the sbf of 165.44.1.ghost_att.ATT.en.US (ATT xt1058). The modem and kernel are within the zip and must be flashed manually. The instructions below are mostly for rooted, locked ATT phones using safestrap.
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Unlocked phones: You can flash the zip and manually flash boot.img, NON-HLOS.bin and fsg.mbn.
ATT locked phones:
If you can still get root, then you can use safestrap to install this zip of ATT 4.4.2 /system and get root again. Also within the zip is the official ATT 4.4.2 boot.img, NON-HLOS.bin and fsg.mbn (for fastboot). This zip does not alter your bootloader.
Prerequisite:
Rooted Moto x
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA..
Safestrap instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-442-165.44.1.ghost_att-ss.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
extract boot.img, NON-HLOS.bin and fsg.mbn from the .zip to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: wipe/factory reset (WARNING. THIS WILL WIPE YOUR USERDATA. This step may be optional for some users.)
twrp: flash rom (motox-442-165.44.1.ghost_att-ss.zip) to the stock-slot (be patient)
twrp: immediately flash supersu .zip
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below).
Fastboot commands: Note: If you use MotoWPNoMo, then you should skip "flash recovery"
Code:
fastboot flash boot boot.img
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Downloads:
motox-442-165.44.1.ghost_att-ss.zip: http://www.androidfilehost.com/?fid=23329332407589378
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
If you hang up during flashing the rom, I had success by flashing supersu first. Then it worked like a charm. Very helpful for me!
Sent from my XT1058 using Tapatalk
I was coming from 4.2.2 and flashing this without updating the modem to at least 4.4 will cause problems:
1. Security setting cannot be opened
2. User apps cannot be uninstalled
Updating my modem to 4.4 resolves both problem.
The sbf was released, and I made a new CWM/TWPR flashable zip using the sbf. The new zip contains the official 4.4.2 modem in addition to the kernel.
I tested the new zip on my phone, and the link is in the op.
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
rmead01 said:
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
Click to expand...
Click to collapse
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Ctrl-Freak said:
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Click to expand...
Click to collapse
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
rmead01 said:
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
Click to expand...
Click to collapse
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Ctrl-Freak said:
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Click to expand...
Click to collapse
Not sure. Bootloader version 30.B2
I had 4.4 rooted and downloaded the files in your post. Was I suppose to remove the the 3 files from the zip or just copy them out? I extracted them but left the 3 files also in the zip file. I copied the zip file to my sdcard. installed safestrap. made a nandroid. flash the zip, flashed the SU, followed the fastboot commands and that's what I got.
---------- Post added at 10:41 AM ---------- Previous post was at 10:26 AM ----------
Here's my input though. I'm on 4.4.2. I'm rooted. I have the 4.4.2 kernel version. My phone actually feels much snappier. Not sure if that's from the cache clear or not but it's extremely noticable how much smoother it is. I have safestrap installed and can reboot to it. All in all i'd call this a success
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Ctrl-Freak said:
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
Click to expand...
Click to collapse
Exactly it! :good:
frenchie007 said:
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Click to expand...
Click to collapse
Kitkat 4.4 does not work in a rom slot. I am guessing 4.4.2 is the same.
If you are running the 4.4 bootloader and MotoWPNoMo, you do not need to flash recovery. If you do try to flash recovery, just ignore the error.
I made a note in the op. Thanks rmead01.
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
natezire71 said:
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
Click to expand...
Click to collapse
Yes
I was running Android 4.4 already when doing this process. I skipped the step of wiping user data and followed the steps exactly. (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there). I had no issues at all and when the bootloader commands were done I pressed the power to select reboot in the bootloader. Phone rebooted, optimized 327 apps, and I'm done. 4.4.2 running great with root and no loss of any data.
Major thumbs up for posting this!! Thank you and god bless XDA-developers!! This forum is invaluable!!!!
Oh I am on a locked bootloader by the way. AT&T locked but safestrap worked great.
Apollo_316 said:
... (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there)...
Click to expand...
Click to collapse
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Ctrl-Freak said:
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Click to expand...
Click to collapse
I figured it was pointless but a previous poster in this thread said they did that too and my bottom line was ensuring I don't lose root above all else. Thanks for pointing that out though. I remember it was formatting /system for a while and I wondered about superSU being in there but wasn't sure what was going to happen.
I'm on rooted 4.4, AT&T locked bootloader, write protection off.
If I install this via safestrap, after this is installed and I'm on 4.4.2 rooted with write protection off, can I then remove safestrap while maintaining my rooted, write protect off, 4.4.2 update?
Sent from my XT1058 using XDA Premium 4 mobile app
I have Z2 D6503, I had once rooted and installed recovery on my phone and left it that way, few days ago I tried to install a rom from recovery, phone wasn't booting to recovery, since then I tried any guide to root and install recovery even till version 17.1.2.A.0.314. and none was working, anybody had this problem?
what can I do to fix it, the phone was already formated from data so any solution is a good one,
thanks in advance, Amir.
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
convict_moody said:
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
Click to expand...
Click to collapse
found one, but I get an error:
Code:
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.003s
not boot.img, recovery.img
download twrp recovery image from their site, and use that one. boot.img is the kernel not the recovery
convict_moody said:
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
Click to expand...
Click to collapse
ticktock666 said:
not boot.img, recovery.img
download twrp recovery image from their site, and use that one. boot.img is the kernel not the recovery
Click to expand...
Click to collapse
I get this error while i'm doing the command:
fastboot boot recovery.img
Click to expand...
Click to collapse
when recovery.img is the twrp recovery image.
CosTuMe said:
I get this error while i'm doing the command:
when recovery.img is the twrp recovery image.
Click to expand...
Click to collapse
Did you try using another PC, or another pc port?
convict_moody said:
Did you try using another PC, or another pc port?
Click to expand...
Click to collapse
true, forgot about it, but now getting this:
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
CosTuMe said:
true, forgot about it, but now getting this:
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I believe in this case if u used command:
Fastboot flash recovery boot.img
It will work, I think the recovery u are trying to boot is twrp,
If u got an error that the image isn't a boot image or something like that, redownload the recovery and try again.
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
Stuck on "Powered by ANdroid". No recovery, only fastboot & rescue mode.
Hello,
I have Honor 7 PLK-UL00, and it is stuck on "Powered by Android" screen. The bootloader is unlocked. I can only go into fastboot or rescue mode. I cannot enter recovery or erecovery mode. I have tried flashing img files through fastboot of Android 6.0 B360, Android 5 B130 and Android 5 B788 but still no luck . The only option that seems left to me is flashing zip through fastboot. Does anybody here have the zip of stock or custom rom that i can flash through fastboot or anybody help me in making the zip.
The problem occurred after I had restored Modem, 3rdmodem, Dtimage, etc using "Partition Backup & Restore" app. Then I restarted, and this problem occurred.
Any help would be appreciated.
Thanks.
I had the exact same problem, i think its because modem partition is corrupted. I tried to extract modem.img from update.app and flash it by twrp dd command, its not working. so if some one with normal system can use dd if=/dev/block/mmcblk0p30 of=/sdcard/modem.img to dump a valid backup maybe it can be used to restore modem.
---------- Post added at 10:01 AM ---------- Previous post was at 09:09 AM ----------
crazyboy24 said:
Hello,
I have Honor 7 PLK-UL00, and it is stuck on "Powered by Android" screen. The bootloader is unlocked. I can only go into fastboot or rescue mode. I cannot enter recovery or erecovery mode. I have tried flashing img files through fastboot of Android 6.0 B360, Android 5 B130 and Android 5 B788 but still no luck . The only option that seems left to me is flashing zip through fastboot. Does anybody here have the zip of stock or custom rom that i can flash through fastboot or anybody help me in making the zip.
The problem occurred after I had restored Modem, 3rdmodem, Dtimage, etc using "Partition Backup & Restore" app. Then I restarted, and this problem occurred.
Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
flash zip via fastboot wont work:
Y:\>fastboot update fb.zip
target reported max download size of 471859200 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (remote: Command not allowed)
finished. total time: 0.002s
walterclozet-g said:
I had the exact same problem, i think its because modem partition is corrupted. I tried to extract modem.img from update.app and flash it by twrp dd command, its not working. so if some one with normal system can use dd if=/dev/block/mmcblk0p30 of=/sdcard/modem.img to dump a valid backup maybe it can be used to restore modem.
---------- Post added at 10:01 AM ---------- Previous post was at 09:09 AM ----------
Click to expand...
Click to collapse
Did you try flashing zip through twrp? Stock or custom?
My device is not even entering in recovery mode, not even TWRP or erecovery.
flash zip via fastboot wont work:
Y:\>fastboot update fb.zip
target reported max download size of 471859200 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (remote: Command not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
Can you upload fb.zip, so that the devs here can have a look and help.
crazyboy24 said:
Did you try flashing zip through twrp? Stock or custom?
My device is not even entering in recovery mode, not even TWRP or erecovery.
Can you upload fb.zip, so that the devs here can have a look and help.
Click to expand...
Click to collapse
1. i tried to flash custom zip rom(includes system.img, cust.img, boot.img) by twrp, not working.
2. i tried to extract system.img, cust.img, boot.img from stock 7.5.1 and 7.4.16 rom to replace custom rom files and flash by twrp, not working.
3. i can enter rescue mode by pressing vol+ vol- and power key let it boot twice usb should not be plugged. i can enter twrp or stock recovery(it will try to flash /sdcard/dload/update.app, but always fail at 5%)
4. i tired to flash 3rdmodem by twrp then flash stock recovery in fastboot mode, enter rescue mode, the ui now shows in english, but still fail at 5%.
5. i tired to extract 3rdmodem, modem use twrp command dd to ovewrite thoese partitions, not working.
6. i tired to pack modem.img to flashable zip using huawei update extractor, set it to /dev/block/mmcblk0p30, not working.
7. you can flash twrp in fastboot unplug usb cable then press vol+ vol- power, the phone will reboot, then screen bacame black, release those buttons, twrp should boot. it may take 30 seconds to enter.
https://drive.google.com/open?id=0Bw7c08wWGiqic2EyZ0R0QzAyR0E replace those img files.
i used dc phoenix tool to unbrick my phone, it boots, but sim can only use 2g network. if the card slot is set to be 4g one, card will be unable to enable or just wont detect sim card.
walterclozet-g said:
i used dc phoenix tool to unbrick my phone, it boots, but sim can only use 2g network. if the card slot is set to be 4g one, card will be unable to enable or just wont detect sim card.
Click to expand...
Click to collapse
Can you explain the steps in detail?
crazyboy24 said:
Can you explain the steps in detail?
Click to expand...
Click to collapse
first contact dc-tool for free test, then buy 15 credits from the website. then download dc-phoenix tool, reboot phone to fastboot, using method 1 with correct update.app(using the wrong one, it will fail when trying to flash). when it finished, if the phone can boot normally, use vol + vol- power to force flash from sd:\dload\update.app. then the phone will be ok. if method 1 didn't work, then you may try method 2, i tried that, but my phone won't work with gsm sim if set as 4g card, only cdma card can.
detail info: https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
if the phone is unbricked, they will require you to post a thread explaing how to unbrick the phone, send the thread link to them, you will get refund. i did that last week.
this is the thread i posted, you can see what i did. but remember try not to use method 2, you may lost serial number and gsm sim card may not be supported, i cant fix that.
Hi everyone !
Some month ago I flashed on my device a beta test of Nougat for Honor 5c. Yesterday I wanted to leave it and go back to a stable rom but I was unable to find a flashable ZIP of stock Rom so I used FlashFire to flash a update.app firmware package (some **** from Huawei...).
After flashing it I tried to reboot my phone but I just got a Error Mode - Please update your system again. (and Recovery image error + load error)
To solve this I reboot to fastboot and on my computer I tried to flash TWRP with fastboot flash recovery twrp.img and I got a error : remote : command not allowed. I search and search and search on forums but I found nothing.
I tried some other fastboot commands, i tried to boot from a img, ... but nothing, just Command not allowed.
I have a Honor 5c NEM-L51, fastboot is "working" lol, no recovery, no force dload update, bootloader unlocked, FRP lock (idk what is this), i was rooted with Magisk and I flashed the package with FlashFire.
Please help me :crying:
Siffrein