Hi,
Is it safe to re-lock my bootloader on the Nougat beta build? I'm stock recovery and not rooted, but I've heard rumours of people bricking their phones. Can anyone confirm?
Cheers
venomizer91 said:
Hi,
Is it safe to re-lock my bootloader on the Nougat beta build? I'm stock recovery and not rooted, but I've heard rumours of people bricking their phones. Can anyone confirm?
Cheers
Click to expand...
Click to collapse
I would say u don't do that rather u lock in stable OOS it will be better not to take risk.
Better to be unlocked if you take a bad OTA you can fix if locked your phone is dead
there is a good bulletproof unbrick method for the op3 using some qualcomm drivers magic, so however badly you mess up with your bootloader locked, there is always a solution... i'd say go ahead and tell us how it went and if safetynet api suspects anything
bombaglad said:
there is a good bulletproof unbrick method for the op3 using some qualcomm drivers magic, so however badly you mess up with your bootloader locked, there is always a solution... i'd say go ahead and tell us how it went and if safetynet api suspects anything
Click to expand...
Click to collapse
OK then report how it went when u do it
bombaglad said:
there is a good bulletproof unbrick method for the op3 using some qualcomm drivers magic, so however badly you mess up with your bootloader locked, there is always a solution... i'd say go ahead and tell us how it went and if safetynet api suspects anything
Click to expand...
Click to collapse
Great idea! Why don't you try it on your own?
@Dupleshwar, @LS.xD well, ok, i'll give it a go even though i don't need to lock it, i wanted to go back to resurrection remix anyway, so i won't miss oxygen os in the slightest if this goes wrong and i have to make a full wipe. note that i have the beta, am rooted and have flashed stock gapps over this mess of a beta. brb!
---------- Post added at 08:24 PM ---------- Previous post was at 08:12 PM ----------
bombaglad said:
@Dupleshwar, @LS.xD well, ok, i'll give it a go even though i don't need to lock it, i wanted to go back to resurrection remix anyway, so i won't miss oxygen os in the slightest if this goes wrong and i have to make a full wipe. note that i have the beta, am rooted and have flashed stock gapps over this mess of a beta. brb!
Click to expand...
Click to collapse
well, this was quick! what happened when i locked the bootloader via
Code:
fastboot oem lock
is, it went into an infinite bootloop, always flashing the op logo and then restarting etc. so when i booted fastboot via power+volume up, and did the usual
Code:
fastboot oem unlock
, it told me it would wipe the data, i chose yes and then it just normally booted exactly as before. it left my encryption, all the data, apps, photos etc. intact.
so while you can't lock the bootloader successfully, it is definetly safe to try
bombaglad said:
@Dupleshwar, @LS.xD well, ok, i'll give it a go even though i don't need to lock it, i wanted to go back to resurrection remix anyway, so i won't miss oxygen os in the slightest if this goes wrong and i have to make a full wipe. note that i have the beta, am rooted and have flashed stock gapps over this mess of a beta. brb!
---------- Post added at 08:24 PM ---------- Previous post was at 08:12 PM ----------
well, this was quick! what happened when i locked the bootloader via is, it went into an infinite bootloop, always flashing the op logo and then restarting etc. so when i booted fastboot via power+volume up, and did the usual , it told me it would wipe the data, i chose yes and then it just normally booted exactly as before. it left my encryption, all the data, apps, photos etc. intact.
so while you can't lock the bootloader successfully, it is definetly safe to try
Click to expand...
Click to collapse
Thanks for info. Have a good day or night
Related
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Make sure you are wiping data, cache and dalvik.
Make sure you didn't get a bad download on the rom you are trying to flash.
I am running stock kernels and have never installed any non stock kernels as stock seems to run just fine. I have wiped everything completely and I've tried two different roms and get the same problem. I don't think it has to do with it being bad downloads. Thank you for the advice though guys. Anyone else have any input? I may just have to go to the verizon store and see if I can exchange it out.
Dude. I had that too some weeks ago and had the problem that I encrypted the phone, which made me not getting into recovery mode. I downloaded a fresh restorer rom from samsung. After everything was fresh I never saw the failure again.
Sent from my Galaxy Nexus using XDA App
murflee33 said:
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Click to expand...
Click to collapse
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Geezer Squid said:
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
zephiK said:
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
Click to expand...
Click to collapse
Not kidding. That link to tells him how to return to stock and re-lock the bootloader.
So I went to far with modding, I didn't know when to stop, but now I do.
I have ROM toolbox (pro) and i started modding my phone like crazy, changing boot animations, icons and so on then i decided to change my framework (big mistake) But i still did it anyways all though it said use with extreme caution and i didn't think anything about it so i still did it and I made a backup it said it needed to reboot for it to work so I rebooted it turned on and everything slid the unlock slide and drew the unlock pattern and it froze and after about 5 seconds it restarted, i can do anything but unlock it and make an emergency call, when i tap emergency call it doesn't do anything not even restart, I have USB Debugging on and my backup of the framework is on my SD card, anything else you need just comment and i will tell you
All you have to do is go into recovery and restore a backup. You should still be able to get into recovery.
Lordomn said:
All you have to do is go into recovery and restore a backup. You should still be able to get into recovery.
Click to expand...
Click to collapse
i can't get into recovery, never could, by backup i meant backup of my framework
Are you on a custom kernel?
Lordomn said:
Are you on a custom kernel?
Click to expand...
Click to collapse
No, could never flash anything, sorry about not replying right away, I have to wait 5 minutes
How so? Is it because of pc or laptop? Drivers? Or just no want for it?
Lordomn said:
How so? Is it because of pc or laptop? Drivers? Or just no want for it?
Click to expand...
Click to collapse
I do really want to flash one but I don't know why i can't i think it because my phone can't go into fastboot or my phone boot loader can't be unlocked (for free) and i don't want to be scammed, something like that
You can still flash back to stock... If you have the ftf for your model. You will lose what you have but you can always redo the edits you have made.
---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------
But alejandrissimo is great at unlocking bootloaders. I had mine done ages ago. Can't remember how much but it was worth it.
Lordomn said:
You can still flash back to stock... If you have the ftf for your model. You will lose what you have but you can always redo the edits you have made.
---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------
But alejandrissimo is great at unlocking bootloaders. I had mine done ages ago. Can't remember how much but it was worth it.
Click to expand...
Click to collapse
Is that the only thing i can do or can i fix it without flashing because i dont want to lose everything but i willl if i have to
Only if you had a nandroid backup in recovery... There is a cwm installer for locked bootloaders. I used it for a while when I first got this phone. But that's the only way unless you manually push the old framework back into it then set permissions
Lordomn said:
But that's the only way unless you manually push the old framework back into it then set permissions
Click to expand...
Click to collapse
One last thing, how can i do this, sorry, but if you tell me and it works i will thank every post you made on this thread
Hi, in my attempts to get Lollipop from the stock rom of 4.4.4, I have severely screwed up my phone. I have tried a bunch of stuff, and I want to just wipe everything and start over. When I turn it on, it stays stuck at the green HTC logo.
When I try to run the RUU to either upgrade to Lollipop or even downgrade to get my phone working again, it gets stuck on the Sending... screen after rebooting the first or second time.
I am able to use fastboot and also get into TWRP recovery. I hope the screenshots and info provided are enough, but please let me know if I can provide more.
Looked for stock images in the internet? I think you will find one which is directly from HTC.
But why don't use CyanogenMod to get the version?
(sry for bad English, I'm from Germany)
---------- Post added at 11:59 PM ---------- Previous post was at 11:56 PM ----------
Cm12=https://download.cyanogenmod.org/?device=m8
(sry for bad English, I'm from Germany)
Well that's what I'm trying to do is the RUU for a stock rom. And nah, I don't wanna use CyanogenMod (unless you mean that will help me get back to stock somehow)? Thanks anyway!
Sry miss understood you...
(sry for bad English, I'm from Germany)
---------- Post added at 12:10 AM ---------- Previous post was at 12:06 AM ----------
Tried this way?
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
(sry for bad English, I'm from Germany)
Anyone else? Still no luck.
ethteck said:
Anyone else? Still no luck.
Click to expand...
Click to collapse
You could download a twrp backup and restore back to stock..
ethteck said:
Hi, in my attempts to get Lollipop from the stock rom of 4.4.4, I have severely screwed up my phone. I have tried a bunch of stuff, and I want to just wipe everything and start over. When I turn it on, it stays stuck at the green HTC logo.
When I try to run the RUU to either upgrade to Lollipop or even downgrade to get my phone working again, it gets stuck on the Sending... screen after rebooting the first or second time.
I am able to use fastboot and also get into TWRP recovery. I hope the screenshots and info provided are enough, but please let me know if I can provide more.
Click to expand...
Click to collapse
from the first screenshot (bootloader), the red OS line with two versions means the flash didnt go through properly!! (the hboot preupdate worked but the second flash wasnt done)
and it looks like you're on AT&T US, so use the following RUU:
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
make sure you have this installed http://www.microsoft.com/en-us/download/details.aspx?id=29
(otherwise the RUU will just exit)
no need to relock or anything with S-OFF (and absolutely stay S-OFF!!)
PS: running RUU will obviously wipe everything off your phone and also put back stock recovery, so you'll need to flash back TWRP once the RUU is done
Thank you both for your advice. I was able to get everything (or so I thought) working by using a TWRP backup, but I soon realized that most of my apps weren't working correctly. I was getting errors trying to download language packs for Swiftkey, Facebook wouldn't even open, etc. I'm currently trying the RUU, but it's doing what it had been doing in the past.
Here's a screenshot of what it looks like:
ethteck said:
Thank you both for your advice. I was able to get everything (or so I thought) working by using a TWRP backup, but I soon realized that most of my apps weren't working correctly. I was getting errors trying to download language packs for Swiftkey, Facebook wouldn't even open, etc. I'm currently trying the RUU, but it's doing what it had been doing in the past.
Here's a screenshot of what it looks like:
Click to expand...
Click to collapse
how long are you waiting? it does take some time...
otherwise, you'll need to flash firmware using fastboot (in ruu mode), cause currently your firmware is in a state of limbo, so not good place to be in
EDIT: the ruu log should be in C:\ruu_log\ folder, you could take a look at the file and see if/where it's hanging
Thanks so much nkk71! After retrying my phone is fixed!
So yesterday I was taking a look to xda developers when I saw a post with cyanogen mod 14 for the Nexus 5x so I installed it. Everything went ok but after looking at the OS for a bit I thought that the OS i had was better (it was nougat 7.1.1, beta program) so before installing cyanogen mod i had made a backup of my older system. I tried to restore the backup but when i tried to turn on the phone it froze when booting, and that started happening over and over, it turns on shows google logo starts booting and freezes, turn of, turns on ....
I've tried to install many diferrent roms from here xda, the normal ones in root toolkit and nothing works, every rom freezes when booting. I've wiped the phone i've done everything i could do in TWRP.
Please if someone out there can help i would be very thankful.
Im sorry for bad english!
Usually you repair it by flashing firmware
rp158 said:
Usually you repair it by flashing firmware
Click to expand...
Click to collapse
How can i do that?
mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150
Stevica Smederevac said:
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150
Click to expand...
Click to collapse
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!
mike_seventeen said:
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!
Click to expand...
Click to collapse
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.
Stevica Smederevac said:
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.
Click to expand...
Click to collapse
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting
mike_seventeen said:
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting
Click to expand...
Click to collapse
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery
Stevica Smederevac said:
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery
Click to expand...
Click to collapse
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
I've done factory resets several times in stock and custom recoverys
mike_seventeen said:
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
Click to expand...
Click to collapse
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.
Stevica Smederevac said:
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.
Click to expand...
Click to collapse
I'll do as you say, but if i can´t solve this i'm kinda screwed because i have no possibilities to buy another phone and i have this one for like 3 months, i have to solve this, i really do. Thanks for all the help! Really appreciated.
Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Edit: See post #14 for fix.
tauio111 said:
Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Anyway I did not manage to get it to boot again, I recommend you restore to stock via fastboot and lock your bootloader before you take it to warranty.
Click to expand...
Click to collapse
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))
mike_seventeen said:
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))
Click to expand...
Click to collapse
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .
tauio111 said:
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .
Click to expand...
Click to collapse
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I can´t explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:
mike_seventeen said:
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I cant explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:
Click to expand...
Click to collapse
No problem, just share the link to the thread from the 6P forums if you find someone with a similar problem.
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