Related
Phone was fine, rooted, flashed roms,
Today flashed a rom and was a bad flash, now im stuck in bootloader screen, and try to select recovery twrp is gone.
tried to select factory reset from there just kicks me back to same fastboot/bootloader screen.
Anyway to restore to stock and redo everything? Was able to force twrp on last time but laptop isnt recognizing phone right now.
Thanks in advanced
solved, thank you.
nitty917 said:
Phone was fine, rooted, flashed roms,
Today flashed a rom and was a bad flash, now im stuck in bootloader screen, and try to select recovery twrp is gone.
tried to select factory reset from there just kicks me back to same fastboot/bootloader screen.
Anyway to restore to stock and redo everything? Was able to force twrp on last time but laptop isnt recognizing phone right now.
Thanks in advanced
solved, thank you.
Click to expand...
Click to collapse
I am going through the same mess right now. Flashed a ROM, bad flash...lost TWRP, so I thought to use hasoon's tool...well I relocked like a moron and still stuck so if anyone would like to chime in that would be awesome...
hooover said:
I am going through the same mess right now. Flashed a ROM, bad flash...lost TWRP, so I thought to use hasoon's tool...well I relocked like a moron and still stuck so if anyone would like to chime in that would be awesome...
Click to expand...
Click to collapse
If you relocked then you gotta unlock while you are in fastboot mode with your Unlock_code.bin. The other option is to flash the Stock RUU and use that, but I'm sure you rather have a Custom Rom. I'm going thru the same thing atm. Anyway use hasoon's tool to unlock your phone again.
yea just start from scratch now. RUU and return to stock
TygerByte said:
If you relocked then you gotta unlock while you are in fastboot mode with your Unlock_code.bin. The other option is to flash the Stock RUU and use that, but I'm sure you rather have a Custom Rom. I'm going thru the same thing atm. Anyway use hasoon's tool to unlock your phone again.
Click to expand...
Click to collapse
Unfortunately, I am being told not found by the tool now, and being stuck in boot loader it won't detect the device....I feel like a heel, I have been around for a while and never had an issue like this!
Yea, you guys are correct...Unlocked boot loader again via Hassoon's tool [Many thanks to this guy], question...where did my TWRP originally go? OP sorry I came in and jacked the thread, I just figured we were fighting a common battle.
hooover said:
Unfortunately, I am being told not found by the tool now, and being stuck in boot loader it won't detect the device....I feel like a heel, I have been around for a while and never had an issue like this!
Click to expand...
Click to collapse
it has to be "FASTBOOT USB" in order for the tool to unlock your phone again. i would check your htc drivers and possibly restart your computer if you haven't done so already.
TygerByte said:
it has to be "FASTBOOT USB" in order for the tool to unlock your phone again. i would check your htc drivers and possibly restart your computer if you haven't done so already.
Click to expand...
Click to collapse
Yea, I got it...THANK YOU! Patience is something I lack at times.
Used the Multi tool to unlock, then it booted right back to my custom ROM...I had to reflash TWRP, which boggles me...
I have a rather odd issue. I've been using the M preview, and after I rooted it, it restarted on me randomly. Anyway, I now have a fresh update to 5.1.1 from stock 5.1. My bootloader is re-locked, the bootloader version is matched to the proper system version, the stock recovery is in place. There is just one problem. Whenever I try to turn off the phone, restart it, enter recovery from android, connect it to a pc, or any other task that takes me out of android, it always boots to the bootloader and I have to choose it from there. There doesn't seem to be any issue getting to anything, it's just I can't change anything about the bootloader no matter what I do. I've been there and back again with unlocking, re-flashing and even now taking a full stock ota from a locked BL. I'm really stuck and could use some help. In the meantime, I'll keep trying and update if I can get anywhere with it. Thanks for reading!
Perhaps something is going on with your volume rocker. Does your volume rocker function normally? Maybe you have a case that could put some pressure on the volume rocker?
Actually, my problem was that the fb_mode_set was enabled, which will always boot into it. It's a stock precaution for updates. The solution was to enable fb_mode_clear, which returned the phone to booting normally. I hope if anyone gets into this situation down the road, this helps them out.
-Mike
kibmikey1 said:
Actually, my problem was that the fb_mode_set was enabled, which will always boot into it. It's a stock precaution for updates. The solution was to enable fb_mode_clear, which returned the phone to booting normally. I hope if anyone gets into this situation down the road, this helps them out.
-Mike
Click to expand...
Click to collapse
You might want to explain to them how to do it
danarama said:
You might want to explain to them how to do it
Click to expand...
Click to collapse
+1 yes please.
Sure. I clean flashed M and rooted it. It randomly rebooted twice on me when I tried to get a script to access root. After that, it was a bootloop at the regular startup screen. So, I entered into TWRP next, it started flashing. The only thing to do was to get into bootloader and reflash via fastboot, so that's what I did. I knew that I could downgrade the BL because it's a preview, but that wasn't my intention at the time. I took the google image of LYZ28E and flashed that, including the bootloader, fresh. Everything worked fine, except that the bootloader was now the first startup screen no matter what I did. I even downgraded to .08, which is as far back as you can go on 5.1! It didn't matter. BL was always the first screen up. So today, I started looking at the configuration of the BL. It seems that there is a safety protocol built into the BL that switches on when an unexpected error occurs, or when the BL is downgraded. It's there for things like firmware updates, etc. so that you don't end up with mismatches, which could potentially brick the phone. It makes sense, actually. Since I rolled back, it just switched on. I just wish there had been a little more literature on fastboot oem commands and their uses, it would have made for quite an easier time with this. Anyway, if you find yourself always starting up at the BL, try fastboot oem fb_mode_clear, which will disable the safety loop, and it should boot regularly. Again, I hope this helps, and if anyone has any questions, feel free to shoot me a message.
Edit: The entire process (TL;DR version)
1. Enter fastboot mode (if it's not already up)
2. Connect your phone to your pc
3. Open terminal
4. Type "fastboot oem fb_mode_clear"
5. Restart phone. It should now boot regularly.
-Mike
kibmikey1 said:
Sure. I clean flashed M and rooted it. It randomly rebooted twice on me when I tried to get a script to access root. After that, it was a bootloop at the regular startup screen. So, I entered into TWRP next, it started flashing. The only thing to do was to get into bootloader and reflash via fastboot, so that's what I did. I knew that I could downgrade the BL because it's a preview, but that wasn't my intention at the time. I took the google image of LYZ28E and flashed that, including the bootloader, fresh. Everything worked fine, except that the bootloader was now the first startup screen no matter what I did. I even downgraded to .08, which is as far back as you can go on 5.1! It didn't matter. BL was always the first screen up. So today, I started looking at the configuration of the BL. It seems that there is a safety protocol built into the BL that switches on when an unexpected error occurs, or when the BL is downgraded. It's there for things like firmware updates, etc. so that you don't end up with mismatches, which could potentially brick the phone. It makes sense, actually. Since I rolled back, it just switched on. I just wish there had been a little more literature on fastboot oem commands and their uses, it would have made for quite an easier time with this. Anyway, if you find yourself always starting up at the BL, try fastboot oem fb_mode_clear, which will disable the safety loop, and it should boot regularly. Again, I hope this helps, and if anyone has any questions, feel free to shoot me a message.
Edit: The entire process (TL;DR version)
1. Enter fastboot mode (if it's not already up)
2. Connect your phone to your pc
3. Open terminal
4. Type "fastboot oem fb_mode_clear"
5. Restart phone. It should now boot regularly.
-Mike
Click to expand...
Click to collapse
Hi! I know I am a bit late to reply but for me the "fastboot oem fb_mode_clear" did not do the trick.
I started to play around with the commands and I finally got the alternative. This one did fix the issue for me, and for anyone whose phone did not get fixed by Mike's method, try this--
do steps 1,2,3 for Mike's method and on the 4th step use "fastboot oem fb_mode_clear system" instead of just "fastboot oem fb_mode_clear".
-Sakuta
Hope I had been of help to at least one person. : )
I have had issues with my zenwatch 3 being crazy slow on android wear 2.0, and i read some possible solutions..
I also have an issue where whenever i turn my watch on it says "device software cannot be checked for corruption" and it makes it take an additional 10-15 seconds to boot up. This has been on the watch since i got it (i bought used and the bootloader was already unlocked, if thats why its doing that. When going through forums I also saw mention for disabling dm verity and wondered if that would get rid of that annoying screen.
I wanted to see if i could remove the zenfit stuff, cause i saw that some users claimed speed improvements, so i flashed twrp, and when i booted in i accidentally said to allow modifications (even though now i see that people say not too). I didnt make any changes while in here, but thought that might be important to state. In the instructions to remove zenfit i again saw to disable dm verity, so i moved onto that.
I then connected through adb and ran the command fastboot oem disable_dm_verity, but that didnt seem to do anything. I then ran the command "adb reboot "dm-verity enforcing" which i dont think was a good one to run, and i wonder if caused my issue. When i tried to boot back into twrp it would boot to a dead android.
I decided at this point that instead of screwing things up further, i would just flash to AW 1.5 and hope for speed improvement there. I downloaded the files, and through fastboot flashed the stock 1.5 boot, system, and recovery. using this thread https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
i rebooted the device and it went to the android wear screen and loaded for a while, and then to the upgrading android screen. when it got to step 7 it went back to the aw loading animation and then attempted to boot up and gave an error "unfortunately process android.process.acore has stopped" and started all over again trying to upgrade android and then getting to this point and failing. I then downloaded the images for stock 2.0 and flashed and got the same exact error.
I then tried to flash twrp again, and now if i try to flash 1.5 or 2.0 it just goes to a dead android screen. I can boot into twrp still with the boot adb command
I want to try flashing 1.5 or 2.0 through trwp, but my watch will not mount/connect at mtp to my PC while at twrp for some reason...
Any ideas or solutions? how can i flash everything straight back to default. Including whatever i may have done to the dm verity?
Please help
If ADB and Fastboot is working on your watch, try this
csrow said:
If ADB and Fastboot is working on your watch, try this
Click to expand...
Click to collapse
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Coltonbyu said:
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Click to expand...
Click to collapse
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
csrow said:
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
Click to expand...
Click to collapse
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Coltonbyu said:
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Click to expand...
Click to collapse
Glad it worked out.
If you want to stay at 1.5, you know what to do.
So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!
avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?
Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible
i have the same situation here. did your issue solve?