Related
Hi I want Resurrection Remix with the Homebutton working (since I am on 3.5.3 right now) and I am not sure how to do that. I have a couple of theory's.
theory 1: Flash full 3.2.4 OOS Rom then Flash RR and GApps.
theory 2: Flash 3.2.4 FIRMWARE along with RR and GApps.
theory 3: Flash Full Official CM13 Rom with GApps then flash RR and GApps.
Please help me because I need to know this.
Use 3.5.0 fw from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Flash it as is and reboot. No need to flash RR again.
3.2.4
kgs1992 said:
Use 3.5.0 fw from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Flash it as is and reboot. No need to flash RR again.
Click to expand...
Click to collapse
I have not flashed RR yet so should i used 3.2.4 FW?
3.2.4 or 3.5.0 either will work
kabrty said:
I have not flashed RR yet so should i used 3.2.4 FW?
Click to expand...
Click to collapse
Flash the firmware before flashing RR.
aadityarulez said:
Flash the firmware before flashing RR.
Click to expand...
Click to collapse
Doesn't matter, they don't flash the same partitions.
Flash
I will factory reset in twrp, then i will flash RR, then
GApps, then 3.2.4 FW, wipe cache/dalvik then boot
Can someone confirm if this will work?
kabrty said:
I will factory reset in twrp, then i will flash RR, then
GApps, then 3.2.4 FW, wipe cache/dalvik then boot
Can someone confirm if this will work?
Click to expand...
Click to collapse
It will work
Thanks
Thanks all of you, you guys are. Phone savers
So TWRP got overwritten by ONEPLUS STOCK RECOVERY so I will flash official twrp with 3.5.4 and then flash RR.
UPDATE: It got overwritten by Oneplus recovery AGAIN. Should I just go back to 3.2.6 then to RR?
Alright so i am going to flash modified TWRP, since the official gets overwritten by STOCK, then try to flash RR in that twrp.
Can someone confirm?
So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.
HI,
Every time I flash a custom rom, it doestn't boot. it goes back to TWRP..
The only time it boots is when I flash rom with official twrp. And it boots with few things missing like magisk and other apps. Bluspark and codeworks doesn't boot.
Stock rom downloaded from oneplus also doesn't boot if the recovery is not official TWRP or the stock one..
Is there something I am missing?
Thanks...
Any ideas?
bibekdwa said:
Any ideas?
Click to expand...
Click to collapse
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
MsuatafaKhatab said:
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
bibekdwa said:
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
Click to expand...
Click to collapse
No problem to flash later
Sent from my ONEPLUS A5010 using Tapatalk
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Macusercom said:
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Click to expand...
Click to collapse
I am now back to stock OB1. Whatever custom rom I flash, it has been troublesome.
Last flash was successful, Audax rom. It had nothing missing. I flashed speaker mod, it worked. Then, I tried a custom kernel, blu-spark for nougat. it bootlooped to Qualcomm loader mode..
I have flashed many phones in the past without any problems for 4 years.. but this time it's not working for me..
Is there any 5T specific step that I am missing?
1. Unlock bootloader.
2. Flash Custom recovery. And boot it.
3. Wiped everything including internal storage.
4. Reboot to recovery.
5. Flashed Rom and then magisk and no-verity.
6. Wiped cache ( only sometimes)
7. After this step, the rom doesn't boot. It comes back to recovery using blu_spark and codeworkx... Stock twrp lets it boot but without magisk.
Then, I flashed magisk... It did the same thing, reboots to recovery.
I tried using magisk uninstaller. It didn't work.
Everytime it goes in to loop, I always had to format data because internal storage was not shown. (0mb)
I have never felt this noob...
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Flash ROM and Gapps and then boot into system. After setting up, flash twrp again and Magisk. No-verity is needed only if you wanna flash certain unencrypted ROMs, in which case formatting data would also be required.
Did you do both fastboot OEM unlock, as well as enabling the option in developer options?
Macusercom said:
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Click to expand...
Click to collapse
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
bibekdwa said:
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
Click to expand...
Click to collapse
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
sardelisp said:
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
Click to expand...
Click to collapse
I was having same issues so i flashed blu spark twrp and im golden hope this helps
forty9er said:
I was having same issues so i flashed blu spark twrp and im golden hope this helps
Click to expand...
Click to collapse
The only twrp I have tried is blu_spark anyway.
Hello there!
Like said in the title, my phone keeps rebooting into recovery after I flashed the latest Pixel Experience rom.
Does anybody know a fix for this?
Thanks!
@latze97: what recovery did you use?
rp158 said:
@latze97: what recovery did you use?
Click to expand...
Click to collapse
I used TWRP 3.3.1-16.
I was able to fix the issue myself by going back to TWRP 3.3.1-3 via fastboot, flashing vbmeta and then installing the stock global rom.
But thank you for the reply anyway!
@latze97: TWRP has problems on Q, more than this reboot. SHRP is more stable.
rp158 said:
@latze97: TWRP has problems on Q, more than this reboot. SHRP is more stable.
Click to expand...
Click to collapse
Which version of SHRP would you recommend? I tried flashing the latest but instead of booting into the recovery it boots into fastboot...
@latze97: the latest, 200301. But that sounds witchy, not really better. There's an SHRP-update coming... If these bugs go on, format /data.
Hey, i'm having the exact same problem, where did you find this vbmeta file ? Link in the other thread is dead...
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://sourceforge.net/projects/resurrectionremix-ten/files/instantnoodlep/
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Changelog: https://get.resurrectionremix.com/ten/changelog/Changelog.txt
Be on OOS 10(both slots)(local upgrade last OOS 10 for slot b)
Flash twrp both slots(https://downloads.sourceforge.net/p...=cfhcable&r=https://forum.xda-developers.com/)
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
**UPDATE** this flash instructions work. I use these and ONLY these instructions. If you have a better way, good for you, but if you can't get it to boot, use these.
***UPDATE 2*** if you have installed Android 11 prior to installing this rom, you must msm back to OOS 10 and local upgrade OOS 10 again to slot b and only use Android 10 recovery
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
dladz said:
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
Click to expand...
Click to collapse
I've had no issues using latest twrp
jamescable said:
I've had no issues using latest twrp
Click to expand...
Click to collapse
Does it have oos cam?
areyouanand said:
Does it have oos cam?
Click to expand...
Click to collapse
Honestly, don't know. I don't use OOS can, but I don't think so
jamescable said:
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://get.resurrectionremix.com/?dir=ten/instantnoodlep
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Be on OOS
Flash twrp both slots
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
Click to expand...
Click to collapse
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Kollachi said:
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Click to expand...
Click to collapse
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
cultofluna said:
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
Click to expand...
Click to collapse
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
jamescable said:
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
Click to expand...
Click to collapse
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Kollachi said:
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Click to expand...
Click to collapse
[Mod Edit] Telegram link removed.
jamescable said:
[Mod Edit] Telegram link removed.
Click to expand...
Click to collapse
He is blind building from latest los source that's all. Respect him for doing that, but it's not 100% guarantee for a fully working rom.
jamescable said:
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
Click to expand...
Click to collapse
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. I think he meant to say reboot to recovery and not boot the twrp.img.
2. Yes you can boot twrp only. That's what im doing since OP7. But you will need to do this everytime you wanna flash something with twrp.
jamescable said:
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
Click to expand...
Click to collapse
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
cultofluna said:
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
Click to expand...
Click to collapse
It's in the pic I uploaded. Even the twrp dev said to flash it. So you won't have to fastboot boot anymore. Once you flash it. It's on your phone and won't go away when you reboot recovery
Every phone used to have a boot(kernel) partition, system partition, modem/radio partition, bootloader, userdata, and a few other INCLUDING recovery partition. Recently, the recovery was missing but now it's back. So we no longer have to have to boot twrp but flash it
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
oscarmaldonado said:
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
Click to expand...
Click to collapse
That is strange. I also have 2025. Try moving the rom to phone instead of usb device. Since this is an updated twrp may be an issue. However. I did NOT have OOS installed on both slots. I flashed latest OOS full rom, used OOS recovery to wipe data. Booted and then flashed twrp to both slots, flashed RR, reboot recovery and flashed magisk