Related
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
fleity said:
hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Click to expand...
Click to collapse
llaalways said:
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
exactly what I did to get here :-/
What is the model of your phone? A2017G?
fleity said:
exactly what I did to get here :-/
Click to expand...
Click to collapse
yes it's a G
let me quickly sum up the current state:
the bootloader unlock screen is no longer displayed (which is very weird)
twrp gets stuck on the teamwin screen
holding power or basically any kind of reboot automatically boots into twrp
the phone is charging in this state and it is recognized by adb with the correct id but as "offline" similar to when you would connect it but not unlock it
the EDL I used is a B09 however I am coming from RR-O-v6. EDL full flashs "everything" therefore wondering if the bootstack B32-B10 I flashed only works with oreo roms etc. does not make any sense because twrp should work regardless, right?
I see that the edl tool can unlock the bootloader, does it make sense to actively unlock it (after full edl flashing B09 again) through that option in order to get twrp working correctly?
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
adb shell recovery --wipe_data
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/soc/6a00000.ssusb/6a00000.dwc3/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 153
I:LANG: en
Click to expand...
Click to collapse
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
you can put twrp 3.2.1.7 in Axon7_EDL_Tool\flash\recovery and rename it as recovery.img, then flash recovery from Axon7_EDL_Tool.
then check if you can actually use twrp.
fleity said:
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
Click to expand...
Click to collapse
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
adb works on recovery mode is weird.
you can try following options
1. Axon7_EDL_Tool flash full with A2017G_B11_MARSHMALLOW_FULL_EDL
2. Axon7tool write recovery on edl mode
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
3. Axon7toolkit, you need bypass virus check, there are a lot of options, including flash twrp, restore from hardbrick on edl mode.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
4. if everything failed, you can try 4th category brick repair
https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
fleity said:
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
Click to expand...
Click to collapse
I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.
bmurphr1 said:
I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.
Click to expand...
Click to collapse
1. forgot to remove dm-verity
2. There is a specific guide to return stock rom and undo warning menu, but it has flashing stock recovery b15 with jasminetool and install update.zp b17
stock recovery
stock rom
edit.
this is what appears if I am right?
juniorgerman said:
this is what appears if I am right?
Click to expand...
Click to collapse
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.
bmurphr1 said:
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.
Click to expand...
Click to collapse
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk
juniorgerman said:
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk
Click to expand...
Click to collapse
That makes more sense to me than just not including it in the guide. When my EDL cable comes in, I should be able to force the tablet into EDL mode and use jasminetool to return the tablet to the stock recovery image I backed up, and then use fastboot to push the original firmware on to the device or re-install TWRP and attempt to flash a working custom ROM. That makes me feel better about not knowing about the no-verity situation. I've seen the video of someone using a piece of copper and plugging the tablet into their computer and removing it about 5 seconds after plugged in, which forces the tablet into EDL mode just like a physical EDL cable does, and use jasminetool to restore the stock recovery. I will probably do it in Linux this next time around since you need to do some rather wonky things in Windows 10 to run jasminetool and zadig, including booting Win10 into Test Mode to remove driver signature reinforcement.
Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.
I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?
Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.
How do you know your bootloader is locked?
Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.