Related
RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery
Code:
adb reboot recovery
. When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Which twrp you flashed? Check the correct twrp in my signature for honor 5C repository.
TassiloBalbo said:
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery . When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Click to expand...
Click to collapse
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
hassanjavaid8181 said:
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
Click to expand...
Click to collapse
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Meaning you can boot to fastboot but your pc doesn't recognise it?
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Did you try all method to going in fastboot.by adb fastboot command or by pressing vol- and power button?
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Glad that you fix your device.
If it is not bothering you let it be and enjoy using your phone.
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
TassiloBalbo said:
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
Click to expand...
Click to collapse
Try removing the usb cable and then try to biot to fastboot. What about erecovery
shashank1320 said:
Try removing the usb cable and then try to biot to fastboot. What about erecovery
Click to expand...
Click to collapse
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
TassiloBalbo said:
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
Click to expand...
Click to collapse
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
shashank1320 said:
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
Click to expand...
Click to collapse
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
TassiloBalbo said:
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
Click to expand...
Click to collapse
Meaning the fastboot is accessible.
Now you have firmware zip, extract it amd you will get few files. Use dload method as given in my signature and you are good to go.
Else use Huawei extractor and browse to update.app you just got in above downloaded zip. You will get boot, recovery, system img you need.
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
TassiloBalbo said:
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
Click to expand...
Click to collapse
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
shashank1320 said:
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
Click to expand...
Click to collapse
NEM-L31 but I don't know the build number
TassiloBalbo said:
NEM-L31 but I don't know the build number
Click to expand...
Click to collapse
Build number is necessary to get right files..
hassanjavaid8181 said:
Build number is necessary to get right files..
Click to expand...
Click to collapse
I know. So do you think it's dead?
TassiloBalbo said:
I know. So do you think it's dead?
Click to expand...
Click to collapse
You should try huawei service center....
Please excuse my lack of knowledge I am a complete beginner.
My wife left her working Asus k013 (do not know which model as I no longer have box) on charge over night, next day it would no longer get beyond the boot screen. We are stuck with the Asus Logo and the revolving boot start symbol.
I have tried the start/volume up and start/volume down options to do factory reset but just returns to the boot start. If I hold the buttons down for a long time it just shuts down. I them tried downloading 'clear data' to sd card but this presumably requires the tablet to boot before it works.
I have purchased a new tablet for her so I do not want to send the tablet for repair but would really like to get it working as spare and to experiment with rooting etc. to try an improve my knowledge.
If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?
Asus k013 stuck on boot
lambdadroid said:
If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?
Click to expand...
Click to collapse
Thanks for trying but this still ends up trying to do a normal boot without completeing
593jim said:
Thanks for trying but this still ends up trying to do a normal boot without completeing
Click to expand...
Click to collapse
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?
Asus k013 stuck in boot
lambdadroid said:
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?
Click to expand...
Click to collapse
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.
593jim said:
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.
Click to expand...
Click to collapse
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?
lambdadroid said:
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?
Click to expand...
Click to collapse
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim
593jim said:
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim
Click to expand...
Click to collapse
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?
Asus k013 stuck on boot
lambdadroid said:
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?
Click to expand...
Click to collapse
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Asus k013 stuck on boot
593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, should have added 'Fastboot device' no longer works.
May need to go back to my friend for help.
Can't see how to attach the photo.
Regards,
Jim
593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, this might have been confusing but I didn't post all needed steps yet. I just wanted to make sure you actually get to the droidboot screen.
Since you managed to get there, this is what I recommend: Use https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 on the "NORMAL START, RECOVERY MODE" etc screen to get into a temporary recovery session. For this tablet you should use trigger T4 and TWRP portrait. Copy the UL-K013-WW-12.10.1.36-user.zip you already downloaded to a external SD card first.
Once you are in recovery, you can try flashing the ZIP. This might restore your system to a usable state.
As for fastboot devices not showing any device: On Windows you may need to install the right USB drivers to make it work properly. You can try the Universal ADB drivers available from https://adb.clockworkmod.com/ or the USB driver provided by ASUS http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip. I cannot help you with this because I'm not using Windows much myself.
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
---------- Post added at 06:46 AM ---------- Previous post was at 06:40 AM ----------
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus
Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.