All I have access to is twrp 3.4 and the all in one tool. Through flashing I screwed up along the way. Can't say where @ this point but just need to make my phone stock again to start over. I've flashed factory OOS 10.3.3, 10.3.4. each time wiping data and dalvik. Re installed twrp 3.4 and magisk 20.4. I've tried flashing aosp roms as well. Had resurection remix installed and wanted to try and go back to OOS and flash renovate ice magisk mod and never got it to boot into 10.3.3 OOS. All that happens is it goes to bootloader unlocked screen and then black with vibration and reboots into twrp. I even have a rr back up and a stock backup that won't take either. This is all being done using an otg. Not familiar with adb on the laptop. I'm familiar with root, unlocking bootloader, and flashing things but from the nexus era. Things are a bit different now and I've been extensively reading and it seems each rom has its own method of flashing. wish I wouldn't have stopped with modding from years ago. Any help is greatly appreciated as I don't currently have a working phone
Format data. Phone will boot then.
Worked perfect, thanks!! Does that have to be formatted after any ROM install including backups? I've looked through the guides and other threads and there isn't a how to step by step explanation of how to flash new Roms or restore backups
Related
Hi,
Its been a while since I been attentive to my Pixel. I was a lucky one who managed to get a Verizon 7.1.2 with an unlocked bootloader. I unlocked the bootloader, flashed a ROM, and rooted and haven't had a single major problem since.
I was running Resurrection Remix from about March and I yesterday I wanted to try to use Android Pay, so I followed a tutorial I found in another thread here to install Magisk, and when it was all said and done I ended up in a boot loop where the phone would reset as soon as it reaches the Google logo, ramdump, and eventually boot back into TWRP.
In the attempts to delete out all kinds of caches and dalviks and factory resets and whatever else, nothing worked.
So in the end I decided to just flash a new ROM. Flashed the latest Pure Nexus, reflashed TWRP, flashed the vendor image... went to go reboot and it gives me the WARNING! NO OS INSTALLED! error. I thought that was odd and decided to just update to the latest Resurrection Remix - same problem.
At this point I am unsure what to do next. I don't care about any user data on the phone, I just want to get it back up and running with a new ROM.
I have a few questions and thank you in advance for all help you may be able to offer:
1) Why am I getting the NO OS INSTALLED issue directly after flashing a ROM? Logs indicate no errors whatsoever. /system/ is mounted. Every time I boot into TWRP it asks me if I want to Keep System partition read only. I always tell it to allow modifications and never ask me this question again - it asks every time. Is it possible that /system/ can actually remain empty even after a fresh ROM install that gives no errors in the log?
2) I believe that I am supposed to reflash to stock image that this phone shipped with to start all over. If I reflash back to stock, will my bootloader have any chance of locking again? I don't even know what version the stock image was, and I'm further confused/concerned about the fact that it was a 7.1.2 image I shipped with - from my understanding there were security updates which make unlocking/rooting impossible. I don't understand why you have to start that far back - is it even needed? The latest Resurrection Remix ROM install instructions assumes that I am on latest "Firmware" NOF26W. This is another issue I don't understand - what is a firmware? The full factory image? In any case, NOF26W is specifically for Rogers Google Pixel devices. Since I need to be on this "firmware" before I install latest, can I just flash the NOF26W Stock image despite the fact that I am using a rooted Verizon Pixel? The NOF26W image is 1.8GB: What exactly in this ZIP am I supposed to flash?
3) There were various weird things about this phone/flashing ROMs that I seem to recall such as having to boot an older TWRP before flashing ROM and then flashing the newer TWRP - is any of this stuff still relevant?
4) I also remember that many people were fastbooting TWRP rather than flashing TWRP for some reason - are there specific builds/non-standard stuff required for any of this to work on the Pixel?
I really appreciate all and any help that anybody can provide. If there's files that you're referring to, PLEASE send links. I need to get this phone back up and running ASAP.
Thanks again!!
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
rohitece06 said:
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
Click to expand...
Click to collapse
This. I just reboot anyway after seeing that message and I've never had any issues.
Hi, I have OP6 since day one. Unlocked, with blu_spark TWRP, rooted with Magisk. Didn't have any problems. Yesterday I decided to try some custom rom and I hit a wall. Can't make Wi-Fi working - tried NitrogenOS and ViperOS. As I don't have a lot of experience with A/B partitions I tried few step by step instructions I was able to find here. Tried with latest stable, latest beta, different versions of TWRP. Problem is not related to Magisk or Gapps - wifi is not working and can't do anything about it.
At my first try I forgot to reflash twrp and I lost access to internal memory (pin in twrp), so I flashed full stock (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and started from this - nothing.
Tried latest beta flashed through TWRP - same effect.
I tried to decrypt everything with dm-verity fix - everything is fine, except wifi.
I've done 10-15 attemps to flash everything since yesterday.
Can somebody write a step by step instruction how to flash something correctly, that's fight for honor at this point:fingers-crossed:? I have no idea what I am doing wrong or what I am missing I flashed plenty of phones and never had problems like this.
On stock(stable and beta) wi-fi is working like it should, olny custom roms are making a problem.
hinix said:
Hi, I have OP6 since day one. Unlocked, with blu_spark TWRP, rooted with Magisk. Didn't have any problems. Yesterday I decided to try some custom rom and I hit a wall. Can't make Wi-Fi working - tried NitrogenOS and ViperOS. As I don't have a lot of experience with A/B partitions I tried few step by step instructions I was able to find here. Tried with latest stable, latest beta, different versions of TWRP. Problem is not related to Magisk or Gapps - wifi is not working and can't do anything about it.
At my first try I forgot to reflash twrp and I lost access to internal memory (pin in twrp), so I flashed full stock (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and started from this - nothing.
Tried latest beta flashed through TWRP - same effect.
I tried to decrypt everything with dm-verity fix - everything is fine, except wifi.
I've done 10-15 attemps to flash everything since yesterday.
Can somebody write a step by step instruction how to flash something correctly, that's fight for honor at this point:fingers-crossed:? I have no idea what I am doing wrong or what I am missing I flashed plenty of phones and never had problems like this.
On stock(stable and beta) wi-fi is working like it should, olny custom roms are making a problem.
Click to expand...
Click to collapse
Use the unbrick tool. It will force write all your partitions.
tabletalker7 said:
Use the unbrick tool. It will force write all your partitions.
Click to expand...
Click to collapse
Last thing I did was flash-all-partitions.bat from image mentioned in my post. I gave up idea of custom rom for now. But I'll try unbrick tool on my next attempt.
Sent from my ONEPLUS A6003 using Tapatalk
i have the SAME problem, did you manage to fix this?
I'm not an idiot when it comes to TWRP/ROM flashing, like I've been doing it for many years, but this whole TWRP a/b thing has me confused and I seem to be doing SOMETHING wrong every time I go between AOSP/OOS. Let me explain.
Starting off on OOS, I did the instructions correctly for flashing Havoc.
Flash rom>twrp
reboot recovery
flash rom>twrp
reboot recovery
flash gapps
Then I decided I wanted to give OOS another try. (I wiped data/dalvik cache beforehand) So I flashed the stock twrp flashable zips in https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585 - [OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
And thus, bootloop. Stuck on the OOS boot animation. I remembered in the Havoc rom thread that it says to never wipe System/Vendor (even though it sounds weird to not wipe system if you're flashing another ROM, at least coming from my other phones). And figured maybe I should have wiped system when going back.
So I used the ALL-IN-ONE-TOOL to completely go back to stock, reinstalled twrp, all that jazz. Made a BACKUP this time of boot,system, and data. Went back to Havoc. Tried to restore the OOS backup, and now I'm just on a recovery bootloop and am currently using ALL-IN-ONE-TOOL to go all the way back to fully stock. Again.
What am I doing wrong?
In the amount of time it took you to write this thread, you could have read one of the many threads discussing how to take OTA. I see you did not once mention Magisk, which is most likely your problem. Read and follow guide here
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
schmeggy929 said:
In the amount of time it took you to write this thread, you could have read one of the many threads discussing how to take OTA. I see you did not once mention Magisk, which is most likely your problem. Read and follow guide here
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
Click to expand...
Click to collapse
..? I'm not having any issue with how to take an OTA or installing Magisk, that's prbably why you didn't see me mention them.
I'm talking about if I leave OOS and go to Havoc, and then try to go back to OOS whether its through flashing a backup or flashing stock OOS, then I get stuck in a bootloop.
rejectedjs said:
..? I'm not having any issue with how to take an OTA or installing Magisk, that's prbably why you didn't see me mention them.
I'm talking about if I leave OOS and go to Havoc, and then try to go back to OOS whether its through flashing a backup or flashing stock OOS, then I get stuck in a bootloop.
Click to expand...
Click to collapse
I gotcha now, when you flash a backup or stock OOS, are you retaining TWRP? Even with restoring a backup Magisk has be reinstalled. Now if you were on Havoc and went completely stock(with stock recovery) and boot looping , I would say something is messed up.
EDIT: Head back into HAVOC ROM thread and start from post 748 and read the responses. Your answer I believe is there.
Hi guys,
long time ago i've already been a Member to XDA Community. HTC Wildfire was a brand new phone at that time. In the mean time i've switched to a Oneplus 2 running Lineage OS 17.1 and two years ago i got a Oneplus 6 running stock ROM till yesterday.
Yesterday i got Lineage OS with Wifi up and running fine with the official guide and official lineage recovery but forgot to flash OpenGapps in the first try. Tried flashing it again but got a Qualcomm Crashdump Mode Error after that.
So i went on to reflash the whole phone with clearing storage, system and so on. Flashed again now with OpenGapps and Magisk with reboot to recovery method described in official installation guide, Lineage was booting fine and tried to search for Wifi-Connection but i wasn't able to see any Wifi at all. I finished the setup and tried again in settings but System UI crashes if i try that. Rebooted, cleared Cache and tried again but nothing.
So i went back to full stock 10.3.0 with MSMDownloadTool but it only flashes partition a? Is that correct?
After a lot of trying different things got back to 10.3.5 on a and b partition with mauronofrios stock fastboot roms from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 (Thank you very much for that! :good: ). I can boot both slots if i switch them in booted twrp without any problem.
On stock everything works fine my wifi detects all available networks and i can connect to them without problems.
What did i do wrong?
Any help would be appreciated.
Thank you!
Schwaus
EDIT:
So i did a little bit more testing:
Installed lineage-17.1-20200804-nightly-enchilada-signed.zip with corresponding recovery without anything like Gapps or Magisk both like described in official instruction and with TWRP from mauronofrio. I also tried to flash latest official OTA from Oneplus via TWRP before flashing Lineageos. In neither of the tested ways Wifi is working and i cant see any Wifi-MAC-adress under settings. Also tried to switch back to stock before flashing with flash-all-partitions.bat from mauronofrios stock to get the persist partitions replaced too.
Every version of Stock like the MSMDownloadtool 10.3.0 or Stock 10.3.5 from mauronofrio Wifi works perfectly without problems. I also can update via OTA without issues. I just dont know what is happening with my Wifi firmware when flashing LineageOS.
EDIT 2:
Got the problem fixed:
Don't know if i done it right but maybe it helps someone.
In my case it was a combination of problems:
- First the latest Oneplus 6 Lineage releases (20200804 and the withdrawn 20200811) seem to have a bug when installed fresh on a device to cause a bootloop so i used the one from 30/06/2020 and updated with the app afterwards.
- Secondly the copy-partitions.zip script hasn't copied all of the partitions necessary. In mauronofrio's fastboot image there is a image named fw_4u1ea.img. This one got not copied by the script, so i booted twrp-3.4.0-1-enchilada-Q-mauronofrio.img and flashed all of the images (fastboot, persist and critical) to slot b again manually like described in his thread. The flash-all-partitions.bat has not worked either.
Now LineageOS works like a charm and i can see and connect to every wifi.
Hey mate. I had the same issue and I gave up at this point. Tomorrow I'll try your "EDIT 2:" and gonna leave a feedback
Hey Schwaus, thanks for this post. *EDIT 2* worked for me
hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.