Having a nightmare trying to install xiaomi.eu hermes ROM - Redmi Note 2 Q&A, Help & Troubleshooting

Hello all, hopefully someone here can help me. I've wasted the past 2 days trying to install the xiaomi.eu ROM file. I am currently running MIUI 7.0 Stable.
After downloading the hermes file moved it onto the phone and attempted to use the updater app to install. I receive the error message "update.zip signature verification failed" after trying this. Doing some searching it seems that I need to install TWRP and SuperUser to enable me to do this.
So attempting to install TWRP. I followed the instructions to the letter yet TWRP is not there. The phone still goes into the default MIUI recovery. Here is the log from the cmd prompt:
target reported max download size of 134217728 bytes
sending 'recovery' (13370 KB)...
OKAY [ 0.674s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.912s
I have also tried to flash using the MI PC Suite but I cannot use the recovery option as I need to make a back up. However, the software won't let me create a back up.
I have also installed Flashify on the phone but it always crashes when I select Recovery Image > Choose file.
Can anyone offer any advise? I am at my wits end here and don't know how to proceed.
(Can't post links as I am new but I used the intructions on miui and xiaomi.eu)
Thanks in advance.

Michael92 said:
Hello all, hopefully someone here can help me. I've wasted the past 2 days trying to install the xiaomi.eu ROM file. I am currently running MIUI 7.0 Stable.
After downloading the hermes file moved it onto the phone and attempted to use the updater app to install. I receive the error message "update.zip signature verification failed" after trying this. Doing some searching it seems that I need to install TWRP and SuperUser to enable me to do this.
So attempting to install TWRP. I followed the instructions to the letter yet TWRP is not there. The phone still goes into the default MIUI recovery. Here is the log from the cmd prompt:
target reported max download size of 134217728 bytes
sending 'recovery' (13370 KB)...
OKAY [ 0.674s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.912s
I have also tried to flash using the MI PC Suite but I cannot use the recovery option as I need to make a back up. However, the software won't let me create a back up.
I have also installed Flashify on the phone but it always crashes when I select Recovery Image > Choose file.
Can anyone offer any advise? I am at my wits end here and don't know how to proceed.
(Can't post links as I am new but I used the intructions on miui and xiaomi.eu)
Thanks in advance.
Click to expand...
Click to collapse
I read somewhere, and have saved to a text file: "You obviously didn't read the thread. The instructions works only for those on developer ROM which has root access. If you are on stable ROM you need to do the following:
1) Download supersu.zip and transfer the file to your phone's internal memory
https://download.chainfire.eu/696/SuperSU
2) Download the twrp287.zip from this thread. Rename it to update.zip, transfer it to your phone and install through the updater app.
3) The updater app will reboot your phone automatically when the installation is complete. Once the screen turned off, quickly hold the volume-up button to enter recoevery. You will see TWRP recovery.
4) While in TWRP, flash the supersu.zip to get root access. Reboot your phone once done.
5) Once your phone rebooted into android again, use any file explore with root access to delete recovery-from-boot.p or renamed it to recovery-from-boot.bak from system folder.
6) Your TWRP should work from now on and persist through reboots.
Hope you managed to get it working. The material interface rocks!"
Sent from my Redmi Note 2 using Tapatalk

Related

[Q] LG P769 Restore Issue

Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app

[Q] Possible soft brick, please advise

Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.

Mate2-TWRP Install Issue

Hello everyone. I had TWRP installed on my Mate 2. There was some update a few months ago and now I can no longer boot into TWRP. All I get is the stock recovery. ADB install of TWRP always reports successful (OKAY [ 0.797s]). Graphical installation always fails however ("Something is wrong" error).
Has anyone been through this? Nothing I do seems to get me back to being able to use TWRM.
Ascend Mate 2 running B147 rooted and unlocked from Consumer Cellular.
Bill R said:
Hello everyone. I had TWRP installed on my Mate 2. There was some update a few months ago and now I can no longer boot into TWRP. All I get is the stock recovery. ADB install of TWRP always reports successful (OKAY [ 0.797s]). Graphical installation always fails however ("Something is wrong" error).
Has anyone been through this? Nothing I do seems to get me back to being able to use TWRM.
Ascend Mate 2 running B147 rooted and unlocked from Consumer Cellular.
Click to expand...
Click to collapse
There is numerous posts that walk you through it. General and question threads.
Moody66 said:
There is numerous posts that walk you through it. General and question threads.
Click to expand...
Click to collapse
Agreed, there are, and I have been through and tried many including:
Downloading TWRP Manager and install from there
Down;load Flashify and install fropm there
Install via ADB Fastboot
Copying image to SD card and flashing from there
Copying update to SD card and flashing from there
None has worked. I'mk thinking the one and only update I received changed the boot partition or something.
Bill R said:
Agreed, there are, and I have been through and tried many including:
Downloading TWRP Manager and install from there
Down;load Flashify and install fropm there
Install via ADB Fastboot
Copying image to SD card and flashing from there
Copying update to SD card and flashing from there
None has worked. I'mk thinking the one and only update I received changed the boot partition or something.
Click to expand...
Click to collapse
147 is what I had. http://forum.xda-developers.com/ascend-mate2/general/guide-cc-variant-to-oem-convertion-t3149767
I have tried that particular one as well. It appears to install but when I go into recovery I get the stock recovery.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.438s]
finished. total time: 0.922s
Bill R said:
I have tried that particular one as well. It appears to install but when I go into recovery I get the stock recovery.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.438s]
finished. total time: 0.922s
Click to expand...
Click to collapse
Download quick boot from play store and try rebooting into recovery.
If that doesn't work try this.
http://forum.xda-developers.com/ascend-mate2/general/root-b321-t3182399
fastboot boot TWRP.img (with your phone still connected to PC)
Sent from my MT2L03 using XDA Free mobile app
Moody66 said:
Download quick boot from play store and try rebooting into recovery.
If that doesn't work try this.
http://forum.xda-developers.com/ascend-mate2/general/root-b321-t3182399
Click to expand...
Click to collapse
You are a life saver! Your link led me to this which fixed my issue.
http://forum.xda-developers.com/showpost.php?p=62380283&postcount=754
Renamed update.app to update.appx and rebooted to recovery. Thank you again very much!
Bill R said:
You are a life saver! Your link led me to this which fixed my issue.
http://forum.xda-developers.com/showpost.php?p=62380283&postcount=754
Renamed update.app to update.appx and rebooted to recovery. Thank you again very much!
Click to expand...
Click to collapse
You are welcome. It was Xordos that figured it out.

Issues with recovery and fastboot

After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.

BV6000s : unable to install TWRP

Hey guys, I do not think this is a re-post of the other TWRP problems on Blackview 6000s. I have tried to install TWRP on my device many times. When I reboot into the custom recovery, a android with a danger sign appears. Instead of the TWRP screen. So what is the problem? (Android Noob here, please don't throw big developer words ).
Have tried
1. Changing USB ports / Using different computers
2. Flash_tool.exe
3. Flashing though adb/fastboot (is it the same?)
4. Different versions of TWRP.
5. Enabled USB debugging, OEM unlock & Install from Unknown Sources
Error Messages:
1. Running this -> adb reboot bootloader
error :no devices/emulators found (device was detected in "fastboot devices")
2. Running this -> fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9318 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.142s
(However, TWRP is not installed?)
Problem is solved, if u need help pm me
Hi,
Its good phone? Worth to buy it?
off160 said:
Hi,
Its good phone? Worth to buy it?
Click to expand...
Click to collapse
Yes, it is. It is a damm good phone. Pm me for more details.
Managed to solve issue. flashed wrong TWRP file lol
ROM for the bv6000s MT6737T?
DoctStrange said:
Managed to solve issue. flashed wrong TWRP file lol
Click to expand...
Click to collapse
Hi did you manage to find a ROM for the phone?
Hello
Might I know what ROM you are using, and where you got the TWRP? I managed to flash TWRP once on the device, and then install SuperSU when it had a previous ROM.
But I flashed it with blackview's latest ROM I found on their website. Since then, when I flash TWRP, the phone won't boot anymore
I'm using TWRP3.0.0, which is the latest one I found with a scatter file.

Categories

Resources