Develop Bugs

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

Stuck at boot.. can get into bootloader but not sure what to do next...

Hi everyone, this all started when I tried to flash a patched boot image for root and seemed to get worse from there. There's no data on the phone that I care about so just wiping it and getting it to boot would be preferable.
I've tried using the skipsoft toolkit (I have the ultimate version if that helps any) to try and get it to flash a freshly downloaded stock image, but for whatever reason after answering all the questions it extracts everything, does all the checks, then says "device is not set" and just jumps back to the main menu.
I've tried downloading the factory image right and running the flash-all script, it goes through the entire process which looks promising, but then just reboots the phone, I get the nice "your device is corrupt" message, press the power button to continue, but then it just hangs at the white "Google" splash screen with the little unlocked icon at the bottom, and doesn't move past that.
I know the version that I had on here prior to the problems was 8.0.0 (OPD1.170816.010, Sep 2017), so that's the one I've been trying to work with.
Not really sure where to go next, hoping someone has some advice for me.
Thanks everyone.

how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again

Never use a toolkit, they can hide error messages and displays that can help diagnose some issues. Always try the step by step methods to rescue provided by the excellent guides available here.

uicnren said:
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Click to expand...
Click to collapse
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..

krash2k said:
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
Click to expand...
Click to collapse
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.

uicnren said:
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
Click to expand...
Click to collapse
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.

krash2k said:
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
Click to expand...
Click to collapse
:good:

uicnren said:
:good:
Click to expand...
Click to collapse
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)

krash2k said:
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
Click to expand...
Click to collapse
honestly, Im not sure. But I also didnt think it would make a difference when flashing the stock images back, but it does. I guess anything is possible.

Yep.. it definitely did. I guess this is a lesson for knuckleheads like me who start messing around before properly updating everything.
I just did all of the same things I did earlier, and it booted fine, with root. Lots of wasted hours over a dummy move.
Thanks again for all the help!

I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?

State.of.mind said:
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
Click to expand...
Click to collapse
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:

Badger50 said:
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Click to expand...
Click to collapse
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command

State.of.mind said:
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
Click to expand...
Click to collapse
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.

v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
On second thought I think that it didn't work because I didn't have the factory image unzipped inside of the platform tools folder? The good news is that I'm up and running

v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?

nickmilla15 said:
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
Click to expand...
Click to collapse
Go back to the basics. Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december). Add that folder to your path statement/environment. Download the FULL image (not OTA). Open that zip file and extract into the same ADB/fastboot folder. Do not unzip the included, nested zip file! Open flash-all.bat and remove the -w switch and SAVE. Boot your phone to the bootloader, and then run the script either way (clicking or fastboot window). There are SO MANY better guides/tutorials out there to follow step-by-step. Maybe read/post in those if you have any further issues. Best of luck.

v12xke said:
Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december).
Click to expand...
Click to collapse
This was my mistake when I was having all of those problems. I was using older versions of adb/fastboot. Everything looked like it was installing alright but then it would just keep bootlooping.. was very frustrating. It was a relief when replacing those binaries with the updated ones worked flawlessly.

if you have managed to get it work then have fun otherwise just use deuces script as per the instructions provided in op.

Pixel 2 xl bricked i think so..

Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..

You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.

Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen

Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!

Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!

also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.

I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.

mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!

thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)

Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator

Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!

Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?

Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!

CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.

xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?

I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.

With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.

Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?

Followed the mega unbrick guide; WiFi and bluetooth don't work

Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?

rahulkulhalli said:
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
Click to expand...
Click to collapse
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?

Puddi_Puddin said:
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Click to expand...
Click to collapse
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.

rahulkulhalli said:
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
Click to expand...
Click to collapse
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
simonsmh said:
for those lost modem imei wifi carrier etc
Flash stock oos or h2os ROM then reboot to fastboot
fastboot erase modemst1
fastboot erase modemst2
good luck!
Click to expand...
Click to collapse

Puddi_Puddin said:
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
Click to expand...
Click to collapse
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Remove those files then flash the same OOS if possible
Click to expand...
Click to collapse
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!

rahulkulhalli said:
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
Click to expand...
Click to collapse
Probably you meet the hardware issues. You can try it because it has no damage to your device.

simonsmh said:
Probably you meet the hardware issues. You can try it because it has no damage to your device.
Click to expand...
Click to collapse
Um, does that mean the h/w is faulty?

Don't know what to do, am stuck with errors

I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help

IAmNotANerd said:
I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help
Click to expand...
Click to collapse
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?

Badger50 said:
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?
Click to expand...
Click to collapse
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.

IAmNotANerd said:
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.
Click to expand...
Click to collapse
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335

Badger50 said:
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Click to expand...
Click to collapse
Could you walk me through it? Its kinda greek to me

as of now Im with no TWRP and my system says 'No Command' many times, sometimes just gets stuck on the android loading google logo screen. or sometiems says that 'deivce is corrupted' screen

IAmNotANerd said:
Could you walk me through it? Its kinda greek to me
Click to expand...
Click to collapse
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:

Badger50 said:
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:
Click to expand...
Click to collapse
This is where I am now. Should I go ahead and factory reset my device? Or is there some error during installation? (Kind of thought as it said some files weee missing as attached in the photo there)

IAmNotANerd said:
This is where I am now.
Click to expand...
Click to collapse
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.

Badger50 said:
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.
Click to expand...
Click to collapse
I did the steps you said to me in that mode, then this opened, all on its own.

Also now it’s giving me two options only. Try again, and factory reset, can do one only I suppose.

IAmNotANerd said:
I did the steps you said to me in that mode, then this opened, all on its own.
Click to expand...
Click to collapse
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.

Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Yep, repeating procedure and updating you soon.

Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/

IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
Yeah, you may have not done yourself any favors when you incorrectly installed twrp.
I now recommend you use the Dueces script. It has saved a bunch of people in your predicament.
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
You can find it here.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.

IAmNotANerd said:
Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.
Click to expand...
Click to collapse
Congrats bruh! Now do some reading before you jump into the fire again :good:

Badger50 said:
Congrats bruh! Now do some reading before you jump into the fire again :good:
Click to expand...
Click to collapse
This needs to be said. Read everything you can before doing anything. Read everything about the problems that you might come across. And, most importantly, read about how to fix things if you aren't successful. I knew nothing, apart from what I'd read, and I've managed seven phones and three tablets, plus my brother's phones and tablets. I have never bricked any device, because I read and follow instructions. The great thing is, you can learn a lot from guides and such, because, if you're paying attention, you get a better understanding of what is going on.
He's right...read everything you can before doing anything you don't know how to do or understand. And, just for good measure, ask before, and not after you get yourself into a bad situation

Just my two cents... Is incredible how people takes risk on a 1000 dollars phone...