Related
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance
ahadabdul said:
succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance
Click to expand...
Click to collapse
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
strongst said:
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
i am in soak test when i unlock bootloader and rooted it..when i wiped data it shows os not installed....what does it mean?
ahadabdul said:
i am in soak test when i unlock bootloader and rotted it..when i wiped data it shows os not installed....what does it means?
Click to expand...
Click to collapse
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade
strongst said:
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade
Click to expand...
Click to collapse
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:
ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?
strongst said:
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:
Click to expand...
Click to collapse
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..
echo92 said:
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?
Click to expand...
Click to collapse
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do
ahadabdul said:
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..
Click to expand...
Click to collapse
1)Again, you do not need root to install custom ROMs, only TWRP is required.
1a)Which TWRP have you flashed, is this the 32 bit or 64 bit version? If this is the official TWRP 3.2, I think that may be the 32 bit version. In which case, you'll want Resurrection Remix 5.8.5 https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
As you cannot boot properly, the easiest way to flash would be to boot your device to TWRP recovery, then connect your device to your computer. Your device's internal storage should be visible then, you may wish to back up your files at this point. Copy the RR custom ROM zip and the GApps package of your choice to your device and flash in TWRP as per the instructions. As usual with flashing custom ROMs, you will have to wipe /system, /data, cache and Dalvik in TWRP before flashing. Up to you if you choose to wipe internal storage as well (but usually a good idea switching between stock and custom ROMs).
Once you've booted into RR, you should have root as it already comes with magisk.
If you want to flash the RR 6.0 custom ROM, you must have the 64 bit TWRP recovery flashed before you attempt to flash the 6.0 custom ROM or any Oreo custom ROMs at the time of writing.
2)Alternatively, as strongst has suggested, if you simply want your device to be working again, you'll have to flash the latest stock ROM again, since you've likely tripped the anti-rooting measures in the stock kernel.
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
ahadabdul said:
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do
Click to expand...
Click to collapse
Which soak test, NPJ25.75-2? If so, that's a really old soak test, and as such I would recommend you flash the latest stock ROM available for your device, else you may run into issues with the newest custom ROMs, particularly if you have a G4 Plus. Can you mention what device and what region you're in, so we can guide you to the correct stock ROM to flash?
Yeah, that phone not turning on is because of SuperSU flashed onto the stock Nougat kernel, which you cannot do for our device - you need a custom kernel. The main ways to get around it are as I described above - flash a custom ROM or re-flash the correct stock ROM for your device.
Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck
superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.
superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.
Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help
Mouchoir said:
Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help
Click to expand...
Click to collapse
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?
Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state
strongst said:
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?
Click to expand...
Click to collapse
You did not answer all questions, so I only can guess...
Mouchoir said:
Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state
Click to expand...
Click to collapse
I'm guessing it downloads partial ota and not a full rom like about 1,7GB so the update fails. In case you have twrp you can easily download the 5.1.5 FULL zip from here and flash it https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
I am sorry that my answer wasn't complete.
- I do have the bootloader message
- The device is a year old, but only used by me
- It's trying to download 5.1.4 OTA which is 1609MB. It downloads everything and tries to install it
- No root is detected
- I don't have TWRP on the phone
Thanks for your answers
Best way it simply install latest TWRP like Sian, do a dirty flash with the full OOS Rom package (5.1.7) for force update.
1/ Do a full backup of your data / sms / pictures on your computer (just for be sure, you must always backup for big changes, especially with encrypted roms)
2/ install TWRP Sian
3/ On TWRP > Wipe > Dalvik/ART - Cache paritions
4/ Install > the latest stable OOS 5.1.7 Rom
5/ Just after that flash Magisk (if you want keep the custom recovery) or don't flash Magisk (stock recovery will erase TWRP after SetupWizard)
Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot
Mouchoir said:
Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot
Click to expand...
Click to collapse
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...
Pho3nX said:
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...
Click to expand...
Click to collapse
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff
Mouchoir said:
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff
Click to expand...
Click to collapse
If you have no twrp already installed on your device you must flash the twrp.img file with fastboot like "fastboot flash recovery twrp.img"
Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Pho3nX said:
4/ Install > the latest stable OOS 5.1.7 Rom
Click to expand...
Click to collapse
Would it work if I download it instead of the one you sent me ?
Thanks a lot
Mouchoir said:
Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Would it work if I download it instead of the one you sent me ?
Thanks a lot
Click to expand...
Click to collapse
Error 7 for me i tried i'm with unlocked bootloader latest TWRP by Eng.stk and i removed form the zip also compatibility.zip
Hello,
I finally managed to install the zip thanks to TWRP, but it seems that my cellphone is stuck on the boot turning logo with the two red dots turning around the big red one
Fixed : https://forum.xda-developers.com/oneplus-5/help/bricked-oneplus-5-t3884364