Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Try restoring through the msm tool.
TheRemyx said:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Click to expand...
Click to collapse
Have you wiped the cache?
It's not a hardware issue.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
Scott said:
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
Click to expand...
Click to collapse
Thanks guys. Using MSM worked.
For those who may have the same issue, I used MSM to go back to 9.0.11 since a few people said they had issues with 9.0.12 such as not being able to unlock it. I restored 9.0.11, unlocked my device, then flashed the 9.0.12 OTA. Issue stayed resolved.
I did try to flash Omnirom again and the issue came back, so I'm curious as to what's happening. I'm going to try another Rom.
Just an update, this seems to happen with any rom I flash now. I tried Omnirom, Pixel Experience, and Syberia OS. They boot up but with no 4g connection. When I use MSM to go back to 9.0.11 or 9.0.12 everything works properly. Not sure what I may be missing?
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
dj_ooms said:
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
Click to expand...
Click to collapse
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
dj_ooms said:
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
Click to expand...
Click to collapse
I had tried flashing GAPPs (ARM64-Nano) and it didn't seem to make a difference. I was skipping that and flashing Magisk just to confirm if I had service first. But would service/signal be dependent on something in GAPPs? I may try your way. I hadn't run into any issues with encrypted storage lately. The last few times I was able to get around it by booting to system first, then rebooting back to recovery.
schmeggy929 said:
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
Click to expand...
Click to collapse
I was installing TWRP because every time I restored or flashed, I was losing my custom recovery.
Related
I'm having a very difficult time getting this phone setup. I can get very, very close... but then it starts boot looping into recovery.
So starting at the beginning, here is what I did:
- Booted up phone, make sure it works and connects to wifi (I find out later that it got encrypted, even though I didn't set a PIN).
- Inside the OS on first boot, I install and use the official bootloader unlock APK from Asus.
- Rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the Oreo modem, current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After many attempts to decrypt (and a lot of help from the forum), I successfully restore the phone to "WW_ZE552KL_14.2020.1712.85_M3.10.47.15_Phone-user.raw.zip" with the Asus tool.
- Phone is fixed and booting again to the OS, but I'm back to square one.
Second attempt:
- Thinking I need to flash the raw Oreo ROM (instead of just the Oreo modem), I use the Asus tool to flash "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw.zip"
- The phone works fine and is now an Oreo ROM with an Oreo modem
- It's still unlocked, so I rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After the reboot, it goes to TWRP... whether I just let it boot on its own, or press power when it says: Start - Continue to boot >
What am I doing wrong?
You're having a rough go at this one eh.
I know we talked about this before, but did you try a factory reset and wiping cache/dalvik before rebooting?
Yes. As we discussed before, you can't wipe cache from TWRP. So I'd wipe dalvik from TWRP, then reboot to the bootloader to do a "fastboot format cache".
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Flapjack said:
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Click to expand...
Click to collapse
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
junglesnake said:
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
Click to expand...
Click to collapse
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
BootloaderBoi said:
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
Click to expand...
Click to collapse
many many thanks! I was able to get Ressurection Remix working by now
your steps were right, and I will detail them better to tell how I made it work for others reading this thread:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website.
1.2 - I also had to find a recent recovery.img, which I think I got it from here https://forum.xda-developers.com/zenfone-3/how-to/original-recovery-img-boot-img-zenfone-t3572188
1.3 - I used the stock recovery's adb sideload to flash the stock ROM
2) Flash TWRP - all good here
3) Flash ROM, Magisk, GApps
3.1 - I wiped system, data, cache and dalvik.
3.2 - I flashed RR ROM, GApps and Magisk (EDIT 2: install all three before the first custom ROM boot, or GApps won't work)
3.3 - Performed a Factory Reset
4) REBOOTED TO GLORY!
For what it seems, the stock ROM encryption that is performed on the stock's first boot was the enemy.
Now one last thing... In Security -> Encription, my device is NOT encrypted.
Do I run the risk of ruining everything if I encrypt it?
EDIT: No, it didn't break, working fine
junglesnake said:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website
Click to expand...
Click to collapse
lmao. His RAW firmware version is the latest version though
https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456
Anyways, enjoy your phone running on custom ROM :good:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
devam1995 said:
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
Click to expand...
Click to collapse
How do you do that using the terminal? I tried following this topic https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 but I got this error
https://imgur.com/wy1immW
TWRP still can't flash OOS
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
Flash a patched
Code:
boot.img
when I got the problem, I did that and it worked, booted me to system but if that doesn't work then you have to flash Magisk.
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
This phone has A/B partitions and is able to store a backup version of the OS so if a new installed version doesn't boot it will revert back to the old one.
When Flashing, you need to flash "BOTH" slots.
If you used the MSM tool to boot, you just booted and not flashed.
The MSM tool will flash your phone, restore the stock recovery and relic the bootloader. It will look like it came out of the box.
I don't know how to get you from wrapped around the axle except to tell you to run the MSM tool and let it wipe the phone and get you back to stock. You can then unlock the BL again and install TWRP, etc if you like.
twistingthai said:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Click to expand...
Click to collapse
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
parker.stephens said:
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
Click to expand...
Click to collapse
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
twistingthai said:
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
Click to expand...
Click to collapse
Glad to help. I was sick of having to put the device into Qualcomm mode just to get it to boot up, then I decided to try reformatting data and it worked.
Hello,
this is my first time installing a custom ROM, so a want to ask if I can use the original lineage instructions from their website for installing the https://forum.xda-developers.com/oneplus-6t/development/rom-lineageos-16-0-t3897334 ROM on my new 6T.
Do I have to take care of something special, are there differences in the installing process?
Better asking before then......
Thanks!
I haven't tried Lineage OS. I believe it is based on AOSP. I am currently running HavocOS which is also based on AOSP. Practically all custom ROMs I have tried have required ensuring a stable version of OOS has been flashed to both slots before installing the custom ROM and then GApps. I would recommend reading a thread from a few custom ROMs to familiarise yourself with the process as I believe it should be the some process for most. I would also recommend backing up your internal storage beforehand as there may be a chance that you'll need to format your internal storage to get around encryption issues. In some cases I have had the phone reboot back into TWRP constantly if the storage wasn't wiped first.
Due to the differences in encryption, here is the way I always install AOSP when bouncing back and forth between OOS and AOSP. I haven't tried not formatting data in a while, so it may work without these days, but it didn't use to.
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps.
- Flash Magisk.
- Reboot to system.
- No loss of data, or anything.
OhioYJ said:
Due to the differences in encryption, here is the way I always install AOSP when bouncing back and forth between OOS and AOSP. I haven't tried not formatting data in a while, so it may work without these days, but it didn't use to.
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, for updates, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, for updates, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, for updates, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps.
- Flash Magisk.
- Reboot to system.
- No loss of data, or anything.
Click to expand...
Click to collapse
Thank you for your answer, everthing worked fine for me installing Lineage, I did it exact the way you posted.
This double flash confused me at the beginning but as you described you have to do it just once.
So, thanks a lot and sorry for my late answer.
KKF32 said:
Thank you for your answer, everthing worked fine for me installing Lineage, I did it exact the way you posted.
This double flash confused me at the beginning but as you described you have to do it just once.
So, thanks a lot and sorry for my late answer.
Click to expand...
Click to collapse
Glad it worked out for you. The A/B slots are new to a lot of people still. The biggest thing to remember is when you flash a ROM you are flashing to the opposite slot. So if you are on Slot A and you flash a ROM, you are flashing Slot B. When you reboot to recovery it will switch to Slot B so you can install Gapps, Magisk, etc. to Slot B where your new ROM is installed. (Gapps, Magisk etc, flash to the current slot, not the opposite slot. )
From 6T (purchased from oneplus.com), any time I follow the instructions for how to flash one of the custom ROMs, I get stuck at the bootloader with no working rom.
I was able to use the MSMTool to restore to 9.0.13. I upgraded a few times flashing OnePlus6TOxygen_34_OTA_024_all_1909112343_9fd6e0057b8747dc, which works, but when I try to flash a custom ROM, I cannot get past the bootloader. I say a few times because I've tried this for a few days now with no success.
Most recently, I used the Flash-all.bat inside 10.3.0-OnePlus6TOxygen_34_OTA_042_all_1912142031_d9ef3-FASTBOOT
I am currently on 10.3.0, with twrp-3.3.1-31-fajita-Q-mauronofrio installed using the fastboot flash boot_a twrp-3.3.1-31-fajita-Q-mauronofrio.img then fastboot boottwrp-3.3.1-31-fajita-Q-mauronofrio.img commands from fastboot.
I can then install Magisk 19.4 or 20.3, however again when I try to flash a custom ROM, I cannot get past the bootloader.
What am I doing wrong?
When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?
Striatum_bdr said:
When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?
Click to expand...
Click to collapse
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?
s7itch3s said:
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?
Click to expand...
Click to collapse
I don't know I don't flash custom ROMs anymore, too old for that stuff and need my time for me.
There are specific instructions for each custom ROM it's better to ask in dedicated threads, some of them need to have OOS in both slots before, some of them need to be fleshed in both slots. Normally you eventually wipe things, flash the ROM and twrp to keep it, then reboot to twrp (necessary to boot on the slot where the ROM is actually fleshed, which is always the non active slot, which become the new active slot) and flash Gapps and Magisk ( because Gapps and Magisk can be flashed only in active slot) then reboot system
s7itch3s said:
Am I performing these steps correctly?
Click to expand...
Click to collapse
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?
Advised Sloth said:
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?
Click to expand...
Click to collapse
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.
OhioYJ said:
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.
Click to expand...
Click to collapse
First of all, thank you very much for your time and explanation.
Sir, so i will proceed as follows:
* Boot into TWRP Recovery
* Perform "swipe to factory reset" & "swipe to wipe data"
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot A
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot B
* Reboot to system
Sir, please check are my steps correct? If not,
From which step( steps mentioned in your guide) should i start?
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Very sorry for knocking you repeatedly!!!
Advised Sloth said:
First of all, thank you very much for your time and explanation.
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Click to expand...
Click to collapse
Your starting point is correct. However make sure you don't miss the re-install TWRP after flashing Lineage each time, and the second time you need to flash Gapps before you reboot to system.
Personally I always do Nano. Anything else you need (that would be included in Micro) can be installed from the Play store. Nano at least includes all the things that can't be installed from the play store.
Pico has the least in it. TV is for TV devices. On OpenGapps there is a box next to each package you can click and it will tell you exactly what is in each package.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sorry for the necropost, but this also works for TWRP 3.6 and Lineage 18.1. I initially had a problem with the default TWRP for my 6t. During the initial TWRP fastboot the version on their site caused a firmware error which I could just barely get out of, but it screwed up the system boot process in some subtle way that even the fixed version of TWRP (found on this site) couldn't solve.
After trying your instructions above, it didn't work the first time because of the screwed up system boot. It just kept trying to boot to recovery. I suspected a firmware error and was almost going to do an mcmdownload soft-brick rescue. I tried one last thing, using the TWRP on the system to sideload the stock ROM. That worked and patched up the system boot process. Once I booted and ran through some basic initialization to make sure developer options were properly set I followed the above instructions and it worked nearly flawlessly.
One strange thing. After I installed Lineage 18.1 and TWRP to both partitions (as well as Gapps / magisk), it rebooted to system and almost booted without incident -- except a large circular logo popped up that said 100% and stopped. I figured that that meant someting completed properly, so I powered off, waited 10 seconds, powered on and then the Lineage green system initialization spinner came up for a few minutes and it went through the user initialization sequence.
Thanks. I almost gave up and bought a new phone.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
OhioYJ, these are great instructions but it initially left me with questions about how that procedures would create duplicate installs on slot A and B. The answer is of course that the Lineage installer for the 6t knows about the dual slot setup and always writes to the inactive slot. Booting into recovery activates the inactive slot so that installing again after that installs to the other slot and now you have Lineage on both slots. The installer for TWRP always installs to both slots and is needed because Lineage always installs its recovery handler and you don't want that so you overwrite.
PS: TWRP has an option for installing itself after installing the requested package. Would that be just as good as installing the TWRP zip?
PPS: I had to do an 'adb push' of the Lineage and TWRP zips to sdcard for the installs. Unfortunately installing and slot switching makes the sdcard unavailable so you have to push the zips again. Is there somewhere I can write them to that I don't lose access to after a boot to recovery?
Hello,
I do have some questions about upgrading LOS from 16 to 17, maybe someone can help me bringing a little light into this upgrading process.
- Is the sideload way the correct way to do this? ( https:// wiki.lineageos.org /devices /fajita /upgrade)
- What´s about the play services, I dont have any installed ( ..."If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them"...) So if later on I want to install e.g. opengapps I have to wipe all my data after upgrading to 17??? (How? TWRP - wipe -advanced wipe - data and cache ???)
and what´s with all may data? I have titanium backup pro (no SD card), so I backup may phone, put it to my PC, upgrade to 17, wipe all data, put the backup back to phone and reboot?
Or do I have to install Magisk.zip and titanium.zip from within TWRP again first
- What do I do if the sideload fails?
- Can I do the upgrad process with TWRP too? (copying and installing from within TWRP?)
- And what about with the A/B slots, no installing twice on both slots?
As you see, I am unsure on how to do things right and I only did this once before as I installed Lineage OS.
(This would be the way I would do this:
- backup all data to PC
- Boot into TWRP
- copy LOS17.zip. Magisk.zip and Titaniumbackup-pro.zip into internal storage
- install LOS17 and boot into TWRP
- wipe data and cache
- install magisk and TB
- copy all data back and restore? (only user data or the system data too??))
Maybe someone can help me with this. Thanks!
My guide for installing Lineage maybe helpful: Guide Installing Lineage
I would recommend a clean install. Most that have tried to follow that wiki have had issues (if you look in the LOS thread). I haven't used. TB zip, but I did use my TB data from the app without issues. If you dont use Gapps, just dont install them. Skip that step. You still have to reboot to recovery to install Magisk though. I dont think I would try a TB zip until after the first boot.
Installing twice is for the intial install to get the same thing on both slots. You dont want Android 9 on one slot and Android 10 on another, or LOS 17 on one and OOS on another. Once you have LOS 17 on both slots and go to update you will just flash once. See my guide about doing an update.
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
KKF32 said:
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
Click to expand...
Click to collapse
How did it go?
badpanda said:
How did it go?
Click to expand...
Click to collapse
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
So I thought maybe the "no factory reset" at the beginning may caused this problem, so I started the whole flashing again.
Long story short: Being distracted I once forgt to flash TWRP after the LOS and now I am stuck in fastboot.
Cant get anymore into TWRP, "fastboot boot TWRP.img" always throws me into fastboot forever wait
Tried to flash TWRP direct from fastboot "fastboot flash recovery twrp.img", always get a write error.
So, at the moment all I can get in is the bootloader, and I have no clou how to get TWRP up and running again.
Edit: Managed to get into TWRP again, but this double flash + Magisk always gives me this "Qualcomm Crashdump Mode"
Help would very much appreciated!
KKF32 said:
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
Click to expand...
Click to collapse
So you tried to go straight to LOS 17, used an old version of TWRP, and never wiped data while going between Android 9 and 10? None of that will work. I think didn't make it clear, you need you need to be on the OOS 10 firmware first. Flash OOS 10 to both slots, at this point using the fastboot ROM would be my suggestion, like my [Guide]Installing Lineage.
Once you have Android 10 in place one both slots, then start your OS 17 install. Note there is a cliff notes version of that guide in the second post, if you don't want all the "wordy" details.
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
KKF32 said:
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
Click to expand...
Click to collapse
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
OhioYJ said:
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
Click to expand...
Click to collapse
So, LOS17 is up and running, I did it the long way but good to know the fastboot Rom method now. I confess some part of this thread would not have been necessary if had read your installations instruction carefully....
So let me thank you for patience und help, "Reading broadens the mind", I often tell others, will remind myself nexttime