Alright.. Although this is worked on me last updates (B190 to B550 to B560 to B564 to B574) I DON'T PROMISE IT WILL WORK ON YOU!
as always, it is possible that you brick your device, break your sd card, your phone catches on fire, you start WWIII SO KEEP THOSE ON MIND
But.. for me when new update comes i just install it by doing normal force update but i press all three keys as long until i feel second vibrate.
This method is worked on me all those updates i wrote first AND I WERE INSTALLED TWRP AND ROOTED all the time.
When you install update by this method. You lose TWRP, Root access and all what you have flashed by TWRP.
EDIT: UPDATED ONLY USING FULL ROM!
So you don't need to install even stock recovery first?
For me it has worked great without stock recovery. I have always installed full rom so it installs stock recovery
So interesting!I'll try it.But it dosen't work for my honor 4C.
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
Has anyone tried going from Sokkoban's deodexed ROM (B564) to B574?
It seems like there are 2 recoveries or something. I have TWRP installed and once i held power + vol up wanting to enter TWRP, but it seems like i held it for too long and the phone booted into the stock recovery and in the top left corner it said "Huawei eRecovery"
Strange...
toncek333 said:
It seems like there are 2 recoveries or something. I have TWRP installed and once i held power + vol up wanting to enter TWRP, but it seems like i held it for too long and the phone booted into the stock recovery and in the top left corner it said "Huawei eRecovery"
Strange...
Click to expand...
Click to collapse
Yes if you extract firmware you see recovery.img and recovery1.img.
Lähetetty minun ALE-L21 laitteesta Tapatalkilla
Hi everybody, I tried to google it and search XDA so far, but am not quite sure.
I have ALE-L21C432B170 installed on my phone and downloaded the official update.app (ALE-L21C432B550) for Android 6.0.
So it should all be fine.
My phone is rooted + TWRP recovery but with Stock Rom, so no major changes at all regarding the OS.
Did I understand it correct that the update (using the running system or forced update) will work with my phone?
I am sorry if this was answered before, but it still remains unclear to me.
Thanks, Chris
cometophob said:
Hi everybody, I tried to google it and search XDA so far, but am not quite sure.
I have ALE-L21C432B170 installed on my phone and downloaded the official update.app (ALE-L21C432B550) for Android 6.0.
So it should all be fine.
My phone is rooted + TWRP recovery but with Stock Rom, so no major changes at all regarding the OS.
Did I understand it correct that the update (using the running system or forced update) will work with my phone?
I am sorry if this was answered before, but it still remains unclear to me.
Thanks, Chris
Click to expand...
Click to collapse
Hi Chris! For me, it worked while i updated from B190 to B550 so it should work from B170 too!
But i recommend you to download some newer version like B560 or B564 (No double tap bug)
Edit: and do force update
YOU WILL LOSE YOUR DATA SO BACKUP, BACKUP!
Hi Vika, thanks so far. I do backup regularly and especially before doing stuff like this... just wasn´t sure about user experience. I´ll consider trying. Otherwise, I will go back to standard ROM, update, and root & TWRP again.
Might take some time, but I´ll let you guys know.
Thx, Chris
It doesn't work, any ideas?
toncek333 said:
It seems like there are 2 recoveries or something. I have TWRP installed and once i held power + vol up wanting to enter TWRP, but it seems like i held it for too long and the phone booted into the stock recovery and in the top left corner it said "Huawei eRecovery"
Strange...
Click to expand...
Click to collapse
Huawei uses two recoveries yes
One stock recovery for updates and such hence recovery (1)
The other one is the "emergency" recovery which is EMUI recovery to download a firmware which usually fails anyway (maybe due to unlocked bootloader and removed drm?)
Also yes it's possible to install OTA due to the fact that TWRP uses a legacy script when it's installing OTA's which is used in regular recovery, therefor it won't fail this has been announced in TWRP changelog but few is understanding it.
Only downside is it will revert recovery and kill root.
and small updates will install just fine, doesn't matter which, just be aware if it mess up its not anyone else fault but yours if you update and it suddenly dies or bootloop
I confirme it works like a sharm
Related
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Boot into bootloader from recovery and select start.
prestige777 said:
Boot into bootloader from recovery and select start.
Click to expand...
Click to collapse
Yeah but it still can't install the update,any way fix it?
Boot to bootloader and flash the stock recovery from factory image. Then boot into stock recovery and the update should start.
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
dahawthorne said:
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
Click to expand...
Click to collapse
May I ask which version of TWRP did you use?
twrp-3.0.2-0-shamu.img
you cant flash an official factory image in twrp..this is a known fact...
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
dahawthorne said:
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
Click to expand...
Click to collapse
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
It seems that people don't read posts before writing. The OP clearly said that he had applied the OTA. I clearly said that this was exactly what I did with the same result. I also clearly explained what I did to fix it. The next comment should be from the OP saying what he's doing to recover. If he does what I did he'll be fine.
drmuruga said:
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
Click to expand...
Click to collapse
He can reinstall stock recovery and side load from there
Either flash the stock recovery.img through twrp or
Flash stock recovery through fastboot or
Install factory image through fastboot
Edit: oops didn't read the entire thread
itsagood said:
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Click to expand...
Click to collapse
To avoid issues, I'd say make sure you're 100% stock, recovery and all before installing an official update. Like I said, just to be sure it won't fail.
I got the the OTA notification before work yesterday. All day at work I was itching to install it but with no PC I couldn't risk it. I was on the DP5 with TWRP, no root, and unlocked. I couldn't wait. I flashed the OTA with TWRP after I restored a backup of when I first installed DP5. TWRP throw a couple of errors but after about 10 minutes of hanging on the boot animation it finally booted. My phone was encrypted but other then that it was fine. I was gonna root it afterwards but I was on stock recovery after flashing the OTA so I couldn't do anything until I got home. Made a noforc-nonverify boot IMG throw on TWRP reformatted. Running great now.
Edit: My DP5 boot.img was also noforc-nonverify.
Sent from my Nexus 6
Hello lovely XDA-members,
this morning a new OTA update/patch came out for my OnePlus 3T, so I downloaded and tryed to install it right away. My phone is rooted on android 7.0 and I have TWRP 3.0.3-0 installed as my recovery. Normally (when I updated to nougat) after downloading a new update the phone reboots itself into TWRP and installs the update by itself, but not this time. I had to seqrch through my phone and had to install thw update manually. After that I rebooted the phone and it started booting the TWRP recovery again, I tried it again and again and again, nothint changed. So I tried to restore my backup with everything functioning, but this wouldnt help either. :/ I read the few existing threads with this problem and heard of a recovery flag that isnt cleared and the bootloader being the problem. One solution that I found was only for an LG phone and I'm afraid that I'll brick my brand new phone I have absolutely no idea what to do now, I would be so happy if someone could help me with this :$
I thank you in advance <3
Encoutered the same problem. Either you reflash the official or twrp recovery (neither did the trick to me) or use this "emergency tool" (which helped me):
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
Btw: TWRP 3.0.3-0 is not working well, switch to 3.0.3-1 beta
Good luck to you
I had the same problem.
How you can ''unbrick it'':
1. Flash a any rom available for the oneplus 3t via twrp
a. after this you will be still in twrp bootloop, to solve this go to step 2
2. Flash back stock recovery via twrp
Now your system will boot again
Optional: Flash back twrp
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Isus <3 said:
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Click to expand...
Click to collapse
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
EYT said:
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pNVlxV3ljMUFaUHc/view
Thank you so much, it worked
EYT said:
Thank you so much, it worked
Click to expand...
Click to collapse
No problemos my friendos
Hello guys, I read lots of topics about this issue and I would like to explain mine.
I wanted to try Android 7 so I decided to update with B378 firmware.
First of all I got unlocked and rooted phone and I made a huge mistake because I forgot to unroot it before flashing the new firmware.
By the way, I flashed the B378 firmware following the dload method using the *#*#2468579#*#* menu and it worked.
At the first boot I immediately noticed that the phone was missing of all the system apps including camera, calculator, flashlight, keyboard.. and the build number appears to be NRD90M test-keys. The updater menu disappeared as well.
About the keyboard I fixed the problem simply activating it in the settings menu but all the apps were still missing.
I saw I had to flash the B378_update_data_full_hw_eu to restore the apps and here started the odissey.
I couldn't boot the recovery cause it was incompatible with Nougat so after a long search I found the TWRP 3.0.2-N and now it works.
I downloaded the B378_update_data_full_hw_eu.zip package, unzipped it in the dload folder but the hidden menu (*#*#2468579#*#*) isn't there anymore. Nothing happens when I digit that code.
So i tried to boot the phone with vol +, vol -, pwr button pressed and the emui recovery installed the package. Installation was 100% succesful.
The apps are still missing..
What's next step now?
A prerooted device not allows to flash hw/eu. Its your choice, downgrade, or Factory reset + flash the data package with dload.
dkionline said:
A prerooted device not allows to flash hw/eu. Its your choice, downgrade, or Factory reset + flash the data package with dload.
Click to expand...
Click to collapse
now my device is unrooted, the hw/eu flashes correctly but I still don't have the apps.
So I could try to wipe and factory reset via recovery and flash again?
Well I think I did worst than before..
I wiped and formatted from recovery and installed again the b378 firmware using vol+ vol- pwr combination (I had to do like this cause the hidden menu doesn't work), the flash was ok 100% succesful.
Before I still have the keyboard because I updated from my previous firmware but now I don't have it as all the other apps.
I tried then to flash the sw/eu, installation succesful 100% but it's the same! No apps, no keyboard, no updater menu....nothing.
What can I do? Format everything again and flash another firmware? Any suggestion? Which one is the best one for android 7?
Hello
I had the same problem. Wrocł the MM 136 and late 182, 360,361,378. I have all the applications and it works perfectly.
Only Downgrade and upgrade can solve it. But dont forget to unlock on b182 if you want root on B378.
dkionline said:
Only Downgrade and upgrade can solve it. But dont forget to unlock on b182 if you want root on B378.
Click to expand...
Click to collapse
please, can you tell me how to downgrade or can you give me a link?
thank you..it's so frustrating
MystikRiver said:
please, can you tell me how to downgrade or can you give me a link?
thank you..it's so frustrating
Click to expand...
Click to collapse
what was your stock build. ? here is downgrade instructions
Arnys said:
what was your stock build. ? here is downgrade instructions
Click to expand...
Click to collapse
Ok, I restored android 6 with emui 4.1.1 all it's working. Build B182.
I wonder if I can flash android 7 without problems
And? Do the update to B378?
Is really necessary pass by B360, 361, etc?
Thanks
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted
Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.
i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.
geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.
Hi,
in order to use some of my apps (SwiftBackup, AFWall+...) I unlocked the bootloader of my sweet, installed TWRP and rooted it using magisk.
Working fine so far, but when the device shows up an update (actually I am on 12.5.1 Global), the update file gets downloaded and then the device restarts.
But instead of updating, TWRP is entered.
Could please anyone advice me on how to apply the update?
I found the file downloaded, but I do not want to install something without knowledge (it is a company cell phone).
Best regards and thanks in advance,
Otto
sagaranuj said:
it happens because the phone doesn't have the official recovery installed anymore. When the phone boots and enters twrp, select the downloaded zip file (of miui update) and install it as you would do for a custom rom.
you might have to root the phone again though.
Click to expand...
Click to collapse
not work OTA update zip fule on twrp
seems like that :-(
I think, a custom ROM will be better anyhow...