Related
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
**edit: what....? never had to use that command before, but thanks a lot Entropy512 **
So this means, every time you update ota from baidu now, you have to unlock bootloader, first, then fastboot twrp, then install gapps + super su, phyy :silly:
spoonymoon said:
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-1.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
Click to expand...
Click to collapse
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Entropy512 said:
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Click to expand...
Click to collapse
Oem unlock don't make any difference, still locked, wont flash twrp, even it claims both oem unlock and flashing twrp.img went ok....but still stock recovery!?
They must have made some partition changes in 35, because when flashing through twrp, it gives two errors can't wipe data , but it don't give any flashing fail error, then when booting up it fc setup and won't continue , then booting into recovery again it's stock! ! Then flashing 35 through stock recovery, there's no errors and system boots up!
As said don't flash 35 you'll regret it
Think 34 is also similar in what you described.
To Entropy512......
What do you think will happen if we delete the new ´recovery dir (just including install_recovery.sh file) completly and replaced boot image from older ota version´s ? eks. from 33 which is not locked, i know because i flashed it and all ok and then put in 35 ota??
would it work you think? i dont have the guts to try...hehe
thx in advance
Try this. Download tantrums recovery flasher, unpack the zip on your computer, then in the "rec" folder go to "oppo" and extract the one other than "stock"
Now copy the modded recovery into the folder which contains fastboot.exe
And then "fastboot boot recovery.img"
the modded recovery will boot and then via that recovery, flash the tantrums recovery flasher. Aroma installer will start, then select twrp and flash what ever you like!
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Unlock bootloader.
Use ADB side load to flash stock rom.
Lock back bootloader. Voila!
Hope it helps. Thanks!
i tired
I tired but after the OTA update i get the dm message again
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
this
cpt.macp said:
this
Click to expand...
Click to collapse
I will try Tomorrow
cpt.macp said:
this
Click to expand...
Click to collapse
When i do this a have to unlock the bootloader so i have 1 message again ...
K3v1990 said:
When i do this a have to unlock the bootloader so i have 1 message again ...
Click to expand...
Click to collapse
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
ill go try that, thanks
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
for full restet u mean Factory restet in the settings?
Edit: found it
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
It worked thank you very much
When dm-varity warning is there, i flash openbeta 7 firmware &modem . Problem solved! Never see this warning. Phone works fine.when i flash openbeta 8 firmware &modem,i wil get back the dam-varity warning
LELBOT said:
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - https://docs.google.com/uc?id=0BzS3n...xport=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com/...BmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
Click to expand...
Click to collapse
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
m_reyna_16 said:
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
Click to expand...
Click to collapse
Yes, it will work.
For the new recovery, it supports f2fs decryption and u have flash it to follow the steps.
These methods will work.
Dm-verity
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
cryptofer said:
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
Click to expand...
Click to collapse
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
Hi,
to be synthetic:
From TWRP recovery, change filesystem to Ext4 for both Data and Cache, then full wipe everything (System too);
Go back to OxygenOS v3.2.8;
Be sure to replace TWRP with Stock Recovery (download from 3.2.8 official thread);
Lock bootloader (both from Developer Options and Fastboot);
Sideload via recovery OxygenOS v4.0;
Consider to factory reset for a clean installation.
For more clarifications, I'm at your disposal
https://www.androidfilehost.com/?fid=457095661767116249
flash it
Test by me
millicent said:
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
cryptofer said:
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
Click to expand...
Click to collapse
I haven't tried it yet but I read a few reports already about systemless root with magisk being able to preserve Android pay
Sent from my ONEPLUS A3000 using Tapatalk
Hello everyone,
This morning, I wanted to recover OxygenOS on my Oneplus3. I'm currently running Cyanogenmod 13.
I used the following guide: "[GUIDE] How to Unroot your OnePlus 3 / 3T and go back completely to stock" (Since I'm a newb, I can't post the link. But Google will get you there)
I booted into fastboot, issued the fastboot flash recovery recovery_op3.img and fastboot oem lock commands from my Linux termina, and rebooted in recovery mode.
In recovery mode, I then erased the cache and all that, selected the "Upgrade android from USB" and issued the adb sideload ota.zip command. This is where my problems began.
After running the command, I got the error "error: protocol fault (no status)". I tried to look this error up, but couldn't find useful information.
I started to panic a bit, fearing that my phone would be bricked. However, after booting back into fastboot mode, unlocking OEM, and rebooting, my phone would boot back into Cyanogenmod 13 (A clean install).
So now I don't have a bricked phone. However, I really would like to go back to OxygenOS, so my question is whether anyone knows how to solve my problem.
Summary:
Running Linux (Debian 8) on my PC;
Running Cyanogenmod13 on my Phone;
Want to recover OxygenOS, but adb sideload gave me "error: protocol fault (no status)";
Tried running the adb sideload command as root, however that did not work;
Can still use the Cyanogenmod13.
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Tybalt said:
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for responding.
I forgot to mention that I also tried killing the adb process several times, using the adb kill-server command and by killing the process sending SIGKILL.
Another thing I tried was using another Debian machine, which is my laptop. Still, those things did not solve my issue.
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
null0seven said:
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
Click to expand...
Click to collapse
Thanks for responding.
Since I don't understand everything yet, I will spend this evening looking up everything in detail, before I start giving it another try. Do you perhaps know of a tutorial about this specific situation? I don't want to bother you by questioning everything you stated in your instructions. They seem clear enough to be able to be looked up on Google :laugh:
drmuruga said:
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Click to expand...
Click to collapse
Thanks for responding.
By the steps after "if you want complete stock", do you mean that I should keep the bootloader unlocked, and then perform the same steps as in the tutorial that I used?
EDIT:
@ null0seven: I found these steps online as I was looking up some things you said (I don't have much time since I will celebrate eastern with my family today)
Rooted Users or users with ROMs other than OxygenOS having new bootloader (Official CM 13,CM 13 Based ROMs dated later than 04 June 2016,H2OS Marshmallow)
Step 1 :- Download the OxygenOS 3.0.2 full zip from the top of the post.
Step 2 :- Boot into TWRP.Wipe Dalvik,System,Data and Cache.After that,flash OxygenOS 3.0.2.
Step 3 :- [OPTIONAL] Flash SuperSU from here :- https://www.androidfilehost.com/?fid=24459283995297946
Step 4 -> Reboot System.
Of course, this is about an old version of OxygenOS. But it looks the same as you said.
I think this, combined with your instructions, will make it a bit clearer. Still one question: What do you mean exactly by flashing?
dvbeck
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?
Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot
Hello, I was just trying to install a custom ROM (Resurrection Remix) on my phone, but now I can't get out of the bootloader.
The steps I took were:
Install TWRP
Root with Magisk (for Titanium Backup)
Factory Reset in TWRP
Flash the RR rom zip file
and now when I turn my phone on, it goes through the bootloader unlock notice and the Google screen, but then it just goes into the bootloader.
I tried going into LineageOS recovery and doing an OEM sideload, but when I go into Apply Update --> Apply from ADB, on my computer, adb devices shows nothing.
Someone please help me.
SuperModder123 said:
Hello, I was just trying to install a custom ROM (Resurrection Remix) on my phone, but now I can't get out of the bootloader.
Click to expand...
Click to collapse
So fastboot should work. You can always flash the stock ROM first and continue from there.
Instructions: https://developers.google.com/android/images
Try the following,
Go back to stock
Boot twrp
Swipe to factory reset in twrp
Flash RR ROM zip
Flash TWRP zip
Boot to system (it should go to OS)
reboot back to TWRP
Flash custom kernel (optional)
Flash Magisk for root
Boot back to system