Database Info

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?

[RECOVERY] TWRP 7.1 (unofficial)

Current build
tulip-twrp-7.1-r1.img
MD5: bdf289666fc7262b8f3af7f5b579ecaa
Built: Oct 18, 2017
Installation instructions
The easiest way to install is using tuliptool. See the tuliptool thread for details.
Notes
r1 should be fully functional. Please report any bugs.

Tried it, but...
I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.
Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys
v1.2.0B09 installed

Oh. Yeah. I'll fix that. The problem is that the flash tool wants an image that is an even multiple of the sector size.
In the mean time, you should be able to use dd in adb shell from the old twrp to update.
mattx1002 said:
I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.
Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys
v1.2.0B09 installed
Click to expand...
Click to collapse

File is now padded to 1mb boundary. OP updated with new MD5. Please re-download and try again.

Is this for b12 or b14?

Should work with both b12 and b14.
MrWhite0429 said:
Is this for b12 or b14?
Click to expand...
Click to collapse

Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin

Yes just flash the recovery. Boot to recovery by holding the volume up button with the power button. I don't think stock updates recovery at boot, but I'm not sure.
Note you will need the custom boot image with verity disabled if you change anything in the system partition. I think SuperSU also disable verity, or at least can.
MrWhite0429 said:
Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin
Click to expand...
Click to collapse

Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
I can not get back into EDL or Recovery. ugh....
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.

I'm confused how you killed android by flashing recovery.
Is it possible you flashed the modified b12 boot image on a b14 system? If that's the case just flash back the backup. I'll create a b14 boot image asap.
MrWhite0429 said:
Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
I can not get back into EDL or Recovery. ugh....
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.
Click to expand...
Click to collapse

I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14
---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------
Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold
Power button THEN press and hold volume up.
Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.
---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------
Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.

Let me know if you get the device working again. I can help if you can't figure it out.
I am still confused about what could have happened...
MrWhite0429 said:
I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14
---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------
Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold
Power button THEN press and hold volume up.
Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.
---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------
Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.
Click to expand...
Click to collapse

Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.

Oh.... by any chance did you let twrp mount system read/write? Even once? That destroys the verity integrity.
MrWhite0429 said:
Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.
Click to expand...
Click to collapse

The Device is also not responding to the wall charger any more. Im afraid if the battery dies I may have a perminantly bricked device.

Don't worry, you can't brick the device if you can get to EDL.
MrWhite0429 said:
The Device is also not responding to the wall charger any more. Im afraid if the battery dies I may have a perminantly bricked device.
Click to expand...
Click to collapse

I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?

Let's assume you did allow twrp to mount system RW and your verity integrity is destroyed. Just upload the original b14 boot image and I'll make a modified version with verity disabled. That should get you running again.
Note I'm getting ready to go out with my wife so it will be a few hours until I can do that.
MrWhite0429 said:
I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?
Click to expand...
Click to collapse

Just flashed the backup B14 boot that I had and no luck. Device still hangs at splash.

MrWhite0429 said:
Just flashed the backup B14 boot that I had and no luck. Device still hangs at splash.
Click to expand...
Click to collapse
Flash stock recovery and try to flash with the original firmware zip

Twrp and Xiaomi.Eu Error

So i tried to install the xiaomi.eu rom on my MiMix 2s but something went terribly wrong. First of all i got Twrp to work and installed the rom. After pressing reboot though the phone just rebooted into fastboot. Now i cant get back into Twrp neither can i reboot to the System. Everything just gets me back to fastboot.
When i try to get back into the recovery, after typing "fastboot boot 'recovery' " i get an Error: "FAILED (remote: Failed to load/authenticate boot image: 00000050)"
I also tried to get the global rom back with the MiFlash tool but it seems the fastboot rom download page is currently down.
Any help would be greatly appreciated.

Try to flash the recovery instead of just booting it(I don't get why people are always only booting in recovery, so useless) did you format everything before flashing xiaomi.eu rom?

Flatric said:
Try to flash the recovery instead of just booting it(I don't get why people are always only booting in recovery, so useless) did you format everything before flashing xiaomi.eu rom?
Click to expand...
Click to collapse
I am doing that first but in the guide in this Forum it tells you to boot the recovery. Also "fastboot reboot recovery" does not work(fastboot: usage: unknown reboot target recovery) and i dont know any other way to get into the recovery on that phone.

neeboq said:
I am doing that first but in the guide in this Forum it tells you to boot the recovery. Also "fastboot reboot recovery" does not work(fastboot: usage: unknown reboot target recovery) and i dont know any other way to get into the recovery on that phone.
Click to expand...
Click to collapse
Just type fastboot flash recovery [name_of_recovery.img].img (place the recovery.img in the correct folder on your computer of course). You can boot in recovery by holding powerbutton and louder button when the device is powered of. Did you flash the correct xiaomi.eu rom for our device?

Flatric said:
Just type fastboot flash recovery [name_of_recovery.img].img (place the recovery.img in the correct folder on your computer of course). You can boot in recovery by holding powerbutton and louder button when the device is powered of. Did you flash the correct xiaomi.eu rom for our device?
Click to expand...
Click to collapse
Ok so booting into the recovery from the phone doesn't work Right now because i cannot shut the phone down. Every time i longpress the powerbutton or the powerbutton + volume button i just get a Restart into fastboot.
Aaand i just checked and idiot me downloaded the wrong Xiaomi.eu Rom .
It is just really unfortunate, that the official MiUi download Servers are offline and that i can't even get the official Version now.

neeboq said:
Ok so booting into the recovery from the phone doesn't work Right now because i cannot shut the phone down. Every time i longpress the powerbutton or the powerbutton + volume button i just get a Restart into fastboot.
Aaand i just checked and idiot me downloaded the wrong Xiaomi.eu Rom .
It is just really unfortunate, that the official MiUi download Servers are offline and that i can't even get the official Version now.
Click to expand...
Click to collapse
Well that means you most likely ****ed up the partitions on your phone... and when flashing the recovery doesn't work you have to wait for miui download servers(at least that's my point if knowledge)
---------- Post added at 20:48 ---------- Previous post was at 20:46 ----------
neeboq said:
Ok so booting into the recovery from the phone doesn't work Right now because i cannot shut the phone down. Every time i longpress the powerbutton or the powerbutton + volume button i just get a Restart into fastboot.
Aaand i just checked and idiot me downloaded the wrong Xiaomi.eu Rom .
It is just really unfortunate, that the official MiUi download Servers are offline and that i can't even get the official Version now.
Click to expand...
Click to collapse
Nevermind I got your back hehe http://en.miui.com/thread-2804733-1-1.html scroll a bit and you find a workaround to get the files just tested it and I can download the necessary roms
---------- Post added at 20:56 ---------- Previous post was at 20:48 ----------
Let me know if you were succesfull afterwards

Flatric said:
Well that means you most likely ****ed up the partitions on your phone... and when flashing the recovery doesn't work you have to wait for miui download servers(at least that's my point if knowledge)
---------- Post added at 20:48 ---------- Previous post was at 20:46 ----------
Nevermind I got your back hehe http://en.miui.com/thread-2804733-1-1.html scroll a bit and you find a workaround to get the files just tested it and I can download the necessary roms
Click to expand...
Click to collapse
Well this is Kind of embarrassing but after leaving the Phone unattended for ~10 minutes i found it turned off. I tried to get into the recovery with the power button + volume button and it worked. I am now downloading the(hopefully) Right Version of Xiaomi.eu and will try to install that.
Thank you so much for your help

neeboq said:
Well this is Kind of embarrassing but after leaving the Phone unattended for ~10 minutes i found it turned off. I tried to get into the recovery with the power button + volume button and it worked. I am now downloading the(hopefully) Right Version of Xiaomi.eu and will try to install that.
Thank you so much for your help
Click to expand...
Click to collapse
Good luck, if you got more questions just ask them

Unable to install miui eu beta zip rom
Hello, i hope you can help me out. I just unlocked Mix2s and it was a hard time to flash twrp on it. Twrp from miui eu forum website is no good i think. Very laggy and orange? So i succeeded flashing twrp v7 from xda. But when i want to install miui eu zip rom 8.7.19 it just won't happen. It seems the phone or twrp does not accept the rom. And it's the polaris rom. I just don't get it.
After unlocking i first flashed the fastboot rom (tgz) miui 10 (phone was on 9.6), but i think that was not necessary. After that i flashed twrp and formatted, because i wanted a clean flash of the eu rom. Was formatting a mistake?
Is my phone missing a partition / file now?
It just won't install the zip rom.
Any suggestions? Thanks!

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.