Bootloop after manual update (B140>B170) - Honor 7 Q&A, Help & Troubleshooting

Hello, I'm stuck in bootloop after I manually updated as in topic title. My phone is locked and unrooted.
I tried to flash the .img files using the multitool but I get the error FAILED (remote: Command not allowed).
What does it mean? Do I have to unlock the bootloader? If so, how do I get the code (I can't access the phone to get the serial number...)?
Thank you for your help!

Related

Help! Can't root build 2.73.728.5

Hello all,
I confess, I am truly a newb here, so please try to keep it as simple as possible.
I have tried rooting my new hero, but with no success. First of all, it came without Android Market, which was confusing. I installed it using vending.zip I found somewhere, but that didn't help as well - it didn't download anything AND kept crashing again and again.
I tried flashing it using Flashrec, but that also failed after Flashrec told me it failed to run the command (when trying to backup the recovery image). After that I tried fastboot and hboot, neither worked.
Could anyone help me out?...
see this thread:
http://forum.xda-developers.com/showthread.php?t=563256
no answers yet
And it doesn't seem likely there will be an answer there..
Does it?...
What can I do? Is there a way to downgrade or replace the ROM I have with a European rom?
Further more...
When trying to use a recovery image in fastboot mode, I get the following result:
I type:
Code:
fastboot boot cm-hero-recovery.img
And the response is:
Code:
downloading 'boot.img' ... FAILED (remote: not allow)
You cannot flash that version atm. The thread csasek linked you too is people trying to do what you are doing. Read that thread and post helpful idea's in there

Bootloader help

Hi guys!
Today, i decided to unlock bootloader to root my moto e. I did not want to download the 1.1 GB android sdk file so i used another option.
I just had to download a small file <500kb. I cannot post links right now cuz i haven't posted much.I followed the instructions correctly but when unlocking i get error:
<bootloader> Failed to erase partition
<bootloader> General Unlock Failure!
<bootloader> OEM unlock failure!
FAILED <remote failure>
However, i still got the bootloader unlocked warning on my phone. So i am in doubt: Is the bootloader unlocked correctly in my phone or not? Should I proceed to root it?
MrKarma4ya said:
Hi guys!
Today, i decided to unlock bootloader to root my moto e. I did not want to download the 1.1 GB android sdk file so i used another option.
I just had to download a small file <500kb. I cannot post links right now cuz i haven't posted much.I followed the instructions correctly but when unlocking i get error:
<bootloader> Failed to erase partition
<bootloader> General Unlock Failure!
<bootloader> OEM unlock failure!
FAILED <remote failure>
However, i still got the bootloader unlocked warning on my phone. So i am in doubt: Is the bootloader unlocked correctly in my phone or not? Should I proceed to root it?
Click to expand...
Click to collapse
Just go to fastboot (pressing power and volume down keys) and check bootloader status!

Unlocking bootloader leads to "status unavailable"

I used flashtool to unlock my bootloader after following the procedure layed out here: http://www.droidviews.com/how-to-unlock-bootloader-on-sony-xperia-m4-aqua/
Specifically I created a new dir under "C:\Users\Admin\.flashTool\registeredDevices" with my device name "SDDSF334343" then inside that dir created an empty file called "ulcode", and inside that file inserted the unlock code I received from Sony (using the M model and my IMEI).
The flashtool did not complain and said "unlock complete" or some such and prompted me to reboot my device. However upon checking at *#*#7378423#*#* it shows "unavailable" for the bootloader unlocked status, and attempting to flash the recovery with "fastboot flash recovery recovery.img" gives "writing recovery FAILED <remote: Command not allowed>", so obviously the bootloader isn't really unlocked it seems.
I found this post http://forum.xda-developers.com/showpost.php?p=63328460&postcount=406, with someone who had a similar problem, but I don't understand what he means by remove the "0x"; my ulcode file does not contain this prefix anyway, only the unlock code I got from Sony and pasted in.
Any ideas?
Other info
Android version 5.0. Firmware: 26.1.A.2.167. Model number E2303. I used Flashtool v0.9.19.8 along with the minimal adb fastboot install (although I also tried again with the latest full Studio download, ugh). Flashtool reported success regards to unlocking, and allows me relock and lock again repeatedly etc
I noticed my phone has the "Bootloader unlock allowed: No" (after dialing *#*#7378423#*#*) before I try and unlock with Flashtool. Does this mean it really, genuinely cannot be unlocked, or does it just mean not officially?
Do I need to flash my phone to another version of the stock firmware to get around this problem? If so which version and would it break everytime my phone updated?
(If I understand things correctly, I can flash to another stock ftf even without unlocking the bootloader using Flashtool)
I started with 26.1.A.2.167 then my phone did it's update recently to 26.1.A.3.111. Neither of these firmwares made a difference to the above. Should I just pick a random stock ftf from XperiFirm?
I'm trying to unlock an e2306 that reports "Rooting Status: Bootloader unlock allowed:no"
I follow the same procedure as the OP and the status turns to "Unavailable" but I do not seem to be able to get root access after this. If I repeat the BLU procedure I can re-lock the Bootloader and the status returns to "unlock allowed: no".
Does "unlock allowed: no" really mean no? My understanding of the tutorials I've found is that it doesn't matter. I may also just be missing something.
fpghost84 said:
I used flashtool to unlock my bootloader after following the procedure layed out here: http://www.droidviews.com/how-to-unlock-bootloader-on-sony-xperia-m4-aqua/
Specifically I created a new dir under "C:\Users\Admin\.flashTool\registeredDevices" with my device name "SDDSF334343" then inside that dir created an empty file called "ulcode", and inside that file inserted the unlock code I received from Sony (using the M model and my IMEI).
The flashtool did not complain and said "unlock complete" or some such and prompted me to reboot my device. However upon checking at *#*#7378423#*#* it shows "unavailable" for the bootloader unlocked status, and attempting to flash the recovery with "fastboot flash recovery recovery.img" gives "writing recovery FAILED <remote: Command not allowed>", so obviously the bootloader isn't really unlocked it seems.
I found this post http://forum.xda-developers.com/showpost.php?p=63328460&postcount=406, with someone who had a similar problem, but I don't understand what he means by remove the "0x"; my ulcode file does not contain this prefix anyway, only the unlock code I got from Sony and pasted in.
Any ideas?
Other info
Android version 5.0. Firmware: 26.1.A.2.167. Model number E2303. I used Flashtool v0.9.19.8 along with the minimal adb fastboot install (although I also tried again with the latest full Studio download, ugh). Flashtool reported success regards to unlocking, and allows me relock and lock again repeatedly etc
Click to expand...
Click to collapse
Your bootloader is inlocked, show Unavailable due to unlocked allowed: NO.
For fix remote failed when trying to flash recovery if you have windows 10 reboot in boot repair and choose disable driver certificate check then flash your recovery using fastboot.
Sorry for reviving an older thread, this is my first post so I hope it ends up being relevant. I am guessing the cause for me is similar since I am having the same problem using windows 7. I don't have a link handy, but i was able to get around it using a thread here on xda. Just search twrp bl locked m4 download the rootkit that matches your firmware and twrp installer file. Hope this is useful to someone.
Did you fix your's?
Mine says Rooting status: Unavailable
I can't flash recovery and img
I get Failed(remote:Command not allowed) in Fastboot
What I did in the first place was I unlocked my m4 aqua e2333 lollipop then root it using fastboot, it was successful then I decided to hard reset mine by deleting the system in recovery(I know I'm so stupid) then I'm stuck in the booting screen so I decided to download the marshmallow version then I took the system and put it in my phone using recovery,of course it didn't work because I'm in lollipop version and the system is from marshmallow then I flashed it using flashtool and it's successfu,l It worked!
But after that I get the Rooting Status:Unavailable
And can't flash anything except Ftf files and my sim 1 slot is not working,if I use both slot both won't work.
I can't find the right stock ftf for e2333 Lollipop(26.1.B.3.109_R6A)
I need the Stock ftf
I want to root and install different roms again
I'm new to Xperia and this is my first Xperia phone ever
Please help asap
Ps. At first it's Rooting Status: bootloader unlocked yes
I activated My Xperia
I think My Xperia is the problem
I read it somewhere here the when you unlocked you bootloader and activated My Xperia....I can't remember...
Is there's a way I can remove My Xperia in an ftf file?

Bootloader Unlocked but says "FAILED (remote: Command not allowed)"

I'm trying to flash system.img using fastboot. However it says "FAILED (remote: Command not allowed)"
I can access fastboot and Recovery.
I'm doing this because I have no OS due to accidental wipe.
I'm using Huawei Mediapad M2 801L
Caelestiel said:
I'm trying to flash system.img using fastboot. However it says "FAILED (remote: Command not allowed)"
I can access fastboot and Recovery.
I'm doing this because I have no OS due to accidental wipe.
I'm using Huawei Mediapad M2 801L
Click to expand...
Click to collapse
Already another thread here. http://forum.xda-developers.com/android/help/help-please-help-to-unlock-bootloader-t3514419/page1
Please use search and read before posting. It keeps the forums clean . Copy and paste the adb/fastboot log you got here so that we can help you better. Also you can flash a custom rom and get things straight if you have a custom recovery like TWRP or CWM installed.

Fastboot can't flash anything after upgrade to B389

Hi~
My phone is huawei honor 7.
Fist, I'm sure I have unlocked my bootloader.
I upgrade to B388 today by fastboot flash cust.img and boot.img and system.img which extract from huawei's official update.app.
Then the phone reboot and I leaved for a while, but when I come back, I found it has replace my twrp by official recovery.
So I just reset my phone and wipe cache. When I reboot to system, I receive an OTA update, and I choose "Download latest full package" then the phone finish update by itself. So my phone now running EMUI 4.0.3 B389.
Finally, I enter fastboot model by "adb reboot bootloader" and try to flash twrp, it tell me:
Code:
PS E:\Root\platform-tools> fastboot flash recovery E:\Root\twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (25890 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.570s
I try to flash some old version system, but I got same error. But I type " fastboot oem get-bootinfo" It shows that I was unlocked.
So how can I flash twrp again and Root my phone?
--------------------------
By the way, I found I even can not relock my oem by now!
Code:
C:\Users\omicron3069>fastboot oem relock 23**********9971
...
FAILED (remote: stat not match)
finished. total time: 0.000s
C:\Users\omicron3069>fastboot reboot
rebooting...
finished. total time: 0.125s
hmmmm... solve this weird problem by turn on "unknown source " switch in security setting.
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
alperenadalar said:
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
Click to expand...
Click to collapse
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
omicron3069 said:
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
Click to expand...
Click to collapse
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
alperenadalar said:
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
Click to expand...
Click to collapse
Have you wiped system? That could be the error that twrp gives.
Edit: Don't forget to make a backup of system and data!
Even if the bootloader screen says that the phone is unlocked, in reality it isn't and that's why you are getting the command not allowed text. Just type fastboot oem unlock and your code to unlock it again. The same problem is present on many Huawei phones like the P8 and P9 Lite I've tested after installing an update.
if you want to emui4.0 to 3.0 it was impossible
HUAWEI big chrysanthemum and foolish engineer doesnt want you to flash emui3.0 But you can use the hisuite to demotion.I hope reply is very useful to you

Categories

Resources