Related
Hello,
I apologise for any mistakes as this is my first time posting here.
I recently changed the screen on my brothers OnePlus One. The installation went really smoothly and the phone displayed on startup.:good:
But for some reason now when ever it it starts up you get a 1+ logo and then it has the android man with the red triangle. It then puts you into recovery . My brother has never tried custom roms on his opo, so he has the stock recovery. I try to install some zips using the ADB sideload method but it gets about 80% done and then says that the signature verification failed even on roms downloaded from the official site. I think the phone would work if I could get TWRP installed and install the rom through there, but I can't get into fastboot mode. My brother has never been in fastboot so I don't know if you had to enable it in the OS first or something like that. If I press reboot bootloader in advance settings in the recovery it just restarts the phone back into recovery. I am not sure whether to try some type of brick fix method however it isn't hard bricked because it turns on and in soft bricked you have to use fastboot for every method that I've seen.
Any help would be brilliant.
Thanks!
Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..
fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available
jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....
I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..
I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
Hey funny you should say that. I'm actually on my second Asus 3 ultra. The same thing happened to my first one got stuck during a firmware update, or corrupted firmware zip.,now the phone won't boot to twrp or bootloader, just vibrates like yours. If I plug the charging cord in vibrates then just get those red led notification light blinks,computer won't even recognize the device so can't flash the bootloader back to the phone to fix, so I guess it's hard bricked paperweight. I only had it for about a week before the brick, had to buy a new one. The thing that's funny to me the first one would boot to twrp no problem, now this new one seems to boot to twrp but just presented a black screen, it's in twrp recovery because you can feel the vibrations for the buttons, just can't see the screen. I would love to be able to fix the bricked one it's brand new, and can't send for warranty because I'm in the US, sucks.
If you have the address for the foreign country's location of manufacturing, you can send it in for repairs. That's what we are working on doing. The horrible thing is, after reading about stories of other customers, Asus really rakes you over the coals price wise for the repair, & then does similarly for return shipping. So we are still trying to find a way around the high shipping prices, at least.
.
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
What stock keeping unit (SKU) is your phone? WW, TW, CN, or JP?
What version of TWRP did you flash?
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
i think the mistake people may be making is flashing stock rom through twrp
twrp only for supersu zip and other things imo
stock rom just flash through the stock recovery apply update from sd (microsd card) need to make sure the recovery and rom match
can you get to stock recovery? also charge it first to a good 80 to 90 if not 100 percent
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
After you get that black screen, just press once the power button to close and then press it again to open, just like you do when you normally close and open the screen. You will see after that the twrp interface.
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
read your post again...noticed...
one thing-if you were on ww-14 i.e. android nougat then cannot simply flash the ww 13 marshmallow as I believe the bootloader is different - think that is why the flash did not work (know this from other zenfone forums where you cannot simply downgrade by flashing a previous android level rom) if it was not a case of downgrading then maybe because of using twrp for stock rom instead of the update process using stock recovery
I tried to flash ww 13 when on ww 14 through stock recovery and it was giving me an error (saying version is not ww which was not the case anyway)-found out through other forums that it is because one cannot downgrade in that manner - therefore I think cause of flash error is the bootloader version. For downgrading one needs the raw file. I found raw file for our ultra (WW13 level) at a Vietnamese site and the flashing tool but have not tried it (no reason to) but am keeping it just in case.
you can get stock recovery from here (note the ww 13 or ww 14 types pick the right one)
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
flash it through fastboot
need to have fastboot drivers installed
https://developer.android.com/studio/releases/platform-tools
or
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
make sure path variable has fastboot folder in it in environment variables of computer
preferably have recovery image in that folder too so you don't have to type some long path names
power off
volume up press and hold then press power
get to bootloader fastboot mode
connect by usb
open command prompt window in folder where fastboot installed
check fastboot devices to verify phone is seen
filename.img = filename of the twrp.img
twrp flash recovery filename.img
if successful then
twrp boot filename.img
may have to press power or volume up to get to the screen
while in stock recovery better to do factory reset too before update
then apply update from sd card
btw I have successfully used the twrp march version 3.2.1 (also at the above mega link) with the latest stock ww 14 (from jan 8 2018) backed up restored successfully, rooted, and have xposed as well
a note on twrp restore if ever having to (just don't check system image restore in twrp when restoring)
trying to do miui port
Can anyone help me???My device isn't opening after twrp flashing.when I reboot I see dark screen,not twrp recovery... please somebody help me,fast.....
Same problem with my iball tablet
Even flashing stock recovery doesn't give me recovery back i have also tried philz recovery but no luck i need help too
I would like to clarify some things first.
I know I fuked up big time, I did things I didnt know how to do, flashed shlt from strange links and the like, I completely assume the responsibility, I fuked up big time and its my fault. Im a stubborn mf and decided to take care of my device without much knowledge.
I apologize beforehand if the answer to this is already somewhere, but i am so so tired im writing this thread and going to sleep, hoping to find an answer tomorrow or at least discuss with you people a solution to the situation I created.
In the span of 24 hours I completely messed up my phone. Its a honor6x, bll-l22 model. It had huawei Nougat on it which i installed months ago, working and smooth. I wanted to upgrade to Android Pie or Oreo at least, and messed it up. I would try to recall and tell you what happened first but I swear i downloaded so many files and roms i cant order it in my head.
I flashed twrp with fastboot, and from twrp i flashed one of those roms. Phone died probably because of incompatible OS. I tried fixing it with DC phonenix but to no avail, phone stil bricked.
Its on a bootloop, huawei logo keeps appearing and dissapearing again and again. When i hold vol up + power it goes to a blank rescue mode screen, please update system again, and also says failed to load recovery. vol up vol down and power doesnt take me to upgrade mode anymore (which is why i cant finish the flashing with dc phoenix, since it asks for you to put your huawei in upgrade mode to finish the firmware install) and the only accessible mode is fastboot (vol down + power) which gives me certain hope to save my device from a hard brick.
i tried flashing a stock marshmallow firmware for my phone model (the extracted .img files of recovery, boot, cust, and system) through fastboot but it says that remote command is not allowed. the only thing i can flash is recovery, so i installed the stock one to see if i get any options to wip/restore/update from sd card/anything but it all failed. i got the twrp for honor6x (berlin) and after flashing and booting directly to recovery, it fails and boots into stock recovery/fails to load recovery and shows the rescue mode i talked to you about in the beginning.
i just tried flashing stock recovery, it says flash okay and when i boot into it, it takes me to rescue mode now, doesnt even boot the stock recovery anymore.
i just checked and its in a loop between rescue mode and boot logo, one comes after the other endlessly.
ive been all day searching for a fix, ive spent 18 hours in front of the pc with breaks for taking a shlt, pissing or eating something, which for me is a lot, im not used to it. so im gonna post this here and sleep a lot and come back tomorrow, i cant stand this screen for one more seconds my eyes are burning.
thank you in advance, i appreciate any help :good:
Can you try reflashing TWRP? Or boot into TWRP? Also, what is the phone status in the bootloader screen. Does it say locked or unlocked? Assuming you can flash and boot into TWRP I would say go to wipe -> format data and then advanced wipe -> mark everything except sd card and wipe it. If not then I recommend dirty flash of your ROM you were using before boot loop i.e latest version of Android 7 for your model through hurupdater. You can find more info about it by searching for it. If the flash is successful boot into the ROM. I think your problem is mostly die to corrupt partitions and hurupdater should fix that. Also download the firmware files from Firmware Finder and rename them accordingly. If you are able to boot into the ROM, then reflashing TWRP and then wipe everything again (except SD Card) and then reflashing the same ROM using hurupdater again. This will remove the dirty flash.
Another alternative u could try is HWOTA 7. It will also upgrade you to Android 8 if you provide the correct files. Just search HWOTA 7 for Honor 6x. And follow the steps. Hope this helps your case
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page14
Here is the HWOTA 7 thread. If hurupdater fails try this
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Here is the link to hurupdater. It works on Honor 6x. Couldn't find the particular thread. Download the Hurupdater zip and official firmware from Firmware Finder and follow the instructions.
Mannan Qamar said:
Can you try reflashing TWRP? Or boot into TWRP? Also, what is the phone status in the bootloader screen. Does it say locked or unlocked? Assuming you can flash and boot into TWRP I would say go to wipe -> format data and then advanced wipe -> mark everything except sd card and wipe it. If not then I recommend dirty flash of your ROM you were using before boot loop i.e latest version of Android 7 for your model through hurupdater. You can find more info about it by searching for it. If the flash is successful boot into the ROM. I think your problem is mostly die to corrupt partitions and hurupdater should fix that. Also download the firmware files from Firmware Finder and rename them accordingly. If you are able to boot into the ROM, then reflashing TWRP and then wipe everything again (except SD Card) and then reflashing the same ROM using hurupdater again. This will remove the dirty flash.
Another alternative u could try is HWOTA 7. It will also upgrade you to Android 8 if you provide the correct files. Just search HWOTA 7 for Honor 6x. And follow the steps. Hope this helps your case
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page14
Here is the HWOTA 7 thread. If hurupdater fails try this
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Here is the link to hurupdater. It works on Honor 6x. Couldn't find the particular thread. Download the Hurupdater zip and official firmware from Firmware Finder and follow the instructions.
Click to expand...
Click to collapse
Hey man! Thanks for your long answer, just got up with a fresh head and stronger hopes so I will keep trying it all. I couldnt boot into twrp dik why. I flash it succesfully with fastboot but after that it boots me into recovery/fails and blank rescue mode screen. I by some miracle button combination achieved to boot straight into twrp right after flashing, so I will try that.
Bootloader is unlocked (phone unlocked) and FRP says "unlock". idk if that is a statement or a command to do it actually haha.
As soon as I boot into twrp, ill wipe it all and follow your instructions
Ill try to use twrp first, then hurupdater and then hwota7.
What do you mean by renaming the firmware accordingly? How can I do that? Isnt that iirelevant since inside the firmware files it still says some things that do not match the title i renamed?
oh, forgot something. fastboot commands are limited. i can flash a recovery.img but not a boot.img or use certain commands. remote command not allowed.
inkainsa said:
Hey man! Thanks for your long answer, just got up with a fresh head and stronger hopes so I will keep trying it all. I couldnt boot into twrp dik why. I flash it succesfully with fastboot but after that it boots me into recovery/fails and blank rescue mode screen. I by some miracle button combination achieved to boot straight into twrp right after flashing, so I will try that.
Bootloader is unlocked (phone unlocked) and FRP says "unlock". idk if that is a statement or a command to do it actually haha.
As soon as I boot into twrp, ill wipe it all and follow your instructions
Ill try to use twrp first, then hurupdater and then hwota7.
What do you mean by renaming the firmware accordingly? How can I do that? Isnt that iirelevant since inside the firmware files it still says some things that do not match the title i renamed?
oh, forgot something. fastboot commands are limited. i can flash a recovery.img but not a boot.img or use certain commands. remote command not allowed.
Click to expand...
Click to collapse
Renaming them means that when you download them from Firmware Finder they will be named different. You just rename them normally. The linked threads will provide you detailed info. Just rename them accordingly and you are good to go. Good Luck.
BTW don't be so hard on yourself. We all make mistakes. Just because you flashed something incompatible doesn't mean you deserve hate. You are a noob. The first time I bricked my phone was when I flashed a zip that was supposed to redesign the settings menu of Android 7 to resemble Android 8. LoL. So don't be hard on yourself. If the phone boots it can be saved.
The combination is power and volume +. Also don't try everything. If the wipes are successful, then just flash hurupdater and you are good to go. If they are unsuccessful then format data first and try again. Format data option is in the same menu
Mannan Qamar said:
Renaming them means that when you download them from Firmware Finder they will be named different. You just rename them normally. The linked threads will provide you detailed info. Just rename them accordingly and you are good to go. Good Luck.
BTW don't be so hard on yourself. We all make mistakes. Just because you flashed something incompatible doesn't mean you deserve hate. You are a noob. The first time I bricked my phone was when I flashed a zip that was supposed to redesign the settings menu of Android 7 to resemble Android 8. LoL. So don't be hard on yourself. If the phone boots it can be saved.
The combination is power and volume +. Also don't try everything. If the wipes are successful, then just flash hurupdater and you are good to go. If they are unsuccessful then format data first and try again. Format data option is in the same menu
Click to expand...
Click to collapse
Haha of course i dont deserve hate, but i was really stubborn, thats it.
Yeah, cant boot into any recovery at all, so hurupdate is impossible.
Also, Im getting lost on all the hwota threads, unfamiliar concepts and stuff i miss so i will posibly do something wrong.
Could you reply with noob-friendly steps on how to install oreo on my device? And if thats not possible ill be satisfied with nougat or even marshmallow, as long as phone works :/. Of course i prefer oreo if possible.
No recovery, when i flash one (stock or twrp) through fastboot, it flashes succesfully but phone doesnt boot into it (yes with vol+ and power), it just goes straight to rescue mode blank screen. Upgrade mode is failing too. Only fastboot works.
inkainsa said:
Haha of course i dont deserve hate, but i was really stubborn, thats it.
Yeah, cant boot into any recovery at all, so hurupdate is impossible.
Also, Im getting lost on all the hwota threads, unfamiliar concepts and stuff i miss so i will posibly do something wrong.
Could you reply with noob-friendly steps on how to install oreo on my device? And if thats not possible ill be satisfied with nougat or even marshmallow, as long as phone works :/. Of course i prefer oreo if possible.
No recovery, when i flash one (stock or twrp) through fastboot, it flashes succesfully but phone doesnt boot into it (yes with vol+ and power), it just goes straight to rescue mode blank screen. Upgrade mode is failing too. Only fastboot works.
Click to expand...
Click to collapse
So you can't enter TWRP? I would recommend that later you flash TWRP through fastboot instead of rebooting press and hold volume up & power button on the bootloader screen. If that doesn't work try flashing TWRP with the following command:
"Fastboot flash recovery_ramdisk (nameofrecovery.img)" . Also HWOTA 7 requires TWRP to be functional. If by any chance you can enter TWRP then make the wipes. Don't wait for anything. Have the Hurupdater files in a SD card along with the firmware.
See myself in the story too LOL. Still can not remember how I got out.....
Try to flash twrp
then run: adb reboot recovery
To fash recovery run:
in Nougat: fastboot flash recovery xxxtwrp.img
in Oreo: fastboot flash recovery_ramdisk xxx.twrp.img
Maybe run both and see what u get.
my phone is hard bricked. it wont even boot to fastboot ot bootloader. three button not working. any help. it just keeps diplaying your phone is now booting. i dont even get three options. please any help would be appreciated
Eww bud is the battery dead? Maybe try to reflash your recoveries
mightyblazer said:
Eww bud is the battery dead? Maybe try to reflash your recoveries
Click to expand...
Click to collapse
even after tye batteries died i am unable to boot into fastboot........
Oh ya hmm not sure about that sorry
Mannan Qamar said:
my phone is hard bricked. it wont even boot to fastboot ot bootloader. three button not working. any help. it just keeps diplaying your phone is now booting. i dont even get three options. please any help would be appreciated
Click to expand...
Click to collapse
Same thing happened to me... any progress?
mangesh2000 said:
Same thing happened to me... any progress?
Click to expand...
Click to collapse
Fixed a few months ago,used it for a while and then sold it.
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
divvykev said:
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
Click to expand...
Click to collapse
Likely the phone was encrypted
divvykev said:
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Click to expand...
Click to collapse
For me this happened a few times, including when I tried to 'fastboot boot' a wrong image or some latest bluespask Twrps. This is the state when the the phone has hung trying to execute something. The remedy is to hold the power button pressed for something like 10 seconds and the phone will switch off (this is a hardware feature so shlould not fail). After that I go to fastboot normally - press volUp+Power for a few seconds till the fastboot message. Also, make sure that you are not charging, as this seems to have prevented me going to fastboot once.