----------------EDIT --- GOT IT FIXED--- READ FIRST 4 PAGES OF THE THREAD----------------------- BACK TO STOCK <3 XDA
Hello, I used relock bootloader command in fastboot.... now the phone only restarts to "ERROR MODE"
It looks like that
"ERROR MODE"
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
--------------------------------------
Anybody can help me? When I restart phone this mode appears again and again, can't enter fastboot mode or recovery.. when pressing any key it restarts to this error mode...
Also phone can't be tunred off, when hard pressing POWER it will instantly reboot to this mode.
Phone doesn't show up in device manager... when doing anything via fastboot command only waiting for device...
-----------------
Can you boot into fastboot mode? is bootloader and frp unlocked?
RobertHarkness said:
Can you boot into fastboot mode? is bootloader and frp unlocked?
Click to expand...
Click to collapse
no
... it was unlocked.. than i used relock command in fastboot mode and endet here....
If you can't boot into fastboot mode then your going to have to contact huawei. Without fastboot your phones hard bricked mate
RobertHarkness said:
If you can't boot into fastboot mode then your going to have to contact huawei. Without fastboot your phones hard bricked mate
Click to expand...
Click to collapse
Ok... that sucks...
Rommco05 said:
Probably if u see this are u already in fastboot try when shows this screen plug cable to pc and write in adb >>>> fastboot devices
Attention!
Please Update system again.
[Green Android]
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
edit: ok now I see... waiting for device
---------- Post added at 07:49 ---------- Previous post was at 07:26 ----------
How happend this situation, what u do before relock bootloader?
Click to expand...
Click to collapse
The smartphone doesn't show up in adb-devices... Also dodn't see it in USB... before I did this it worked without problems.
The situation before... everything worked normal and I restarted to fastboot and tried to relock bootloader with oem relock bootloader command... after that command phone turned off and the looping error appeared... tried various button combinations also vol down + usb plugin ... but only this mode appears... also I cant turn smartphone off it restarts and restarts and restarts to this mode...
Rommco05 said:
Probably this phone need service. When u relock bootloader u have twrp or stock recovery and which system was in phone?
Click to expand...
Click to collapse
Before I did this command I had the chinese TWRP installed and Stock Rom... since the relock command doesn't delete anything of these things I think it is still here I think.... but I can't access it ...thats the problem and since the error mode doesn't start an usb-connection to Computer I can't use adb/fastboot... Thx for help guys
Rommco05 said:
Isn't good idea relock bootloader with twrp, if u want do relock always with stock recovery... :/
Click to expand...
Click to collapse
Yes was stupid idea... help would be still appreciated... Anybody know where I must send the smartphone to to repair it? (Europe/Germany)
UPDATE!!!
----I UNLOADED THE BATTERY TO 0 % NOW SO SMARTPHONE TURNED OFF----
------>CONNECTED AND RESTARTED MULTIPLE TIMES WITH USB CABLE AND BUTTON PRESSING------
------------------------>>>>AFTER 50 TRYS I AM IN FASTBOOT MODE<<<<------------------------------
WHAT DO NOW?
fastbootmessages:
PHONE Relocked
FRP Lock
When try to flash boot img via adb I get Error
target reported max download size of 471859200 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.717s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s
Rommco05 said:
I think you need to unlock booloader and after flash all imgs
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
im not sure if is this right order
Click to expand...
Click to collapse
Great!
But now next problem... when I unlock Bootloader I will need my Unlock code from Huawei Site... but can only access if if I have Model Nr (Which can be obtained only in Android) and Serial Number (Also only viewable in Android).... I have both IMEIS on the Back of my phone.... any ideas how to obtain without boot to android?
4r44444 said:
Great!
But now next problem... when I unlock Bootloader I will need my Unlock code from Huawei Site... but can only access if if I have Model Nr (Which can be obtained only in Android) and Serial Number (Also only viewable in Android).... I have both IMEIS on the Back of my phone.... any ideas how to obtain without boot to android?
Click to expand...
Click to collapse
You won't be able to unlock bootloader even if you have unlock code because of FRP. The only option is to use the DC Phoenix which uses some kind of backdoor - belive me, been there done that.
OK but maybe I can try... obtained my Serial via DC Phoenix... now only need the Product Idea when Dialing *#*#1357946#*#*. .... anybody can tell me please? :3
4r44444 said:
OK but maybe I can try... obtained my Serial via DC Phoenix... now only need the Product Idea when Dialing *#*#1357946#*#*. .... anybody can tell me please? :3
Click to expand...
Click to collapse
Not possible, you'll again need some program to directly read the bootloader code. What happened to your old one, it's always the same ?
Rommco05 said:
check here first post https://forum.xda-developers.com/p9/help/how-to-product-id-bricked-p9-t3561156
Click to expand...
Click to collapse
This is an old program, doesn't support Honor 9...
Rommco05 said:
He use it for Huawei P9, isnt id and serial on box?
Click to expand...
Click to collapse
Isn't this thread about bricked Honor 9? On the box of Honor 9 is everything except ID. Anyway, I found a newer version of the program, he can give it a try.
Ok got everything... but all time I try this Error appears in fastboot:
FAILED (remote: Command not allowed)
----------------------------------------------------
I tried to Unlock via DCPhoenix (Bought for 20 €)... it sayed it got unlocked but FRP is still locked..
"Phone Relocked"
"FRP Lock"
In Fastboot..
Rommco05 said:
Have you installed drivers (HiSuite)?
Click to expand...
Click to collapse
Yes... restore via it doesn't work.. "Your device is not supported" Error when using rescue mode.
So I think the main problem is now I can't do anything on fastboot because Bootloader is relocked (Also OEM-Unlock isnt activated in [email protected]).... So I think the only thing I can restore my 400€ Phone is to backdoor unlock it.... DC-Phoenix without success. any ideas from the real pros? Would pay 50€ if your method would work to restore my phone :/
Rommco05 said:
No no, just for drivers for communicating phone and pc. I think is some way how push imgs without unlocked bootloader
I'm not sure if is for this topic https://forum.xda-developers.com/an...stion-mounting-recover-partition-adb-t3591261
edit: I don't want money anyway...
Click to expand...
Click to collapse
Ok... I have to go to work now... will try later... I will read other posts later thank you all for help!!!!!!!!
4r44444 said:
Ok... I have to go to work now... will try later... I will read other posts later thank you all for help!!!!!!!!
Click to expand...
Click to collapse
Use this tutorial, it should work. Does it show you any error ?
https://www.dc-unlocker.com/repair-bricked-huawei-honor-7
Related
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
sguy156 said:
Unlocked phone by following steps on HTC site. Phone got unlocked without any issues now upon reboot phone is stuck on htc one boot screen What are my options do I have to flash another rom ??
Click to expand...
Click to collapse
Hold vol down as it goes through the next loop, and it will put you in bootloader. From there, you can go to fastboot mode and flash custom recovery. Then adb sideload, adb push a ROM, or load a ROM to the removable SD if you have a card reader you can connect to your computer. Then boot custom recovery and flash the ROM.
sguy156 said:
Using HTC RUU to repair the phone and I am getting ERROR [130]: MODEL ID ERROR ERROR [131]: . Any ideas what does this error means
Click to expand...
Click to collapse
It means you are trying to run the RUU for another carrier version. What version do you have (this section is for AT&T) and what RUU are you trying to run?
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
sguy156 said:
Will putting the recovery in sd card and then booting the phone work and dont I have o turn S-OFF before I can flash any ROMS ??
Click to expand...
Click to collapse
Yes if your S-OFF you can put recovery on your sdcard
http://forum.xda-developers.com/showthread.php?t=2951030
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
I thought you had S-OFF so no you can't load a custom recovery to your sdcard.
---------- Post added at 08:45 AM ---------- Previous post was at 08:36 AM ----------
sguy156 said:
I am S-ON and bootloader is relocked . Can I still flash custom recovery with S-ON and then flash ROMS ?? Rebooting the phone it says wrong img . What can I put on the sd card to flash the img for the phone to boot..
Click to expand...
Click to collapse
Try the universal drivers from the link below.
http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/#asus
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
sguy156 said:
How can I flash another recovery when the PC doesn't see it as phone. Tried two different cables . Once I get the PC to see the phone it should be ok . See the screen when the phone boots up.
Any other suggestions on getting the PC see the phone. I installed HTC sync also that didn't helped also ..
Click to expand...
Click to collapse
The PC can see the phone, otherwise you wouldn't get the Model ID error message you indicated in the first post.
So no response if you type the following in command prompt?: fastboot devices
Fastboot and/or adb connectivity issues are rather common.
Another trick you can try, is to uninstall all HTC software (Sync and drivers) from your PC. Then connect the phone. DO NOT accept any prompts to automatically install drivers or Sync. Go to Device Manager, find the device, and pick the option to manually select the drivers, and pick the generic Android MTP device drivers.
Also try different USB ports. IN particular, if the ports are USB 3.0, that is known to cause issues (you may be able to disable the 3.0 drivers).
And if your PC is Win8.1, that is also known to be problematic.
---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------
sguy156 said:
I will try universal drivers and see what happens. What commands
I need to try on the phone if these drivers work ??
Click to expand...
Click to collapse
fastboot erase cache
fastboot flash recovery filename.img
(where filename.img above is replaced with the actual name of the desired recovery file)
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
sguy156 said:
Yes trying fastboot doesn't show the phone. Is this something HTC can fix under warranty
Click to expand...
Click to collapse
Fastboot and adb connectivity issues are almost always a problem on the PC's side (ports, Win version, drivers, USB 3.0). Warranty replacement isn't going to help you.
I've given you a few suggestions on addressing the connectivity issues. You haven't indicated whether you have tried them yet, or not.
i tried your sugestions phone is showing up as HTC andriod device and running adb devices doesn't show anything. Not sure what else I can try , I am trying this on a windows 7 PC as windows 8 gave me so many issues .
@sguy156
So your running adb commands from c:\user .
I think your not navigating to adb properly.
I go to where adb and fastboot lives and Shift+right-click so I can open the cmd there
Thats what i did ran it from the location where adb and fastboot are installed same issues .
I hate to ask but do you have usb debugging on wile trying to use adb ?
Please keep an open mind as I'm trying to help ?
---------- Post added at 08:57 AM ---------- Previous post was at 08:30 AM ----------
Try this out if you can't get anything going.order the cable and use a second rooted Android device (no drivers needed at a all)
http://forum.xda-developers.com/att...c-fastboot-t2965030/post57315448#post57315448
USB debugging was on when phone was rooted not sure if its on ss I
Cannt check it now ..
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
sguy156 said:
Ok I finally got fastboot to work . Tried this on windows 7 PC with different cable and it worked . Now what ROMS I can use to flash the zip with SON and get this phone working.. but flashing the recovery gave me this error
C:\adb>fastboot flash recovery openrecovery-twrp-2.8.1.0
target reported max download size of 1826414592 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.813s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.408s looks like verification of signature failed . Is this anything to be concerned about ..
Did these command also .................
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.013s
Phone didn't reboot into twrp recovery got stuck at htc one boot screen is it because bootloader is locked ??
Click to expand...
Click to collapse
I'm not trying to be rude but now that you have fastboot figured out I suggest you put the phone down in another room and start reading on what procedures to take next.
You learn the hard way by not looking in the "General section" where all the information is posted.
Yes you need the bootloader unlocked to push a custom recovery.
Thanks for your help , I found the other steps on other section . Hit post too quickly ..... Learning experience ..
sguy156 said:
Thanks for your help , I found the other steps on other section . Hit post too quickly .....
Click to expand...
Click to collapse
I like shortcuts when I drive ,I just don't advise taking them with the hacking of my devices.
If you use the "Tapatalk app" or the "XDA app" the forum is easier to read through
hi guys.i have have the customer servise flash tool for m86(pro5).just for m86,not work on any other phones.
and i want to share it yo you.
now just forget the customer servise.
it can falsh roms even if you lost your recovery and fastboot when your bl is locked.just like the Downloading Mode in samsung.
tools download here (Credits go to @Naphtha)
TestPCTool 1.0.0.9.rar
MultiUpgrade 4.8.5.rar
SAMSUNG USB DRIVER
How to Flash the Rom (M86).pdf (if you need some help with this just reply i will answer your question if i have time.) although my english is poor
you may need flyme roms here
[url]http://www.flymeos.com/firmwarelist?modelId=10&type=1[/URL]
enjoy it
nothing has changed
error token signature
i have this programms but they don`t worked... (Token signing fail)
P.S. please help me to flash my phone (i have fastboot mode & root, system running normally)
skype - evgen2910
My PC does not recognize my device when connected via USB , is said to have been a malfunction , I installed the RR rom and can not recognize it.
Please help:crying::crying:
Are there any tools that work for us with locked bootloaders and no recovery?
locked boot and rooted Pro 5
hexxor93 said:
Are there any tools that work for us with locked bootloaders and no recovery?
Click to expand...
Click to collapse
i have same situation
without success always i get error token sign failed WHEN USE MultiUpgrade 4.8.5.
WHO HAVE REAL SOLUTION THIS HAPPEN AFTER UNLOCK PASSWORD WITH MRT Dongle.
The same, i've a Token sign failed.
EDIT : After research, this tool is the bull**** beacause we need to are into Meizu factory. Indeed, to get the right token you need another tool, but only Meizu have it.
Sorry Guys.
EDIT 2 : https://forum.xda-developers.com/meizu-pro-5/how-to/to-unlock-hardbricked-meizu-pro-5-t3566173 Possible Way
Hi Guys, any other solution ? It reports me the same token sigh failed.
- First time when I stucked in Guest Mode (firmware 5.1.6G i thing ) I was able to fix it by this guide from KYOTOX
https://forum.xda-developers.com/meizu-mx/general/guide-meizu-mx5-stuck-guest-mode-fix-t3397191
(after boot to the desktop phone was 5-6 seconds in Admin User than phone switched to the "GUEST MODE", no more recovery mode, locked bootloader, rooted ) it was possible to solve it by that guide
- now I stucked after upgrade to 6.9.7.5 with Android 7 again (propably because I am just beginner without any experiences with flashing etc )
- Problem is before desktop appears, new flyme or Android 7 is showing me stupid commercials on 7 sheets, so during the process of reading sheet , phone switches to the GUEST, so in generally no chance.
Sorry for my english
multimedia box said:
i have same situation
without success always i get error token sign failed WHEN USE MultiUpgrade 4.8.5.
WHO HAVE REAL SOLUTION THIS HAPPEN AFTER UNLOCK PASSWORD WITH MRT Dongle.
Click to expand...
Click to collapse
bl locked rooted and no recovery.i use the flash tool but no luck.tokens failed. i follow this steps.i have the phone in bootloader mode{locked,rooted}
c/adb write
1.fastboot devices
2.fastboot oem unlock
3.close and boot again in bootloader mode.now you have unlocked bootloader
4.download recovery TWRP_3.0_m86 and put it at c/adb and write fastboot flash recovery TWRP_3.0_m86.img
5.close phone and press volume + and close button to reboot recovery.
and thats it. the phone boots twrp recovery!!
mikee72 said:
bl locked rooted and no recovery.i use the flash tool but no luck.tokens failed. i follow this steps.i have the phone in bootloader mode{locked,rooted}
c/adb write
1.fastboot devices
2.fastboot oem unlock
3.close and boot again in bootloader mode.now you have unlocked bootloader
4.download recovery TWRP_3.0_m86 and put it at c/adb and write fastboot flash recovery TWRP_3.0_m86.img
5.close phone and press volume + and close button to reboot recovery.
and thats it. the phone boots twrp recovery!!
Click to expand...
Click to collapse
With what rom previously flashed u've been able to do this ?
hey there!
i need some help here please!
i was trying to unlock my bootloader (using this guide) and it went all fine till step 17 (command "fastboot oem unlock-go"), it said i got no permission for unlocking. and now i'm stuck here. the only thing that works is fastboot mode. from there i can switch to adb using the reboot-to-edl-patch, but then i'm stuck again. device-manager shows device as usual (ports COM & LPT) and the red light is blinking, but command "adb devices" replies an empty list. tried "adb kill-server", replugging phone, rebooting computer, still the same.
so what can i do now?
thanks for helping!
Hi. You can install a fastboot rom in edl-mode with mi flash. I recomend a developer rom for this action. Then you can try the unofficial unlock from the start, but i recomend the official unlock.
Odatosz said:
Hi. You can install a fastboot rom in edl-mode with mi flash. I recomend a developer rom for this action. Then you can try the unofficial unlock from the start, but i recomend the official unlock.
Click to expand...
Click to collapse
sorry, forgot to say that miflash does not show the device after i selected the rom. i need to do something before i can flash via edl-mode. but what?
Make sure that you have the correct drivers installed on a 64bit machine, with driver signature off. And you cant get adb device list from there, so thats normal. Try to install the 7.1.8 fastboot rom that should work.
Well even m in a same situation.... as u said ur mobile is giving u red led blinks.. ..
And in device Manger ur fone is showed as Qualcomm 900E instead of 9008 and that's the reason adb couldn't list ur device
All u need to do is do a Google search - xiaomi deep flash cable
shetty_chadda said:
Well even m in a same situation.... as u said ur mobile is giving u red led blinks.. ..
And in device Manger ur fone is showed as Qualcomm 900E instead of 9008 and that's the reason adb couldn't list ur device
All u need to do is do a Google search - xiaomi deep flash cable
Click to expand...
Click to collapse
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
no1dev said:
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
Click to expand...
Click to collapse
There is no problem with miui 8. You just have to follow the steps from this post: [Tips and Tutorials] Redmi Note 3 [ SnapDragon ] - Unlock the BEAST in Seconds!!! . Just google it, because i cant post links here... Make a efs partition backup before you proceed! With a bad flash you can lose your IMEI like lots on the forum did... I would say to unlock your phone with the official unlock. Good luck!
no1dev said:
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
Click to expand...
Click to collapse
Odatosz said:
There is no problem with miui 8. You just have to follow the steps from this post: [Tips and Tutorials] Redmi Note 3 [ SnapDragon ] - Unlock the BEAST in Seconds!!! . Just google it, because i cant post links here...
Click to expand...
Click to collapse
en.miui.com/thread-253680-1-1.html
abihary said:
en.miui.com/thread-253680-1-1.html
Click to expand...
Click to collapse
There you go. Don't forget to read my edit from the other post!
Odatosz said:
There you go. Don't forget to read my edit from the other post!
Click to expand...
Click to collapse
tried that, but no success in unlocking. same reply as mentoined above (FAILED: <remote: oem unlock is not allowed>)
is there any other rom i could try to flash? not to unlock the bootloader afterwards, but to just unbrick my phone?
I would recomend to install a global developer rom for now. And unlock your bootloader with the official method.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Just install a developer ROM like you did before. Then you can decide what to do next. I would recommend to unlock your bootloader officially if you want custom ROMs on your phone.
good news: i finally managed to unbrick it!
flashing the fastboot 7.1.8 rom, and then flashing the original emmc_appsboot.mbn file via fastboot:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot reboot
during reboot holding volume-up + power and starting mi pc suite
..and suddenly it's unbricked!
so happy right now!
Glad to hear that.
no1dev said:
hey there!
i need some help here please!
i was trying to unlock my bootloader (using this guide) and it went all fine till step 17 (command "fastboot oem unlock-go"), it said i got no permission for unlocking. and now i'm stuck here. the only thing that works is fastboot mode. from there i can switch to adb using the reboot-to-edl-patch, but then i'm stuck again. device-manager shows device as usual (ports COM & LPT) and the red light is blinking, but command "adb devices" replies an empty list. tried "adb kill-server", replugging phone, rebooting computer, still the same.
so what can i do now?
thanks for helping!
Click to expand...
Click to collapse
The solution is here:
download the required files from the given link: [50mb]
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
Hello guys!
i was reading the only thread i found on a brick situation with a redmi 5 plus but i couldn't find a propper answer to my problem, here's why:
Found a realtively cheap RM5+ on internet got my hands on that phone but it won't boot tried to get back to seller but he dissapeared (eventho i have the address but it's quite far) and now i'm stuck with a phone that won't boot in anyway, here
TL;DR: bought a RM5+ online/i was scammed
This is what it does:
Boots and doesn't do anything at all, just the MI logo.
if PWR and Vol Down goes to fastboot
if PWR and VOL + says "The system has been destroyed"
if testpoint and flash it says "ACK count don't match"
i don't know if it's something with the roms i've tried but it would be great if you could point me in the right direction.
I've tested quite a lot of roms but i'm willing to download whatever you throw @ me, i'm kinda desperate.
Thanks!
maybe this helps http://en.miui.com/forum.php?mod=viewthread&tid=293457&highlight=unbrick+guide
Since you can access stock recovery, have you tried flashing an MIUI ROM using Xiaomi ADB?
https://xiaomitool.com/adb
Fran Montero said:
maybe this helps
Click to expand...
Click to collapse
sigma392 said:
Since you can access stock recovery, have you tried flashing an MIUI ROM using Xiaomi ADB?
Click to expand...
Click to collapse
Hello, thanks for your response!
I am not able to boot into recovery as it says "System has been destroyed" only fastboot and even trying with fastboot it says that partition formating is not allowed
How much did you paid for it?
I 've paid 131 Euro on aliexpress
cyds86 said:
Hello, thanks for your response!
I am not able to boot into recovery as it says "System has been destroyed" only fastboot and even trying with fastboot it says that partition formating is not allowed
Click to expand...
Click to collapse
And when it´s in mi logo it says "locked" or "unlocked"? maybe strange question but my device came unlocked out of the box and doesn´t want to boot but I can flash system and boot via fastboot mode. Some sellers try to unlock bootloader and change the firmware so not all of them got it succesfully and this unfortunately softbricks device.
Also you can try installing this tool https://androidmtk.com/download-15-seconds-adb-installer open a cmd with admin rights and type fastboot devices to check first if pc is recognicing, then you can attempt to flash most of partitions through fastboot if your device is unlocked.
If this don´t solve then you have to go for edl/download mode but try first this and report
Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.