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?
Related
I rooted my Nexus 5 this morning for the first time using chainfire and everything was fine and dandy. I then downloaded goomanager to install twrp and thought it was all good. Turns out when I booted into recovery, it was corrupted with the red triangle android. I restarted the device, but as I started it up, the device automatically went into action launcher as the default launcher. I thought this was strange (as the stock laucher has been my default since I got the phone) so I tried to change it back to the Google home launcher, but it was missing. Here's where I made the mistake. I figured if I deleted action launcher, the system would reinstall home, but it turns out I was greeted with a launcher-less and recovery-less nexus 5.
I tried to use adb on my computer but it would not connect. I do not have the option in device manager to update drivers, just to view them. Now my phone is at the splash screen with access to fastboot but no recovery.
Thanks in advance for assistance.
sully212121 said:
I rooted my Nexus 5 this morning for the first time using chainfire and everything was fine and dandy. I then downloaded goomanager to install twrp and thought it was all good. Turns out when I booted into recovery, it was corrupted with the red triangle android. I restarted the device, but as I started it up, the device automatically went into action launcher as the default launcher. I thought this was strange (as the stock laucher has been my default since I got the phone) so I tried to change it back to the Google home launcher, but it was missing. Here's where I made the mistake. I figured if I deleted action launcher, the system would reinstall home, but it turns out I was greeted with a launcher-less and recovery-less nexus 5.
I tried to use adb on my computer but it would not connect. I do not have the option in device manager to update drivers, just to view them. Now my phone is at the splash screen with access to fastboot but no recovery.
Thanks in advance for assistance.
Click to expand...
Click to collapse
first off, you need to do some reading on android.
2nd, your recovery is not corrupted, the red triangle android is the stock recovery. you didnt flash a recovery because goomanager isnt flashing twrp recovery since 4.4. it didnt even download it probably. what you have to do is flash the recovery while you are in fastboot. everything else you wrote i about the launcher i dont understand what you wrote. but before you go any further, you should learn about what you are doing before you do it. do not use a toolkit, you will not learn anything that way and could get yourself into an even worse circumstance http://forum.xda-developers.com/showthread.php?t=2508292
simms22 said:
first off, you need to do some reading on android.
2nd, your recovery is not corrupted, the red triangle android is the stock recovery. you didnt flash a recovery because goomanager isnt flashing twrp recovery since 4.4. it didnt even download it probably. what you have to do is flash the recovery while you are in fastboot. everything else you wrote i about the launcher i dont understand what you wrote. but before you go any further, you should learn about what you are doing before you do it. do not use a toolkit, you will not learn anything that way and could get yourself into an even worse circumstance http://forum.xda-developers.com/showthread.php?t=2508292
Click to expand...
Click to collapse
Thank you for the clarification. I attempted to flash recovery through adb commands, however, the device did not show up. I have tried multiple times to reinstall drivers, but to no success. When I go to device manager => nexus 5 => hardware => properties => drivers, the only available option is to view driver details, with no option to update, roll back, disable or uninstall them. Do you know how to fix this?
sully212121 said:
Thank you for the clarification. I attempted to flash recovery through adb commands, however, the device did not show up. I have tried multiple times to reinstall drivers, but to no success. When I go to device manager => nexus 5 => hardware => properties => drivers, the only available option is to view driver details, with no option to update, roll back, disable or uninstall them. Do you know how to fix this?
Click to expand...
Click to collapse
you dont flash the recovery via adb, you use fastboot while youre plugged into your computer and are in your bootloader. again, fastboot, not adb.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
oh, and if you have root already, you can flash twrp recovery using the flashify app(download twrp recovery to your phone, flash with flashify. and you can use the twrp manager app to download and install twrp
simms22 said:
you dont flash the recovery via adb, you use fastboot while youre plugged into your computer and are in your bootloader. again, fastboot, not adb.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
oh, and if you have root already, you can flash twrp recovery using the flashify app(download twrp recovery to your phone, flash with flashify. and you can use the twrp manager app to download and install twrp
Click to expand...
Click to collapse
Again, still a little puzzled. All this makes sense, but for some reason, all of my launchers were uninstalled in a reboot. Like this (http://forum.xda-developers.com/showthread.php?t=1212448). When I boot up, the splash screen is persistent and keeps rotating without the lock screen showing up. So, in a sense, the only thing I have access to on my phone is the fastboot menu. In all cases, I need to use adb to either push a new launcher app to my phone or flash a complete recovery.
sully212121 said:
Again, still a little puzzled. All this makes sense, but for some reason, all of my launchers were uninstalled in a reboot. Like this (http://forum.xda-developers.com/showthread.php?t=1212448). When I boot up, the splash screen is persistent and keeps rotating without the lock screen showing up. So, in a sense, the only thing I have access to on my phone is the fastboot menu. In all cases, I need to use adb to either push a new launcher app to my phone or flash a complete recovery.
Click to expand...
Click to collapse
adb doesnt work in the bootloader, but works in recovery. fastbootcworks while youre in your bootloader. try flashing a recovery. or you can start over by flashing the factory img via fastboot while in the bootloader. another reason i hate root toolkits, occasionally they themselves mess things up.
---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------
btw, some bad info in that thread you linked. bootloops dont happen if you have no launcher. nothing happens actually, just no launcher.
simms22 said:
adb doesnt work in the bootloader, but works in recovery. fastbootcworks while youre in your bootloader. try flashing a recovery. or you can start over by flashing the factory img via fastboot while in the bootloader. another reason i hate root toolkits, occasionally they themselves mess things up.
---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------
btw, some bad info in that thread you linked. bootloops dont happen if you have no launcher. nothing happens actually, just no launcher.
Click to expand...
Click to collapse
It works! So fastboot recognizes my device, now I just need to flash twrp through fastboot commands, correct? Thank you so much for your help!
Got it working! Thanks so much again... Thought I had a brick on my hands for a little while there. You're a lifesaver! +1!!!
sully212121 said:
Got it working! Thanks so much again... Thought I had a brick on my hands for a little while there. You're a lifesaver! +1!!!
Click to expand...
Click to collapse
sweet.. now im happy for you
I have stock recovery and can't boot. My model is currently reported as "g2" thanks to the mahdi rom which I screwed up flashing.
Has anyone been able to flash back to a stable firmware by bypassing the model check (using a special .dll, anything?).
datdude_tc said:
I have stock recovery and can't boot. My model is currently reported as "g2" thanks to the mahdi rom which I screwed up flashing.
Has anyone been able to flash back to a stable firmware by bypassing the model check (using a special .dll, anything?).
Click to expand...
Click to collapse
i had that problem once and this is what i did...
i booted back into recovery,TWRP or CWM,
i had TWRP , went to advanced wipe and wiped everything,
system,data,cache,dalvik cache
powered down and put it back in download mode and reflashed stock.
it seems that if you dont wipe system it is still picking it up as whatever model rom you flashed.
hope that helps...
podagee said:
i had that problem once and this is what i did...
i booted back into recovery,TWRP or CWM,
i had TWRP , went to advanced wipe and wiped everything,
system,data,cache,dalvik cache
powered down and put it back in download mode and reflashed stock.
it seems that if you dont wipe system it is still picking it up as whatever model rom you flashed.
hope that helps...
Click to expand...
Click to collapse
Appreciate the response, but I mentioned in my post that I have stock recovery. Not CWM or TWRP. No dice for me
datdude_tc said:
Appreciate the response, but I mentioned in my post that I have stock recovery. Not CWM or TWRP. No dice for me
Click to expand...
Click to collapse
well how did you flash mahdi? anyways do a adb push through stock recovery.
podagee said:
well how did you flash mahdi? anyways do a adb push through stock recovery.
Click to expand...
Click to collapse
So adb is accessible through stock recovery? I hold down+power until the LG logo, then release both, and press both again. This takes me to hard reset menu, not recovery. I press power three times, the andriod guy appears with a progress bar (i think it is attempting to factory reset here) and then it reboots. Everything I seem to find on Google/XDA indicates the only way to access a recovery mode is through a custom recovery.
If it's really this simple I'm going to flip.......ha
datdude_tc said:
So adb is accessible through stock recovery? I hold down+power until the LG logo, then release both, and press both again. This takes me to hard reset menu, not recovery. I press power three times, the andriod guy appears with a progress bar (i think it is attempting to factory reset here) and then it reboots. Everything I seem to find on Google/XDA indicates the only way to access a recovery mode is through a custom recovery.
If it's really this simple I'm going to flip.......ha
Click to expand...
Click to collapse
there is a recovery menu even through stock that you can reach. not sure how to get there except through your phone being on in the kk ui. i will try looking around. kinda busy at work so if i dont respond quickly im sorry. in the mean time try again through lgflashtool. make sure your sim card is out when doing it
---------- Post added at 10:46 AM ---------- Previous post was at 10:33 AM ----------
how did you get stock recovery back on your phone?
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
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.
So i tried flashing blu-spark twrp.. and magisk up until the moment i had to reboot after installing magisk... now the phone is stuck in this screen i dont know what do, help
What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update
dgunn said:
What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update
Click to expand...
Click to collapse
thanks, sorry dont have another phone to take a picture of this but its basically the screen we get when first booting that shows the device has an unlocked bootloader... the 'warning screen'
edit: **** the link was wrong
edit2: this one but in our device http://i.imgur.com/88NcI2K.jpg
+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.
Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.
lal000r said:
+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.
Click to expand...
Click to collapse
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
ptoner said:
Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.
Click to expand...
Click to collapse
Sorry, can you clarify your last bit about selecting the other boot?
habylab said:
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
Nothing was wiped. All data remain in place.
Click to expand...
Click to collapse