Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
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
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