Lineage OS install problems - HTC 10 Questions & Answers

So, I think I had all my bases covered to install lineage OS.
I unlocked bootloaders from htcdev
I turned S-off with sunshine
I installed twrp
I didn't seem to have any issues doing these (installed root during)
But when I go to install the latest lineage os from twrp, then gaps it seems to work fine. I wipe cache then reboot.
When I reboot it gets stuck in a loop at the android logo where it shines back and forth.
I checked my download screen and it says OS-1.80.651.30, which I understand is android 6. Lineage is 7, is that where the hangup is... if so what do I do to fix that? In my previous rom experiences I just flashed the zip and was good.
I feel like I'm missing a step or missed something. Any help would be appreciated. Thanks!

Well in general it is always better if your firmware matches the ROMs base to make sure everything is working as expected. There are some ROMs booting on MM firmware and even fingerprint scanner works on them due to modifications by their developers. Best would be to ask if you need a more recent firmware - and if so which one - on the respective ROM thread.
A second possibility could be the TWRP version you're using. To flash N ROMs successfully make sure you got TWRP 3.0.3-0 unofficial installed. If not head over to the TWRP thread and get it from download tab.
I always try to run the latest firmware just to make sure.
Sent from my htc_pmeuhl using XDA Labs

Related

Root not working on m9 with twrp 2.8.7.0 using chainfire, need help.

I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Jerry060599 said:
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Click to expand...
Click to collapse
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
LLegion said:
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
Click to expand...
Click to collapse
tks for the help . will be trying it out.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
LLegion said:
Of u still have issues i can give whatsapp and help you with further assistance
Click to expand...
Click to collapse
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
Jerry060599 said:
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Click to expand...
Click to collapse
Look at post 3 in this thread. Best is you read all information in the first three posts.
Here u havebaccess to my personal folderhttps://drive.google.com/folderview?id=0B--58xBx8PTOfmYyeDdXeFJ1ZnRSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg&usp=sharing
Flippy498 said:
Look at post 3 in this thread. Best is you read all information in the first three posts.
Click to expand...
Click to collapse
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Jerry060599 said:
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Click to expand...
Click to collapse
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
dragonesdenano said:
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
Click to expand...
Click to collapse
Sorry for the (extremly) late reply. I had not been home for the past week. I tried restoring to stock system image and flashin su binaries before. It didnt work. At this point, I suspect that the only reason why I can't flash supersu is because of my firmware version. So I'll be wimpering in a corner untill some kind devs at htc decide to release the source for my version.

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol

Nexus 7 on 4.4.2 - how do I get to 7.1

Hey guys,
I have a Nexus 7 that is stock and on 4.4.2. When I bought it all I did was run Towel root to get root and I have not taken an update in all these years. I also installed an app to unlock bootloader. I am even still on stock recovery.
I'd like to go to 7.1 now. What is the easiest way for me to do this right now? Please include all steps as I do not have a ton of experience with this.
Thanks in advance!
I apologize if I maybe my question was too broad. Can i go directly from 4.4.2 to 7.1 or do I have to upgrade to something else first.
Can i leave the tablet rooted with towel root or do I have to unroot first?
Thanks
http://forum.xda-developers.com/showthread.php?t=2382051
You should read and watch some basics to understand what
you have to do.
In short: unlock bootloader, flash latest factory image or latest bootloader and radio, flash twrp and then 7.1 rom of your choice
Thanks for the link, I appreciate it.
I'd like to try and just go straight from 4.4.2 to 7.1 if that is possible. I now went ahead and installed TWRP on the tablet. This went fine and TWRP seems to be working perfectly.
So now I have unlocked bootloader, SU working, TWRP and I'm still on 4.4.2. What is now the easiest way for me to get 7.1?
^He was just saying you need the latest bootloader. To get that you can flash the latest factory image or just the bootloader.img itself (and radio if you have the mobile version). Latest is 4.08
Either way download the latest factory image and on your tablet download the rom and gapps you wan't. We can only fit the smaller gapps read about it in your roms thread.
I'm assuming you're familiar with fastboot, if not there are many, many guides all over xda and the internet.
Drag and drop the bootloader.img in the factory zip into your fastboot folder and with the tablet booted to the bootloader run this:
Code:
fastboot flash bootloader bootloaderfilename.img
fastboot reboot-bootloader
The file name for flo is bootloader-flo-flo-04.08.img
(your kitkat rom will most likely not boot with the newer bootloader but you don't need to)
Use the volume buttons to select recovery and press power to boot twrp.
Now just wipe the tablet (not internal storage) and flash the rom and gapps. That's it. Reboot.
Ok, i really appreciate your help folks. I think im getting closer to understanding what I need to do.
Yosmokinman, where can i get the 4.08 bootloader img?
Also, you mentioned radio if I have the mobile version. What do you mean by this? My tablet is wifi only?
When i flash the rom and gapps do i do that from twrp? Can i flash both at same time one after the other or do i have to do something in between?
When i reboot will i have to reinstall all my apps, photos, files, etc. Or will they still be there?
Sorry for all the questions, Im hoping to not make any mistakes. I love my little Nexus and dont want to hurt it :good: thanks very much once again!
yosmokinman said:
^He was just saying you need the latest bootloader. To get that you can flash the latest factory image or just the bootloader.img itself (and radio if you have the mobile version). Latest is 4.08
Either way download the latest factory image and on your tablet download the rom and gapps you wan't. We can only fit the smaller gapps read about it in your roms thread.
I'm assuming you're familiar with fastboot, if not there are many, many guides all over xda and the internet.
Drag and drop the bootloader.img in the factory zip into your fastboot folder and with the tablet booted to the bootloader run this:
Code:
fastboot flash bootloader bootloaderfilename.img
fastboot reboot-bootloader
The file name for flo is bootloader-flo-flo-04.08.img
(your kitkat rom will most likely not boot with the newer bootloader but you don't need to)
Use the volume buttons to select recovery and press power to boot twrp.
Now just wipe the tablet (not internal storage) and flash the rom and gapps. That's it. Reboot.
Click to expand...
Click to collapse
^ Factory Images for Nexus and Pixel Devices
wifi only N7 is not the mobile version so forget about the radio. You're looking for "razor" on the images page.
Yes the wiping and rom/gapps flashing is done through twrp and you should be flashing rom then gapps one after the other then hit reboot.
Everything will be gone but your internal storage. You'll have to redownload and setup everything. Don't worry about hurting the tablet you can recover from pretty much any problem with the factory image.
yosmokinman, ok I am getting ready to do this! Thank you again.
So I found the 4.08 bootloader thanks to your link. I think I am just going to go with latest Cyanogenmod 7.1 snapshot. If I understand correctly I will be using opengapps ARM 7.1 Pico.
Does above seem correct?
Also, what about my kernel, I am still on the stock/original kernel (I believe 3.4.0-gac9222c#1) from back when I originally got the tablet new. Does that just stay the same?
Finally, you mentioned that as long as I have a factory image I should be good if I run into any problems. Do you mean a factory image that I can download (from where?)? or do you mean an actual image from my tablet? As of now I have never made an image of mine (not sure how I would do that).
I can almost taste that Nougat now
Thanks again!
treepog said:
yosmokinman, ok I am getting ready to do this! Thank you again.
So I found the 4.08 bootloader thanks to your link. I think I am just going to go with latest Cyanogenmod 7.1 snapshot. If I understand correctly I will be using opengapps ARM 7.1 Pico.
Does above seem correct?
Also, what about my kernel, I am still on the stock/original kernel (I believe 3.4.0-gac9222c#1) from back when I originally got the tablet new. Does that just stay the same?
Finally, you mentioned that as long as I have a factory image I should be good if I run into any problems. Do you mean a factory image that I can download (from where?)? or do you mean an actual image from my tablet? As of now I have never made an image of mine (not sure how I would do that).
I can almost taste that Nougat now
Thanks again!
Click to expand...
Click to collapse
When you flash the ROM, you'll get a new kernel. All of that is wiped when you wipe system from TWRP. Then when you flash the ROM from TWRP, you'll get a new system and the kernel and all else.
Sound fine. Except there is no nougat snapshot (thats cm13 marshmallow) you wan't Cyanogenmod 14.1 nightly.
If you downloaded the latest image for razor from that link above that is the factory image. If you look in the zip there is another zip that has the different partition images.
You said your N7 is the wifi only version so make sure the bootloaders file name is "bootloader-flo-flo-04.08.img" don't flash the wrong one.
Ok, thanks again. I will report back once I do it. Thank you so much!
Ok, I finally had a chance to do this today. I decided to go with CM android 6 instead of 7 because I really want something that is totally stable. When I got the factory image I saw it only goes up to android 6 and since I was getting the bootloader from 6 (4.08 bootloader) I figured just stick with 6.
If I wanted to upgrade to CM 7 or 7.1 would the 4.08 bootloader still be correct??
Anyway, it is like I have a brand new tablet. Running great!
THANKS SO MUCH FOR THE HELP!!!
I'm running stock MM with the Nova launcher. Aside from the intermittent sensor issues, it's still a remarkably smooth tablet.

TWRP: "No OS installed" + ADB Sideload "e3004", need help

Hi all,
I posted this also on OnePlus forum but posting this here also since I'm quite near panicking here.
So the long story short: I rooted my 5T earlier today and now I needed to restore everything back to stock and locked. Everything went rather well until it was time to install the official OnePlus build before the bootloader locking. I downloaded it and copied the most recent Build from OnePlus website to my phone, booted to TWRP and started the TWRP advanced wipe. But so it happened that stupid me also wiped the Data section along with the Dalvik/ART Cache, System, Boot, and Cache sections. So I don't have that ROM package on my phone anymore.
Well, I found this ADB Sideload feature so I decided to give it a try. The problem is that when I try to transfer the ROM from my computer to my phone I get the error "e3004: this package is for oneplus 5t devices this is a oneplus 5". And yes, my phone is the 5t so this doesn't make any sense to me.
Please tell me that I have some options left to try out.
Using TWRP 3.3.1.0 cheeseburger and Magisk 19.3
EDIT
I just realized that I have installed a wrong version of the TWRP. So, how can I install a correct version?
EDIT#2
Installed correct version of TWRP (the dumpling one). Didn't help
Rvnheart said:
Hi all,
I posted this also on OnePlus forum but posting this here also since I'm quite near panicking here.
So the long story short: I rooted my 5T earlier today and now I needed to restore everything back to stock and locked. Everything went rather well until it was time to install the official OnePlus build before the bootloader locking. I downloaded it and copied the most recent Build from OnePlus website to my phone, booted to TWRP and started the TWRP advanced wipe. But so it happened that stupid me also wiped the Data section along with the Dalvik/ART Cache, System, Boot, and Cache sections. So I don't have that ROM package on my phone anymore.
Well, I found this ADB Sideload feature so I decided to give it a try. The problem is that when I try to transfer the ROM from my computer to my phone I get the error "e3004: this package is for oneplus 5t devices this is a oneplus 5". And yes, my phone is the 5t so this doesn't make any sense to me.
Please tell me that I have some options left to try out.
Using TWRP 3.3.1.0 cheeseburger and Magisk 19.3
EDIT
I just realized that I have installed a wrong version of the TWRP. So, how can I install a correct version?
EDIT#2
Installed correct version of TWRP (the dumpling one). Didn't help
Click to expand...
Click to collapse
Then what happened? Are you sure ,you downloaded full ROM zip?
surya nivas said:
Then what happened? Are you sure ,you downloaded full ROM zip?
Click to expand...
Click to collapse
Still can't install OS via Side load due the same error. And when I use Mount in TWRP my phone is recognized as OnePlus 5 in Windows 10.
I downloaded OS 3 times but no difference.
Next I'll try Full Wipe in TWRP if that helps. If anyone got any other suggestions feel free to share 'em. I'll try those also when I got a change, thank you.
Your TWRP must be for 5T maybe?
Install this TWRP: https://github.com/engstk/android_d...-3.3.1-x_blu_spark_v9.101_treble-op5_op5t.img
Make sure you have the full firmware and not the OTA: https://androidfilehost.com/?fid=6006931924117890018
You should be able to flash the firmware through TWRP by placing it in root storage.
Okay, so the phone is up and running again. It took me awhile because I was away and had no change to try out any solutions.
Thank you everyone for your responses!
If anyone ever have the same problem here is the situation in a nutshell:
- I rooted the phone but accidentally installed wrong version (OnePlus 5 version) of the TWRP
- Everything actually worked until I wanted to lock the phone again
- After I wiped the phone in order to install stock ROM I couldn't install any ROM because of the wrong TWRP which made the hone think it is a OnePlus 5 and not the 5T
- I installed the correct version of the TWRP but it didn't help
- What I needed to do was a full wipe first and then install the correct TWRP
- Then I was able to use the Side Load to get the ROM to the phone
Im not saying tis will work but I had a similar hing happen with a magisk file..i finally just renamed the file to something simple like my name.zip......went right on there with no error message

Question Standard oxygen OS or magisk and lineage ROM?

What you guys recommend better option I'm torn between oxy or lineage ROM with magisk for one plus 9 pro. Lmk thoughts Ty.
I used lineage for awhile and can say that battery life will be better, device will perform well, and background apps are more reliable, but I just prefer other ROMs over lineage, it's too basic in terms of customization and OOS is better in some ways. You'll give up the OnePlus camera app and it's optimizations and post-processing. If you're okay using gcam instead of OnePlus cam, then lineage is ok, but I'd recommend crDroid over it most definitely. Its equally stable but felt snappier and more complete feature set in my use. Plus the maintainer updates frequently and does a good job.
Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .
Anonymous-Ciphers said:
Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .
Click to expand...
Click to collapse
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps
thats_the_guy said:
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps
Click to expand...
Click to collapse
Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help
I return to OOS from Lineage OS last month, after using Lineage for a long time. Just because camera on Lineage just can't fit my needs. I tried Google Camera, but there are some bugs and still OOS camera is the best.
Anonymous-Ciphers said:
Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help
Click to expand...
Click to collapse
Haven't seen a no touch issue before. Well I'd try another factory reset inside TWRP and flash again, I believe 9 and 9 pro are unified for cr but also make sure you got the right zip. If that doesn't work, OOS 11.2.7 is the newest full zip file you can download from OnePlus, maybe try flashing that, and try installing crDroid without updating to 11.2.8 or 11.2.9. If that doesn't work, might be at a loss.
How come twrp I can't get going

Categories

Resources