Database Info

Recovery bootloop. No USB debugging. No Recovery.

So long story short, tried installing unofficial CWM recovery, and phone bootlooped. It just boots up, says it's booting to recovery, and restarts. Boots to recovery restarts. I can boot into download mode, but I don't think USB debugging is enabled because I can't see my device on adb. I think my only option might be fastboot, but I don't know how to set it up or use commands to reinstall philz custom recovery. I had that before I tried the unofficial CWM. Anyone have an idea on how I can get myself out of this one? Any help will be very much appreciated!

Use Odin to flash a recovery. Should bring it back to life
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15

metalfan78 said:
Use Odin to flash a recovery. Should bring it back to life
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15
Click to expand...
Click to collapse
I'm on Antergos right now, so I can't use Odin. My phone tries to boot to recovery mode when I just hold the power button down, fails, then keeps trying to reboot to recovery.

Dont know if this was somved or not, but it sounds like your recovery didnt take, thats why it keeps trying boot into recovery and failing. Its missing. Either restore a backup, find a way to flash a recovery since you cant use odin, or find a way to flash back to complete stock package which will include a recovery.

I just took the phone to sprint and got a new one free of charge.

Bricked my phone need help please!

Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg

balpem said:
Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg
Click to expand...
Click to collapse
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?

jfer671 said:
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?
Click to expand...
Click to collapse
No because I had twrp recovery installed and tried to flash cwm over it. After that I had no recovery at all. But I made some progress now... I am able to flash the same newest twrp 2.8.7.0 recovery to the phone and I managed also to flash the 5.1 stock recovery. I flashed BOOT.img from 5.1 and SYSTEM.img from 5.1 and I got rid of the error in fastboot menu.
Stock recovery I can flash via installer_r24.4.1-windows from acbka.
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
And these two recoveries seems to be the only one that work on my phone....? Currently I have stock recovery installed and i put MT7-L09C900B324 on my sd card (dload/UPDATE.app) and did the three buttons rescue. It seemed to work but It stoped at 90% and still no luck. What am I doing wrong this time?
Hi Suite does not recognitze the phone. When I abort the istallation and reboot the phone starts with the Huawei Logo and goes black and starts to the Huawei logo and goes black and so on...
Here is a picture of where i am stuck at 90% right now, so close...:
hxxp://s13.postimg.org/p093toz5z/IMG_0192.jpg

SOLVED
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:

balpem said:
...the trick was to flash the stock recovery for all Lollipop versions
Click to expand...
Click to collapse
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover

jfer671 said:
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover
Click to expand...
Click to collapse
I flashed via fastboot the stock recovery which you can download via the link above. the provider (user rowihel2012) claims, that this recovery works for all lolipop stock roms.
After that I made a reboot and pressed (power button and volume+) to check if its installed.
Than I downloaded the lollipop version I have had previously installed. In my case this was the B324 European version.
I put it on my sd card (dload/UPDATE.app) and launched the phone with the three button rescue method. The recovery recognized the rom on the sdcard and started to flash the OS.
After less than 5 min, my phone was restored.
I have made the experience, when using certain roms (B324, B308 etc..) with certain stock recoveries, I was not able to flash the OS and the recovery stoped always at 90%.
The recovery linked above seems to work great for the B324 version, I haven't tried any other stock roms with it.

I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).

jfer671 said:
I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).
Click to expand...
Click to collapse
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?

balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
balpem said:
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?
Click to expand...
Click to collapse
I see, so then it seems like some recoveries did in fact work with fastboot on me, because the Vol+ and Power worked, but it either only put me in V100R001C900B300 OR MT7-L09C900B300. I've read that I can't just flash KK over LP, that I needed to flash the B300 which is why I flashed transition package first. Should I not have done this?
Once in transition mode though (I booted up and checked, then went back into recovery), if I flashed 4.4 (recovery), it oddly put me back to B327...strange even though the recovery flashed was B137 or B145.
Let me see this link above. I'm back again at 5.1.1 LP B327. I'll do instead fastboot and flash above the recovery and so on, and I'll post the results, if any. Oddly enough, if I flashed boot, recovery and system images of 4.4, I get an "Android" boot screen that hangs, no Huawei.
I really like LP because of some of the features not found in KK like the dual windows, camera tweaks, etc. But no root yet available. TWRP doesn't seem to work as well, fails in fastboot.

balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
Okay...so I was able to flash down to B324, but not via the link provided. What I did was, flash B300 cust.img on (fastboot) then flash boot/recovery/cust/system.img (fastboot). Rebooted with VolumeUp + Power to check for recovery (success), performed a wipe and done! Back to B324.
Now I gotta figure how to go back down to B145, which is where I was at with Root and with no problems at all. If I flash B300 again and then B145...I get the "Android" logo (instead of Huawei) and then the HAM7 reboots and recovers itself back to B324.

Deleted OS from OnePlus One

So I was trying to perform a simple factory reset in recover mode on my OnePlus One and accidentally erased the OS. I know I could simply download a ROM onto my SD card and install though recovery only my volume buttons don't work so I'm unable to boot into recovery that way. And when I tried to boot into recovery from my PC I get a "device not found error" I'm assuming because USB debugging is not enabled. PLEASE HELP!!!! Is there any other way to boot into recovery and/or install a ROM?

Try this tool: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
May or may not work for you, it worked for me a while back.

Twrp or cm recovery? If twrp use otg pen drive with downloaded ROM and install via twrp.

drmuruga said:
Twrp or cm recovery? If twrp use otg pen drive with downloaded ROM and install via twrp.
Click to expand...
Click to collapse
Might be a redundant question but will this "pen drive" boot the phone into recovery or will I still have to figure out his to get it into recovery

GamerJesus said:
Try this tool: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
May or may not work for you, it worked for me a while back.
Click to expand...
Click to collapse
In the instruct ructions it says to hold the volume up button along with the power button (which I can't do) is it okay to skip that step?

MrSquareBidness74 said:
Might be a redundant question but will this "pen drive" boot the phone into recovery or will I still have to figure out his to get it into recovery
Click to expand...
Click to collapse
Ha ha ha ,i know. If there is no os , when you switch on phone it will enter recovery only , he said volume buttons not working , but if power button eork , when he switch on phone it will enter recovery i think . If so he will do as i told..
---------- Post added at 12:17 PM ---------- Previous post was at 11:54 AM ----------
Pc identify only fastbootmode or adb on switch on position. If there is no os r, phone in recovery mode pc won't recognise . Are you in recovery or phone is not booting ?

When I boot the phone up it gets to the OnePlus screen and stays there

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !
I recently rooted my Motorola Moto G3 and it worked.... ish, when I opened my phone from it being turned off I was greeted with the message telling me that it was super duper dangerous to root your phone and I could damage my phone, that normally goes as it is just a mandatory thing that they have to say, I waited for a while and it didn't go, I waited for a day and it didn't go. So I let it run out of charge and tried to boot it again, this didn't work, I was still seeing the same white screen with red and black writing. I then let it run out of charge and open it in fast boot mode by pressing the power button and volume down, this did work and from there I have managed to open the team win recovery project but whenever I do anything from then, it will go back to the error page and then will never load. I have even reset the phone to factory settings. If I hold the power button it will turn off the phone but very shortly after automatically turn itself back on to this same image.... please help!

How did you end up rooting it? Have you tried flashing a factory image?

If I were you, I would try to reflash stock firmware with factory reset

@Artyb52
hi, what did you do to Root ??
check these , if you have done evrything :
1) USB debugging enabled, allow OEM unlocking Enable ( developer options )
2) install ADB and fastboot. ( in PC)
3) Unlock bootloader in Fastboot mode .. (After unlocking did you PowerOn your phone, and check ? did it ON with out any problems? )
4) Installing a recovery , by following proper commands and choosing right version ..
5) flashing SuperSU with that Recovery.
If you have done everything Right, then Do onething.. Change CustomRecovery Version ( if on TWRP ) ,
else Goto Fastboot.. press POWER OFF, so that your phone gets SHUT DOWN, then On it normally ..
i have seen a problem where REBOOT function causes Bootloops..

i tried that and it didnt work :/
@nandakis4 shame it didn't work. Do you have any other tips, I would be really grateful

@Acetyloaceton how do you do that ? sorry for sounding like such a noob, i'm new to the game

l3ones said:
How did you end up rooting it? Have you tried flashing a factory image?
Click to expand...
Click to collapse
@13ones I tried flashing the TWRP image, is that different to the factory image ?

The same thing happened me when I rooted my phone. To fix it I downloaded cm 13 then placed it on internal storage and flashed it (and gapps) from twrp and it worked fine.

Acetyloaceton said:
If I were you, I would try to reflash stock firmware with factory reset
Click to expand...
Click to collapse
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Artyb52 said:
@13ones I tried flashing the TWRP image, is that different to the factory image ?
Click to expand...
Click to collapse
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.

l3ones said:
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.
Click to expand...
Click to collapse
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this

Try this
Using adb sideload on twrp
1. Flash supersu 2.62, then
2. Flash supersu 2.65
Command : adb sideload supersu.xx.zip
In my case, it works.

Artyb52 said:
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this
Click to expand...
Click to collapse
If I'm not too late, sure. What model do you have?

Bricked Honor 6X BLL-L22 device, help is appreciated.

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.