Related
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
I think you got the "cannot receive hello packet", because your bootloader is locked. Using this method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 to unlock it, then flash twrp, then firmware
The bootloader was unlocked (though it may have been unintentionally re-locked somehow?), and MiFlash works with a locked bootloader, so I don't think that's the issue. Axon7tool also doesn't help, because just like adb it can't find the device.
Now, trying again today, MiFlash is working for some reason. I haven't done anything differently, but I can flash whatever I want with MiFlash now. But it doesn't really make a difference, because the phone is still entirely unresponsive, I can't enter recovery or boot in any way. Any suggestions for what else to try?
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
bkores said:
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
Click to expand...
Click to collapse
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Aspoehro said:
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Click to expand...
Click to collapse
Ok so TWRP is definitely not the problem. Can you remember exactly when the problem happened, like after SuperSU was flashed since you mentioned using the Flash TWRP and root option?
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Aspoehro said:
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Click to expand...
Click to collapse
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Gnreux said:
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Click to expand...
Click to collapse
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
bkores said:
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Click to expand...
Click to collapse
I can't be sure since I don't know exactly what the problem is or how I caused it. All I really have are guesses at this point.
Aspoehro said:
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
Click to expand...
Click to collapse
I rebricked myself last night (lol), so I had to reflash full package, from the same link you posted, and here are some notes:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Second boot worked (and I now remember that the same thing had happened the first time I bricked my device), but Android asked me for a password even though I had formatted /data
From there, install TWRP via fastboot (and fastboot_unlock prior to that if bootloader is locked, it shouldn't be), format /data using TWRP, reboot, and you should have a working device
Hope it helps!
Gnreux said:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Click to expand...
Click to collapse
I don't even get that much, nothing I do gets any response from the phone at all. No LED when trying to boot (including EDL or recovery), no LED when charging, the only indication that the phone isn't perfectly dead is that it shows up in device manager and MiFlash.
You could try not flashing fastboot_unlock right away and booting first instead... This is the only thing we are doing differently, although I don't see how it could have an impact.
You could also try flashing this EDL package (B13) instead and flash your device specific bootstack afterwards.
Still no luck with anything I try to flash in MiFlash. But I tried reinstalling drivers with Zadig, and axon7tool is working this time. Trying to read gpt works fine, but if I try to read/write boot or recovery, I get "W: bad lba in partition entry 26" and "Cannot find partition boot"/"Cannot find partition recovery". I tried writing TWRP and a couple stock boot/recovery images despite the error, still no change.
Do those error messages give any new information that might be helpful?
Try miflash firmware from offical:
https://www.zteusa.com/axon-7#support
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
lipe123 said:
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
Click to expand...
Click to collapse
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Flapjack said:
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Click to expand...
Click to collapse
Glad it helped someone!
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse
1. make sure you're in download mode, not bootloader
2. make sure twrp.img is in your sdktools folder
maybe a bad download of twrp?
The saga continues...
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse
PodCulture said:
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
Click to expand...
Click to collapse
yes, after s-off u have to format data
OMJ said:
yes, after s-off u have to format data
Click to expand...
Click to collapse
I've no problem doing that, but teh phone isn't letting me do it.
PodCulture said:
I've no problem doing that, but teh phone isn't letting me do it.
Click to expand...
Click to collapse
How are you trying to format data?
Sent from my unknown using XDA Labs
Unlocked needs root and twrp
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
OMJ said:
How are you trying to format data?
Sent from my unknown using XDA Labs
Click to expand...
Click to collapse
PodCulture said:
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
Click to expand...
Click to collapse
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Thanks! Got everything back up and running now. Nice to have a phone I can use the way I want to again. TONS of bloat though.
OMJ said:
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
How did u get s off
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
You're not waiting long enough.
And by the way it tells you to press the power button to PAUSE booting.
It's only a few second wait (possibly one second longer than the default unlocked message on other devices). I just timed it. It's 8 seconds. A regular device will display that message for 3-4 seconds.
It just means that your bootloader is unlocked.
Sent from my ONEPLUS A6013 using Tapatalk
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
Had this issue on my op6. This solution fixed it for me. not sure if we have this tool for the 6t yet. If the message is orange then it's the unlocked bootloader message. If it's in red it's the corrupt message and you gotta hit the power button twice to boot.
The message i get is in RED color. Not in ORANGE.
And yes if you press twice the power button it boots normally.
My question is about how to get rid of this!!!
If for some reason the device is gonna reboot -like in Settings-> Utilities-> Scheduled power on/off- it wont boot until I get action...
Fear!!!
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
azzinder said:
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
Click to expand...
Click to collapse
And password
iaTa said:
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
Click to expand...
Click to collapse
Waiting patiently for news...
azzinder said:
Waiting patiently for news...
Click to expand...
Click to collapse
Rescheduled to tomorrow
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Done
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
This works! It is a lot easier than the MSM download tool solution. However, I wonder if it just mutes the notification, or solves the problem indeed?
I flashed a TWRP backup afterwards and that did not go well. I wonder if that could be caused bij the corrupt problem?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Doesnt working for me. after reboot also i can see same error. however i can boot after twice pressing on power. i do not want to use Msm tool as it will format data. seems no other way as of now
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Hey that's amazing! I think this has finally solved this for me on my OnePlus 6. I was perfectly content to just put up with that warning forever, but this seems to have cured it ... And simple too! Thanks ?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Thanks, this worked.
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
No the device is not corrupted. Unlocked bootloader warning vs the device is corrupt are 2 different things. My bootloader ia unlocked since the day 1 and never had the corrupt warning until I flashed OOS 9.0.5. The step above resolved the device is corrupt issue.
---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------
kitcostantino said:
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
Click to expand...
Click to collapse
Yeah I agree its something to do with the slot A and B. I was running the phone with unlocked bootloader since day 1 and had flashed multiple twrp updates, kernels etc and never had the issue. It's when i recently flashed OOS 9.0.5 and then twrp on it is when this started.
Not sure about OP6T but on my OP6 the terminal commands helped.
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
This worked on my 6T ! Thanks !
Sorry if this sounds dumb but I've been out of the modding game for a long time and I barely knew what I was doing when I started. I've had 2 other devices since I last rooted so something's aren't adding up.
When I view my files in TWRP they seem almost encrypted, mainly the sdcard. If I wanted to install an image or zip file in the past I would find them on the sdcard and flash away. I attached a video to show in detail what I am seeing. Sorry for the poor quality. EDIT: sorry, after uploading my gif I see it only made it a thumbnail. I'll work on a correct version.
Thank you in advance.
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
OhioYJ said:
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
Click to expand...
Click to collapse
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
tjlmbklr said:
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
Click to expand...
Click to collapse
Yeah, either use a USB drive through OTG or copy it to internal (when in OOS) and use fastboot to boot the newer TWRP. You should be able to install from internal storage after that.
Disable fingerprint, smartlock , face recognizing etc.
It's security related.
Reboot
Then the folders show normal
tjlmbklr said:
I'm running 9.0.11
I'll try that version you linked. Thanks. I assume I have to install using adb sor USB OTG since my internal file system is encrypted, right?
Click to expand...
Click to collapse
9.0.14 has the May security patch and the new encryption, which will be an issue. I'm not sure why you are seeing that with 9.0.11, but definitely try the other version I linked to, I know it is up to date. Worst case, as mentioned, if you temporarily remove your password / pin code / pattern everything will just work. However then you will have to redo this, along with all your finger prints. Not that it's a big deal. Just get the right TWRP, and you won't have to do that.
OhioYJ said:
They are encrypted. I see you are using BluSpark's TWRP, what OS / Version are you running? Does BluSpark work with the May security patch? Previous versions of TWRP had problems with the latest security patch and could not decrypt it.
Boot 3.3.1-6 from here then see if your files are still encrypted.
Click to expand...
Click to collapse
Duvel999 said:
Disable fingerprint, smartlock , face recognizing etc.
It's security related.
Reboot
Then the folders show normal
Click to expand...
Click to collapse
OhioYJ said:
9.0.14 has the May security patch and the new encryption, which will be an issue. I'm not sure why you are seeing that with 9.0.11, but definitely try the other version I linked to, I know it is up to date. Worst case, as mentioned, if you temporarily remove your password / pin code / pattern everything will just work. However then you will have to redo this, along with all your finger prints. Not that it's a big deal. Just get the right TWRP, and you won't have to do that.
Click to expand...
Click to collapse
Temporarily disabled? I'm not sure how to disable other than delete the fingerprints all together. Will I need to do this every time I need.to boot into recovery?
tjlmbklr said:
Temporarily disabled? I'm not sure how to disable other than delete the fingerprints all together. Will I need to do this every time I need.to boot into recovery?
Click to expand...
Click to collapse
If you just delete your password / pin / etc, it will automatically delete all your finger prints and your TWRP problem will go away. No you should NOT need to do this. This is only because you don't have an up to date, or the wrong version of TWRP installed. I never remove my password and go into TWRP all the time. It's not an issue.
tjlmbklr said:
Sorry if this sounds dumb but I've been out of the modding game for a long time and I barely knew what I was doing when I started. I've had 2 other devices since I last rooted so something's aren't adding up.
When I view my files in TWRP they seem almost encrypted, mainly the sdcard. If I wanted to install an image or zip file in the past I would find them on the sdcard and flash away. I attached a video to show in detail what I am seeing. Sorry for the poor quality. EDIT: sorry, after uploading my gif I see it only made it a thumbnail. I'll work on a correct version.
Thank you in advance.
Click to expand...
Click to collapse
I think all you need to do here is turn off your screen lock by setting it to "None."
When you reboot to TWRP, you should see the files now unencrypted.
TWRP had the potential to allow you to input a "Pattern" screen lock, but I can't guarantee it will work under all circumstances, nor do I know what it does with fingerprint scans, etc.
I unlocked my bootloader, then tried to flash TWRP through fastboot but that's where something weird happened. It flashed successfully, but the next time I booted my device into recovery, the stock recovery came up. So I flashed TWRP again.
Then I flashed the decrypt.zip and Magisk.zip, and the zip to enable camera2api. And rebooted device, only to notice that my WiFi just isn't turning on. And it's been a mess since then. (My device did get rooted though)
So I tried booting my device, and there comes up Google's device setup which NEEDS internet access, and I realised my WiFi isn't turning on.
I tried everything. Wiping data, cache, factory reset, even tried flashing stock ROM again but it gave an error saying:
"This file is for device "xxxxxx" while your device is " " "
It just said " ", nothing. So I realised I can't even flash ROMs now.
But hours later I managed to get past the device setup by (recharging and) using mobile data, and realised my IP Address was showing as N/A and WiFi MAC Address as 02.00:00:00:00:00
After another loads of hours, I managed to fix my IP Address thanks to a thread on XDA, but the MAC still remains that way.
So after hours of research, now at 4AM, I came to the conclusion that I gotta use BusyBox and Terminal Emulator to change it.
But now, what do I set my MAC Address to? How do I find my original Address? Is that even possible?
Need help on this ASAP, please.
Thanks in advance.
sarthak882 said:
I unlocked my bootloader, then tried to flash TWRP through fastboot but that's where something weird happened. It flashed successfully, but the next time I booted my device into recovery, the stock recovery came up. So I flashed TWRP again.
Then I flashed the decrypt.zip and Magisk.zip, and the zip to enable camera2api. And rebooted device, only to notice that my WiFi just isn't turning on. And it's been a mess since then. (My device did get rooted though)
So I tried booting my device, and there comes up Google's device setup which NEEDS internet access, and I realised my WiFi isn't turning on.
I tried everything. Wiping data, cache, factory reset, even tried flashing stock ROM again but it gave an error saying:
"This file is for device "xxxxxx" while your device is " " "
It just said " ", nothing. So I realised I can't even flash ROMs now.
But hours later I managed to get past the device setup by (recharging and) using mobile data, and realised my IP Address was showing as N/A and WiFi MAC Address as 02.00:00:00:00:00
After another loads of hours, I managed to fix my IP Address thanks to a thread on XDA, but the MAC still remains that way.
So after hours of research, now at 4AM, I came to the conclusion that I gotta use BusyBox and Terminal Emulator to change it.
But now, what do I set my MAC Address to? How do I find my original Address? Is that even possible?
Need help on this ASAP, please.
Thanks in advance.
Click to expand...
Click to collapse
Try flast AFT ROM.
Sent from my ZenFone Max Pro M1 using Tapatalk
RedGreenBlue123 said:
Try flast AFT ROM.
Click to expand...
Click to collapse
You mean to flash any stock ROM using the Asus Flash Tool? So do I flash this latest version of stock ROM with it? https://forum.xda-developers.com/showpost.php?p=81227331&postcount=2
RedGreenBlue123 said:
Try flast AFT ROM.
Click to expand...
Click to collapse
Thanks a lot! I flashed the 340 ROM and that fixed it all, although I'm now back to Oreo and locked bootloader.
So gonna go through unlocking it and rooting my phone again, hoping I don't end up in this mess again. Thank you!
sarthak882 said:
Thanks a lot! I flashed the 340 ROM and that fixed it all, although I'm now back to Oreo and locked bootloader.
So gonna go through unlocking it and rooting my phone again, hoping I don't end up in this mess again. Thank you!
Click to expand...
Click to collapse
Yeah, man. Don't use Pie AFT because it is not stable. 340 is the best AFT ROM.
Sent from my ZenFone Max Pro M1 using Tapatalk
RedGreenBlue123 said:
Yeah, man. Don't use Pie AFT because it is not stable. 340 is the best AFT ROM.
Click to expand...
Click to collapse
Wait, it's messed up again damnitttt
I used the Pie AFT, the 059 one. And now my phone just isn't booting, it shows the "boot loader is unlocked" warning (which it shouldn't? as AFT re-locks the bootloader, no?), shows the Android, ASUS logo and switches off
Man how do I fix this now
I was trying to get to Pie so that I can flash Havoc OS then. Please help
I might be able to get back to the 340 using AFT again, but then how do I update to Pie without using AFT? I'm still new to this, please help
Edit:
Also, this time the AFT just suddenly closed after (apparently) completing its process, and it didn't take as long as it took when flashing the 340. And my phone was still in Fastboot mode. So when I rebooted my phone, it surprisingly asked for a password. I didnt enter anything and it said Invalid Password, and I restarted my device and since then it's just not booting up.
Edit 2:
Wait it seems I made a really stupid mistake, my drive ran out of space, so I think the AFT couldn't extract the zip file completely.
I'm now trying it from another drive with space. Hopefully this time it'll all work fine
sarthak882 said:
Wait, it's messed up again damnitttt
I used the Pie AFT, the 059 one. And now my phone just isn't booting, it shows the "boot loader is unlocked" warning (which it shouldn't? as AFT re-locks the bootloader, no?), shows the Android, ASUS logo and switches off
Man how do I fix this now
I was trying to get to Pie so that I can flash Havoc OS then. Please help
I might be able to get back to the 340 using AFT again, but then how do I update to Pie without using AFT? I'm still new to this, please help
Edit:
Also, this time the AFT just suddenly closed after (apparently) completing its process, and it didn't take as long as it took when flashing the 340. And my phone was still in Fastboot mode. So when I rebooted my phone, it surprisingly asked for a password. I didnt enter anything and it said Invalid Password, and I restarted my device and since then it's just not booting up.
Edit 2:
Wait it seems I made a really stupid mistake, my drive ran out of space, so I think the AFT couldn't extract the zip file completely.
I'm now trying it from another drive with space. Hopefully this time it'll all work fine
Click to expand...
Click to collapse
Just install 060 FW only from here and it will work for Havoc:
https://sourceforge.net/projects/shanudey/files/X00TD/Firmware
Sent from my ZenFone Max Pro M1 using Tapatalk