Database Develop

Updates after unlocked bootloader

Sorry for the nooby question but I am new to Huawei. Will I keep receiving updates after unlocking my boot loader ? What if I'll route my phone, will updates keep coming ?
Thanks for the help.

yes u can always receive & download updates.
u just cant flash the firmware if u r on custom recovery (twrp,etc). root will be removed. updates will overwrite system partition to stock.
Sent from my Huawei P9 Plus using XDA Labs

download update then you can just flash stock recovery (no need to remove later versions of SU as they are integrated into system) then after update, flash TWRP and SU (to get root back), takes 5 minutes.

I always flash TWRP to the erecovery (recovery2) partition, so no need to flash the stock Recovery before the update
This way you can have stock recovery & TWRP at the same time.

eintracht1895 said:
I always flash TWRP to the erecovery (recovery2) partition, so no need to flash the stock Recovery before the update
This way you can have stock recovery & TWRP at the same time.
Click to expand...
Click to collapse
good info. im new to this device. how to enter twrp after flashing to recovery2 partition.

monx® said:
good info. im new to this device. how to enter twrp after flashing to recovery2 partition.
Click to expand...
Click to collapse
When your phone boots just press volume up at the screen which says that your device is unlocked and can't be trusted. You also can use the apk from here: http://forum.xda-developers.com/showpost.php?p=67463880&postcount=6
By the way, do you plan to make a Rom for the P9 Plus? I know you from my old Xperia days and always loved your Roms

eintracht1895 said:
I always flash TWRP to the erecovery (recovery2) partition, so no need to flash the stock Recovery before the update
This way you can have stock recovery & TWRP at the same time.
Click to expand...
Click to collapse
How does one flash twrp to recovery 2 partition? Would love to set things up as you have, thanks
sent from my P9+

Jostian said:
How does one flash twrp to recovery 2 partition? Would love to set things up as you have, thanks
sent from my P9+
Click to expand...
Click to collapse
Just boot into fastboot mode and flash the TWRP.img with this command: “fastboot flash recovery2 twrp.img“ and replace twrp with the name of your twrp image.

eintracht1895 said:
I always flash TWRP to the erecovery (recovery2) partition, so no need to flash the stock Recovery before the update
This way you can have stock recovery & TWRP at the same time.
Click to expand...
Click to collapse
GENIUS!
there are 2 recoveries for this but I never thought about making use of the second one... How do you choose which recovery to enter into though?

zhuanyi said:
GENIUS!
there are 2 recoveries for this but I never thought about making use of the second one... How do you choose which recovery to enter into though?
Click to expand...
Click to collapse
If you want to boot into stock recovery, press and hold volume up right after you started/restarted your phone (you have to press the button before you see the Huawei logo).
For twrp just press and hold volume up when you see the screen which says your device is unlocked.
Or you can use the app from post #6.

Oneplus 3 decryption Ultimate guide

Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.

Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.

Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.

I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...

Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem

ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.

nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?

ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.

nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?

ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked

nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.

ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.

nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

P20 Pro - Bricked - tried everything...(!)

I was rooted through Magisk on firmware .255, but I saw an approved update for firmware .280 which I wanted, and I also wanted to go back to stock for a while. I downloaded the update.zip, extracted the .img needed and flashed accordingly; cust, erecovery, system, cache, kernel, recovery, userdata, etc, all I could.
I now can't get it to boot no matter what I try. I always end up on the screen "Your device has been unlocked and can't be trusted" and then stuck on "Your device is booting now". I can get into eRecovery and/or flash TWRP.
I've tried the below;
Flashing dload folder on a USB OTG
Flashing update zip in TWRP
Flashing update zip with Huruupdater in TWRP
Flashing through fastboot update (update.app extracted)
Flashing through fastboot update_full_base (update.app extracted)
Going through HiSuite - it sees the recovery but then says "No recovery packages found for your phone"
Wipe data etc.
I did forget to remove fingerprint security before I did this, my bootloader is unlocked and FRP.
Genuinely never bricked a phone before! Any help would be appreciated.

I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?

Don't make me buy a pixel tomorrow!

belloni said:
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Click to expand...
Click to collapse
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again

otonieru said:
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
Click to expand...
Click to collapse
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?

belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
EDIT: I've found the old magisk_patched.img but when I flash it says "FAILED (remote: partition length get error)

belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
from other phone with magisk installed.
other thing you might want to try is enter stock recovery (not TWRP) and wipe /data and cache from there
just a heads up though,
your way of updating the OS is totally dangerous, you could.messed up partition,
you should use EMUI Flasher instead

I have a guide to fix this in the guides section. Follow it and you'll be fine.

Find somebody that had a p20 pro rooted to send you a backup of their software (with the data partition wiped).

https://forum.xda-developers.com/showpost.php?p=79107368&postcount=82

Question Cant Access Pixel Experience recovery after installing it

So i already install pixel experience recovery on my phone, no error or anything but i cant seem to access it. when i tried to go into recovery mode, instead accesing pixel experience recovery it just go into miui recovery.
is the installation failed? or im doing something wrong?

Inhuman11 said:
So i already install pixel experience recovery on my phone, no error or anything but i cant seem to access it. when i tried to go into recovery mode, instead accesing pixel experience recovery it just go into miui recovery.
is the installation failed? or im doing something wrong?
Click to expand...
Click to collapse
PE recovery? Do you mean, an image?, if this is the case, you should need to proceed the same way as if TWRP is.

SubwayChamp said:
PE recovery? Do you mean, an image?, if this is the case, you should need to proceed the same way as if TWRP is.
Click to expand...
Click to collapse
and how to do it? install guide in their website didnt include anything after image instalation

I have the same problem. You should probably post this in the PE thread.

Inhuman11 said:
and how to do it? install guide in their website didnt include anything after image instalation
Click to expand...
Click to collapse
Not sure if you are referring only to the recovery image (I didn't usually saw it available to download it though), or to the ROM, to be flashed through it.
If you say for the PE recovery image, you have to boot to it, using fastboot, and then from PE recovery, flash it onto the ramdisk and reboot again to recovery to be sure you get it.

SubwayChamp said:
Not sure if you are referring only to the recovery image (I didn't usually saw it available to download it though), or to the ROM, to be flashed through it.
If you say for the PE recovery image, you have to boot to it, using fastboot, and then from PE recovery, flash it onto the ramdisk and reboot again to recovery to be sure you get it.
Click to expand...
Click to collapse
Here is the link to img file and the rom. https://download.pixelexperience.org/spes
And already tried it using fastboot, still going to miui recovery.
Is it because i install it on boot_a instead to boot_b ?

Inhuman11 said:
Here is the link to img file and the rom. https://download.pixelexperience.org/spes
And already tried it using fastboot, still going to miui recovery.
Is it because i install it on boot_a instead to boot_b ?
Click to expand...
Click to collapse
Firstly, you can't install it using fastboot, you should need, to boot to it, only.
And from the PE recovery screen, you should need to flash it on the ramdisk, not sure if this option is available, as it has limited options, in this case, if not, you'd need to boot (and probably flash) TWRP, and from there, flash the PE recovery image onto the ramdisk.
And for the next, an image you need to flash using fastboot (not available for recovery) you don´t need to target to any slot, unless you have a good reason, because the flashing process is done in the active slot.

I still have the same problem.
Any solution?

I have this same issue, I at least think. Here's where I'm at.
I downloaded the build and the recovery image for Pixel Experience, specified for my device. I got as far as to use "fastboot flash boot PixelExperience.img" onto the device.
The phone is now unable to reboot, and the OS stops responding whenever I do anything with it. I can't reboot to recovery, or reboot at all. I'm not sure if I'm supposed to wait, and for how long?
I followed the directions on the Pixel Experience website found here:
- https://wiki.pixelexperience.org/devices/fog/install/