Hard brick - Honor View 10 Questions & Answers

Hello everyone ...
I flashed the stock kernel(i had a custom kernel), system and vendor to return to the stock version I am confronted with a complicated brick.
Currently my phone cannot boot, it goes directly to erecovery. In fact its strange, when it is off I first have the honor logo of the beginning, finally it turn off 3 seconds, then again the logo honor and at the second attempt it shows the screen "your device is unlocked ect ..." and finally Erecovery .
Cherry on the cake FRP is lock, so it is impossible to flash anything ... i tried that -> fastboot oem frp-unlock "bootloader code" and FAILED (remote: password matching failed!!). (The password is good lol)
If someone has an idea to save my beloved View 10 ?
I tried already tried that : https://forum.xda-developers.com/8-lite/how-to/guide-unbrick-huawei-p8-lite-2017-honor-t3766652 (and didnt worked for me )

Rommco05 said:
If is FRP locked u cant do anything... I dont like to say this but Funky Huawei can help
edit: or DC Phoenix is much cheaper
Click to expand...
Click to collapse
I just bought DC-phoenix, all the files of the update.app flash well one after the other but that does not solve the problem :/
Now the animation of the boot is launched but suddenly the phone off and reboot erecovery...
Anyone know what happen ?

Rommco05 said:
Contact support of DC Phoenix
Click to expand...
Click to collapse
In the end I managed to boot my smartphone normally but other problem, to get there I was forced to clean all the internal memory and re-flash all the files with dc-phoenix but now many things do not do not work in the rom. For example the starter animation is the basic "just android", can not record fingerprints ect ... I also lost the support treble so impossible to install other roms.
Any ideas guys ?

Rommco05 said:
Have you unlocled bootloader and FRP? If yes can u flash twrp?
Click to expand...
Click to collapse
Yes, twrp is installed and the bootloader as well as frp are unlocked. after a few hours I recovered the support treble (the custom roms work again) and now in the settings I have "Honor View 10 and C432 B141" and no longer "Kirin 970 Device and Unknow system".
All the main features came back except the fingerprint sensor and the boot animation which is still black with just written "Android"
Honestly i dont care about the boot animation but any ideas to recovering the fingerprint support ?
Édit : I can register a fingerprint but when the "fingerprint setup" tell me to put my finger on the sensor to set up the unlock screen, but when I put my finger on the sensor the settings app closes and impossible to finalize the fingerprint registration.
Factory reset do not work :/ when it gets to 99% I have an error and the phone reboot in secure mode

Rommco05 said:
Use this tool
[Tool] [HuRUpdater] [0.3] [Flash official firmware in recovery
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
It worked! Everything works perfectly now :victory:
I downloaded the files of the version B130 and it is the last version (B141) which was installed lol
but everything works perfectly! Thank you for your help, it is very appreciated

Related

How can i root (unlock Bootloader) my Mate 9 without letting Huawei know?

Because i rooted all my phones so far, i also want to root my new Huawei Mate 9 to get all advantages and full access.
But how can i unlock my bootloader without requesting an unlock-code from Huawei and being on a black-list?
Is there a way to get rid of this?
Do one of these three solutions wok for Mate 9?
https://translate.google.com/transl...k-fuer-alle-huawei-phones/&edit-text=&act=url
http://actualizatumovil.com/Temas-Bootloader-unlock-without-emailing-Huawei
https://forum.xda-developers.com/showthread.php?t=2290610
Thank you for your answers in advance,
Florian
--- EDIT ---
Solved!
My tutorial for unlocking, installing TWRP and rooting Huawei Mate 9 at Post #13
Use dc-unlocker, but you have to pay, usually around 4-6 USD.
https://www.dc-unlocker.com/supported_models_1/huawei_phones
Hi azukayx,
thank you for your answer!
azukayx said:
Use dc-unlocker, but you have to pay, usually around 4-6 USD.
https://www.dc-unlocker.com/supported_models_1/huawei_phones
Click to expand...
Click to collapse
This method is working securly?
My Build-Number is "MHA-L09C432..." but here it says only MHA-L09B, it could work still?
And only read bootloader code is available: is that the code i am normally getting from Huawei? Or what is that?
Thank you for your answer in advance,
Florian
htcdesire-hd said:
Hi azukayx,
This method is working securly?
My Build-Number is "MHA-L09C432..." but here it says only MHA-L09B, it could work still?
And only read bootloader code is available: is that the code i am normally getting from Huawei? Or what is that?
Florian
Click to expand...
Click to collapse
Not sure, you can always shoot them an email asking or use their chat when they are online. There may be other unlocking services floating around, you may have to google them.
Need help to relock bootloader stock mate 9 usa
I have the mate 9 USA version bought it with unlocked bootloader and some programs are missing like the software update setting is gone, file manager etc. Please I need help going back to stock and relocking bootloader. :
azukayx said:
Not sure, you can always shoot them an email asking or use their chat when they are online. There may be other unlocking services floating around, you may have to google them.
Click to expand...
Click to collapse
Thank you i will try this and contact the support before...
Is there also a unlocking method without Huawei?
azukayx said:
Use dc-unlocker, but you have to pay, usually around 4-6 USD.
https://www.dc-unlocker.com/supported_models_1/huawei_phones
Click to expand...
Click to collapse
Thats the service i used to unlock my phone.
htcdesire-hd said:
Hi azukayx,
thank you for your answer!
This method is working securly?
My Build-Number is "MHA-L09C432..." but here it says only MHA-L09B, it could work still?
And only read bootloader code is available: is that the code i am normally getting from Huawei? Or what is that?
Thank you for your answer in advance,
Florian
Click to expand...
Click to collapse
Read bootloadercode is fine, save it in a textfile and use fastboot oem unlock xxxx (where xxxx is your bootloader unlock code) be sure usb debugging and oem unlock are activated before using fastboot
After downloading the DC Android app and investing about 4€, the bootloader could be unlocled without problems and without Huawei!
But resetting phone (after Bootloader unlocking) failed and EMUI is not loading any more...
I try to flash the original firmware and hope to solve this problem with that... Downloading EMUI via eRecovery also failed because of verification problems...
htcdesire-hd said:
But resetting phone (after Bootloader unlocking) failed and EMUI is not loading any more...
I try to flash the original firmware and hope to solve this problem with that... Downloading EMUI via eRecovery also failed because of verification problems...
Click to expand...
Click to collapse
If you're still stuck try Funkyhuawey.
htcdesire-hd said:
After downloading the DC Android app and investing about 4€, the bootloader could be unlocled without problems and without Huawei!
But resetting phone (after Bootloader unlocking) failed and EMUI is not loading any more...
I try to flash the original firmware and hope to solve this problem with that... Downloading EMUI via eRecovery also failed because of verification problems...
Click to expand...
Click to collapse
Try to do factory reset again from stock recovery,and wipe cache.
Hold volume up + power till you see the logo and release power while keeping volume up.
By the way i hate dc unlocker,more problems than fixing lol
gm007 said:
Try to do factory reset again from stock recovery,and wipe cache.
Hold volume up + power till you see the logo and release power while keeping volume up.
By the way i hate dc unlocker,more problems than fixing lol
Click to expand...
Click to collapse
I solved the Problem!
I only had to re-lock and then unlock my bootloader again via fastboot and it's working now!
But there are other problems:
When i activate developer options and try to open it, the settings are always crashing...
The same happens when i try to make a factory reset within the storage settings...
When i connect my phone to a PC while in TWRP, there are only some folders with cryptic numbers and i am not able to copy files to my phone (like superuser)...
What can cause this strange behavior?
And why is there no HiCare App and no update menu available? How can that be reactivated?
Problems solved using FunkyHuawei!
Now everything seems to work correctly (except of backing up via TWRP)...
For others who have the same problems with rooting their Huawei Mate 9, here is a little Tutorial:
How to unlock the bootloader without Huawei
download and install "DC Huawei Bootloader Codes" (from dc-unlocker) from playstore
open the app and klick on "DC-unlocker account"
pay the about 4€ via playstore (username and password is sent via email to the given address)
download and run the DC-Unlocker client (from dc-unlocker.com)
follow instructions from website (https://www.dc-unlocker.com/huawei-id-unlock)
unlock-code should be shown after following all instructions
shutdown phone
hold volume-down-key and connect the phone via USB to a PC (release key when bootloader appears)
run fastboot-command "fastboot oem unlock xxxxxxxxxxx" (x = your unlock code)
confirm message on screen
system performs factory reset
bootloader should now be unlocked! (can be seen in bootloader)
if something not working try to lock ("fastboot oem relock xxxxxxxxxxx") and unlock the bootloader again
or do a factory reset and wipe cache via recovery
if nothing solves the problem buy a FunkyHuawei account (15$/month) and make a clean re-installation of the firmware like discribed there (https://funkyhuawei.club/instructions)
How to install TWRP recovery
shutdown phone
hold volume-down-key and connect the phone via USB to a PC (release key when bootloader appears)
flash recovery via fastboot (recovery should be in same folder as fastboot.exe) ("fastboot flash recovery twrp-xxx.img") (x = downloaded version)
type "fastboot reboot"
leave the USB cable connected to PC
when phone booted hold volume-up, volume-down and power key
release power key after vibration
release volume keys after Huawei-logo disappears
TWRP should start!
How to root phone
requirements: unlocked bootloader and TWRP recovery t3.0.2-2-hi3660 (from this thread: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
copy superuser-r275.zip to phone storage (download link also available in the thread mentioned above)
boot into TWRP recovery (connect the USB cable to PC -> hold volume-up, volume-down and power key -> release power key after vibration -> release volume keys after Huawei-logo disappears)
choose "install" and select the previous copied .zip-file
after installation reboot phone
install Superuser_2.0_Beta_9.apk (from here: https://forum.xda-developers.com/showpost.php?p=69224582&postcount=1896)
download "Root Checker" from play store
Root Checker should show root access!
Please cosider that i am not responsible for any damage on the device after using this tutorial
htcdesire-hd said:
Problems solved using FunkyHuawei!
Now everything seems to work correctly (except of backing up via TWRP)...
Click to expand...
Click to collapse
Is this method possible without involving FunkyHuawei?
Are there any problems with losing functionality after this is complete? Heard reports of the software update setting going away, file manager missing, themes not working, etc.
xfive420 said:
Is this method possible without involving FunkyHuawei?
Are there any problems with losing functionality after this is complete? Heard reports of the software update setting going away, file manager missing, themes not working, etc.
Click to expand...
Click to collapse
I don't think so, because i had to re-flash the whole firmware to cure the errors and i think, until now, there is no other method to flash a firmware without using the Huawei eRecovery (modified with FunkyHuawei)...
No, after the clean setup with FunkyHuawei everything works fine for me, without any errors! It works like before, allthough the Bootloader is unlocked and the phone is rooted

Camera Not Functioning after re-locking Bootloader

Hi guys,
I'm new here so please be patient with me. Hands were itchy few days ago, hence, I went and unlock bootloader on my phone, it unlocked without any problems and is successful, but, when I started to flash new ROM in it, it crashed and soft bricked my phone. Always show 'No OS installed' on TWRP.
I was left with no choice but to software repair it with Xperia Companion but have to relock the bootloader to do so. Xperia Companion fixed my phone up, with Andriod 7.1.1 and it works again! but whenever I press the camera button this comes up 'Error: This camera may be in use by another application. Please close the other application and try again' ...
I've tried multiple ways to do so:
1) Unlocking the boot loader again - When being switch on, it request for Andriod Password in order to unlock the phone. Which I have never set any password at boot up before.
2) Trying to flash it into TWRP to recovery mode - Whenever I do so, it goes back to 'No OS installed'
3) Trying to flash different compatible ROM - Which reverts back to "NO OS installed"
4) Re-lock boot loader - Phone works fine, everything is OK except for the Camera issue.
If anyone could help me in my situation, I would just like to get this Camera function working again. I dont mind flashing other ROM in it or whatsoever.
Please help! :crying:
YCraftedJelly said:
Hi guys,
I'm new here so please be patient with me. Hands were itchy few days ago, hence, I went and unlock bootloader on my phone, it unlocked without any problems and is successful, but, when I started to flash new ROM in it, it crashed and soft bricked my phone. Always show 'No OS installed' on TWRP.
I was left with no choice but to software repair it with Xperia Companion but have to relock the bootloader to do so. Xperia Companion fixed my phone up, with Andriod 7.1.1 and it works again! but whenever I press the camera button this comes up 'Error: This camera may be in use by another application. Please close the other application and try again' ...
I've tried multiple ways to do so:
1) Unlocking the boot loader again - When being switch on, it request for Andriod Password in order to unlock the phone. Which I have never set any password at boot up before.
2) Trying to flash it into TWRP to recovery mode - Whenever I do so, it goes back to 'No OS installed'
3) Trying to flash different compatible ROM - Which reverts back to "NO OS installed"
4) Re-lock boot loader - Phone works fine, everything is OK except for the Camera issue.
If anyone could help me in my situation, I would just like to get this Camera function working again. I dont mind flashing other ROM in it or whatsoever.
Please help! :crying:
Click to expand...
Click to collapse
Flash a custom Kernel (e.g AndroPlus) and you'll be OK.
clickbtr said:
Flash a custom Kernel (e.g AndroPlus) and you'll be OK.
Click to expand...
Click to collapse
Just tried it, with custom kernal (Andro Plus), followed everything as instructed. Phone soft bricked again... =/
YCraftedJelly said:
Just tried it, with custom kernal (Andro Plus), followed everything as instructed. Phone soft bricked again... =/
Click to expand...
Click to collapse
Remember to unlock your bootloader, when it ask for Android Pass, simply just enter mutiple time any pass (30, not sure,), if your phone reboot after 10 times, wait for it to reboot and enter wrong pass again. After that, your phone will boot up, now you need to flash custom kernel to use camera.
clickbtr said:
Remember to unlock your bootloader, when it ask for Android Pass, simply just enter mutiple time any pass (30, not sure,), if your phone reboot after 10 times, wait for it to reboot and enter wrong pass again. After that, your phone will boot up, now you need to flash custom kernel to use camera.
Click to expand...
Click to collapse
Great! it worked! IDK what happen, but I just unlock the bootloader, restarted, no Android password was asked... but yeah! camera is working now! Thank you so much! =D
YCraftedJelly said:
Great! it worked! IDK what happen, but I just unlock the bootloader, restarted, no Android password was asked... but yeah! camera is working now! Thank you so much! =D
Click to expand...
Click to collapse
Congratulations :laugh:

[Solved] Possibly bricked, eRecovery not working

I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
use another Android phone download huaweifirmware finder on the google play ,select mha-l29c567,than select dns update,change your router dns,you can do erecovery after setup dns!
sweetjuice said:
use another Android phone download huaweifirmware finder on the google play ,select mha-l29c567,than select dns update,change your router dns,you can do erecovery after setup dns!
Click to expand...
Click to collapse
Thank you for your response. However, I tried it and it didn't work for me. I downloaded the app, checked the firmware was available, registered the update, changed my router DNS, and then attempted the eRecovery. It downloaded the package then installed it, but the same problem continues.
audioralf said:
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
you can install a full firmware with hwota method.
audioralf said:
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
Is this the information you're asking for?
Huawei Mate 9
Version: MHA-L29C567B910
I don't know how to get any other information (other than the IMEI and SN which are on the box), since I can't make it past the boot logo screen.
mavera said:
you can install a full firmware with hwota method.
Click to expand...
Click to collapse
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
cr33p3r1n1134 said:
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
mavera said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
Click to expand...
Click to collapse
Rebranding is not really necessary.
@OP
For MHA-L29C567B190 (you wrote B910 which I assume is incorrect), use:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v84935/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...35/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/.../v84935/f2/full/hw/usa/update_full_hw_usa.zip
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
cr33p3r1n1134 said:
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
Click to expand...
Click to collapse
Unlocking bootloader does a factory reset so that might be why it's working again
cr33p3r1n1134 said:
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Click to expand...
Click to collapse
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
ji_mestone said:
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
Click to expand...
Click to collapse
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
cr33p3r1n1134 said:
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
Click to expand...
Click to collapse
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
ji_mestone said:
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Yeah, the ADB sideload problem also happened to me. Eventually gave up on that.
I hope I'm allow to post links.
But here is a link to something I remember using.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Using those tools mentioned in that post helped me out. I had to do a lot of experimenting with that as well. Every time I connected and disconnected my phone from my computer, I checked which were the references that needed deleting, then deleted them. It was tedious, but I'm not expert, so maybe I took the long way.
Maybe try using those tools?

SM-G930F reboots no Recovery possible

I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Huzalio said:
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Click to expand...
Click to collapse
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cache, factory reset, then reboot device.
cooltt said:
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cach, factory rest, reboot device.
Click to expand...
Click to collapse
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Huzalio said:
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Click to expand...
Click to collapse
Mate keep trying you have to be really quick when it goes off to quickly press volume up
cooltt said:
Mate keep trying you have to be really quick when it goes off to quickly press volume up
Click to expand...
Click to collapse
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Huzalio said:
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Click to expand...
Click to collapse
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
cooltt said:
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
Click to expand...
Click to collapse
Yeah did exactly that switched to the combo before it showed anything no succes.
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
Not sure what's wrong with it then
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Ulf3000 said:
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Click to expand...
Click to collapse
able to confirm to enter download modus
Huzalio said:
able to confirm to enter download modus
Click to expand...
Click to collapse
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
cooltt said:
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
Click to expand...
Click to collapse
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Huzalio said:
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Click to expand...
Click to collapse
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
cooltt said:
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
Click to expand...
Click to collapse
Okay i see.
Do you somehow have a good tutorial?
Huzalio said:
Okay i see.
Do you somehow have a good tutorial?
Click to expand...
Click to collapse
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Ulf3000 said:
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Click to expand...
Click to collapse
sadly no succes :/
Huzalio said:
sadly no succes :/
Click to expand...
Click to collapse
I think it's obvious you don't know what your doing, no offence. Everything that's been suggested should work with no problems. You are better off taking it to a Samsung centre to fix it. I doubt anyone will be able to help you here.
unbricking with the factory binary
This method is not for the faint of heart; it involves downloading 1) the factory binary for your phone, and 2) the correct firmware for your phone (which you can find at sammobile). I don't know if it will fix your particular problem but if everything else has failed, it's worth a try. You will basically be taking your phone back to its state when it was first set up at Samsung factory, before the firmware for your region was installed. I used this to get past a drk imei error, it's worth taking a look. Anyone else who knows more than me, please weigh in on what you think about it.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516

What could happen if smartphone reboots while downgrading?

Good afternoon
i would like to downgrade my honor view 10 emui 10.0 to emui 8 so i can unlock the bootloader via hcu client, but it often reboots for no reason +-4 times a day
i wonder if it reboots during the downgrade or a hard reset do i risk to brik it?
i dont know if it's a software issue or hardware, but few times it even rebooted while actually rebooting, after the logo appeared it hust shut down again and boots up
reebots are not caused by phone shaking, some time i wake up and see that smartphone rebooted during the night. (it ask for pin after every reebot)
thanks
Nothing good if you're flashing it.. it will corrupt the image.
Is the battery ok? Replace it if not.
Try a factory reset and see if that restores the stability.
thanks for your time blackhawk
i dont know if it's a battery issue
i bought this smartphone 3 years ago, and i can still make a full day with a single charge
i'll try with the hard reset first to see if something change
blackhawk said:
Nothing good if you're flashing it.. it will corrupt the image.
Is the battery ok? Replace it if not.
Try a factory reset and see if that restores the stability.
Click to expand...
Click to collapse
_MOE_ said:
thanks for your time blackhawk
i dont know if it's a battery issue
i bought this smartphone 3 years ago, and i can still make a full day with a single charge
i'll try with the hard reset first to see if something change
Click to expand...
Click to collapse
You're welcome.
Replace the battery first then go from there.
battery replaced
no diffrence
Found dozens of users online with the same issue,
anyway tried a downgrade via hisuite proxy and bricked the phone
can access fastboot and erecovery
from fastboot
tried flashing stock rom = archive does not contain 'android-info.txt'
tried extracting partition from stock rom and flashing it = FAILED (remote: Command not allowed)
same errors with 3 diffrent stock roms
bootloader is locked
hisuite recovery option not successful same for hisuite proxy (tried with diffrent versions of hisuite)
erecovery recovery failed
Info about my device
Device Factory : Huawei
Device Model : BKL-L09
Device Firmware : BKL-L099.1.0.364(C432E5R1P13)
Bootloader Status : Locked
OEM Status : Locked
Phone Status : Locked
Bootloader Version : Ver2.3
Vendor Country : vendorcountryhw/eu

Categories

Resources