Database Users

Nexus 10 (Manta) Help Thread - Ask Your Questions Here!

Samsung/Google Nexus 10 Help Thread!
mantaray​
Welcome to the Nexus 10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. For a list of supporters, see here:
Current List of Supporters@demkantor - All Things Nexus - adb & fastboot expert!
@lj50036 - GitHub Expert and All Around Android Guy!
@rirozizo - Battery Guru and Android Know It All!
@XxLordxX - The Unbricker!​
Click to expand...
Click to collapse
Supporters: If you want to be put on or off the list, just send me a PM!
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @ like above. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible for posting there, you may post here. And Please Read The 2nd & 3rd Post Of This Thread Before Posting! Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette

Knowledge is Power!
This section is not meant to offend but rather inform XDA members, please read, understand and abide by what is said in this post... you will never be called a n00b if you do!
First Read This:
~~~~This alone will save you - thanks Tony Stark~~~~
How to post your problem or question
This isn't really complicated but the more you know the more likely you can find your own answer.
But we are here to help! So the more information you give us, the better/faster we may help you!
Step One
Have you searched for the answer to your problem/question?
If not do this first, both the search button in the XDA forums and Google work wonders.
At least attempt to show you did a little research before you scream help or this ROM is garbage, Not searching or just simply complaining will get you ignored EVEN IF YOU WRITE IN ALL CAPS
All questions belong in Q&A Forum All General Phone discussion in General NEVER post random problems in Developers section
Step Two
So you have searched for your answer and can't find it, that's okay, it happens to all of us. But before you create a new thread seek out a similar one (in the proper forum for you device) and ask there - or here.
You may think a new thread is better but in truth people look at the old ones just as much, and keeping all similar questions in one thread helps to elevate congestion and makes the next guys search a ton easier.
Step Three
Know what to post. This means explain your problem as best you can (dont write a book, just not "help my phone is possessed by demons" this is not helpful)
So this means explain all about your phone, boot into your bootloader and write down all from that screen within your post. Are you rooted? Explain where your troubles began and what you have tried to do to fix it.
Give details as much as possible, this often will include a logcat. Which there are many ways to get, learn how to before you have a problem.
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
Code:
cat /proc/last_kmsg
Also read THIS or maybe try THIS
Use pastebin or codewraps around your logcat ( # sign from above)
Obviously every problem and question will require different information, but the more you give the better chance someone can help you.
Step Four
Wait for your answer, do not post the same question in ten threads, one will do. While you are waiting keep searching for your own answer.
When someone gives you help say thank you (with the thanks button preferably - don't make a post that just says thanks... nope, never)
Even if you don't like the answer be grateful someone took time from their day to try and help, If you think it's bad advice maybe reiterate your question and politely ask for a clearer or better explanation to the solution.
Once you have an answer
Edit first post to add the fix. If there was no fix maybe explain why there is no fix in first post.
This will help others searching for a similar problem later. Make sure your helper was thanked as well.
*Remember ROMs, Kernels, etc, may be posted in the developer section, basic questions shouldn't be in those threads. If you must add something, like a bug report, be sure to add a logcat or you man not be helped.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Again, please understand that no one here is paid, we are here to learn and we help for fun. so please be respectful...

Quick Tips!
Okay, so if you look through the Q&A thread here the number one issue that keeps popping up is "Help Bootloop!" and "Help I Think it's Bricked!"
So here is a quick guide that will most often fix these issue (90% of the time anyway)
First things first.... Drivers
Now many of you have these installed, so if you can connect your device to PC through USB and are able to communicate with adb and fastboot just skip this.
If however you can not, then you need to download appropriate drivers for Windows.
You can get these through the Adroid SDK if you already have this
Or direct from the OEM following the link HERE
Or some say having the Naked Drivers works best, so try HERE or HERE or HERE
If you need help installing these then see the next chunk on adb/fastboot or feel free to ask here as well!
*Linux users just need the android rules set up, see fastboot link for how to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So after drivers are up... Fastboot!
Well here is many's big fear, but fear not as the terminal is not that scary!
For an in depth explanation on how to use fastboot, I highly suggest reading through THIS
It will have all you need to know and if there are any further question please feel free to ask here or in the fastboot thread.
If you have any issues running fastboot (or adb) commands, please copy and paste all input/output from terminal/cmd here so one of your helpers can assist better.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can connect to PC and you know the commands.. but what to flash?
For the most part we want to use the stock firmware found here (some OTAs HERE for another use)
Download the latest for mantaray (currently 4.4.2-(KOT49H)
Now check MD5sum or sha1 for a match (Linux use terminal, windows use THIS)
If all is good lets extract the contents (I prefer 7zip but whatever)
So if all of your prep work is a success then when you type
Code:
fastboot devices
Into a terminal/CMD you will see your serial number
If not be sure you are in bootloader mode (power on while holding volume +)
Also have a high quality USB cable if not the one that came with your device
*Still have issue, ask in this thread!
If you have a locked bootloader it may be wise to
Code:
fastboot oem unlock
Then follow the below info, if you don't want to unlock your tablet just run the flash-all.bat to get similar results
And now you have a bunch of images, lets erase and flash so we will be oh so clean!
*have everything backed up first! this will erase your tablet!
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now after we cleaned things up, lets flash back to stock!
Code:
fastboot flash bootloader nameofbootloader.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
(Everything should be named accordingly except for bootloader, so change this command)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Congrats! You can reboot to a functioning tablet!
Some quick notes:
If you want a custom recovery, fell free to instead flash latest TWRP or CWM or whatever.
You do not need to use stock recovery for the above to work, but you will need your custom recovery in a .img
Similarly if you want a custom ROM instead of stock you can do this, but only if your dev supplies you with the system.img, if not just boot to recovery, make a nandroid, wipe all, flash custom ROM and gapps through adb sideload.
If you still have a bootloop or a "brick" then ask us here and someone will be glad to give you personal assistance.
Or for real time help you can see if anyone is at ##Manta_Help_IRC on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anything I missed feel free to ask in this thread!
Happy Flashing!

Tech Specs and More!
Want To Know More About Your Tablet
GENERAL INFO
GSM ARENA
Factory Images "mantaray" for Nexus 10
AOSP
Click to expand...
Click to collapse

Quick Linux/Unix Rooting Guide
First of all, you need to have Fastboot and ADB. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now follow the instructions on your tablet screen. As soon as your bootloader is unlocked the device will reboot, so you'll now download the recovery and the Superuser.
Get the TWRP from here (download the .img file): http://www.teamw.in/project/twrp2/128
Get the SuperSU from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
Copy SuperSU to your device internal memory (that's probably empty now) and rename the .img file of TWRP to recovery.img. Now enable USB debugging again (it's explained above lol) and replug the tablet on your PC. Time for typing again! (Please, open the terminal in the folder where the recovery.img is located).
Code:
adb reboot bootloader
Wait for it to reboot, and then type:
Code:
sudo fastboot boot recovery.img
(If you want to install the recovery permanently in the device, type 'sudo fastboot flash recovery recovery.img' before issuing the command above).
Now you probably see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click in Install and select the SuperSU zip that you copied to your tablet internal memory earlier. When the flash is complete, reboot the tablet and congratulations! You're rooted :victory:.
Hope this helps anyone who may need it!
Click to expand...
Click to collapse
Quick Linux/Unix Restoring to Stock Guide
So you've decided that you don't want root anymore or you did something and want to restore to stock? That's not a hard thing to do! Just follow these steps and you'll be fine.
First you need to have adb and Fastboot ready. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now you'll follow the instructions on screen. When your device is unlocked, you'll have to download the stock firmware you want from one of those links:
Android 4.2.2. - https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz
Android 4.3 - https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Android 4.4 - https://dl.google.com/dl/android/aosp/mantaray-krt16s-factory-94413961.tgz
Android 4.4.2 - https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz[/CODE]
Click to expand...
Click to collapse
Now that you're done with your download, you'll extract the .tgz package the way you prefer. Now, open a command line in the folder where the extracted files are and (with your device plugged on fastboot mode) just type:
Code:
chmod 755 flash-all.sh
sudo ./flash-all.sh
The procedure will now begin. It can take some time to finish. When it ends, it's recommended that you lock back your booloader, which is as easy as unlock. Type (tablet plugged in fastboot):
Code:
sudo fastboot oem lock
Hope this helps!
Click to expand...
Click to collapse
~Lord

XxLordxX said:
If you want I can do the Linux walkthrough and script . I'll be more than glad to assist in this.
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
Yes a Linux walk-through is what I was going to do... I can also do a windows one it will just take me a bit longer... Thx lj

i want in! "all-round-android-guy"
Sent from my Nexus 4

Nexus 10
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110

kerriganinks said:
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
Click to expand...
Click to collapse
What is your PC's OS.....:good:

OS
lj50036 said:
What is your PC's OS.....:good:
Click to expand...
Click to collapse
Windows 7 64 bit. on several machines. I tried 3 diff systems same results, even tried the hated toolkits, but the bootloader locks on any reboot at all. Negating any changes, the fastboot at least didn't reboot so it said all commands were completed, but nothing actually changed. I'm having issues reading those verifications on the page to post, is there a way around that. I got the phone number to call this in to Samsung for service, something has it locked and I've wasted way too much of my life toward trying to work on someone else's tablet. I've used the flash method on several phones and tablets in the past, so not a complete novice, just know it's not giving the same results as for others because something's wrong with the tablet.

This indeed is a strange issue, it seems others have had the same challenge
http://forum.xda-developers.com/showthread.php?t=2638227
Can you try the fastboot method of restoring stock again and this time copy and paste all input/output here
Also can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app

Nexus 10 Boot behavior
Hello forum gurus!
I have a question regarding the boot behavior of the Nexus 10 that you'll probably know something about.
I need to have the device boot straight to the android desktop after it's been plugged in while in an off state. Usually, most devices boot into a battery-charging screen when you apply power while they're off, then they top up the battery and go to sleep, waiting for you to press the power button.
I'm hoping there is a way to alter this behavior and get the device to boot into android's desktop straight up. I've seen this setting being changed between different ROMs and I'd like to hear your opinion how to get the change done.
This is for a project of mine, the way I see it, i'll be using a few of these tablets for an installation.
Thank you for your feedback in advance!
Best,
Stef

Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks a lot, also for the quick response.
I'll wait for your reply, so we don't end up pestering the same people twice for the same thing.
BR,W
demkantor said:
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Please Help
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me

unitnerd said:
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
Click to expand...
Click to collapse
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

XxLordxX said:
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
How do i reformat with pc?

hi, i am very new to android (i still use a flip phone)
i have unlocked my nexus 10 (4.4.2), and have stopped there.
after the final steps in post #3
>fastboot erase system -w
>fastboot erase boot
>fastboot erase recovery
>fastboot flash bootloader nameofbootloader.img
>fastboot flash system system.img
>fastboot flash userdata userdata.img
>fastboot flash cache cache.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>Congrats! You can reboot to a functioning tablet!
after the reboot, would the device be rooted?
thanks in advance.

Not if using the factory image, you would still need to boot into recovery and flash superuser, then it would be rooted. Or boot to recovery and flash one of the many custom ROMs, all of which are prerooted
Really the only thing you need to do is unlock the bootloader, flash a custom recovery, then either flash a custom ROM or su
Sent from my Nexus 4 using XDA Premium 4 mobile app

thanks for the reply,
it looks like a 'catch 22' , but im sure its just that, i am seriously confused.
after reading several links, that link, to yet another linked guide.
i thought that i would use team win recovery project but it requires root. so thats a no go.
i checked a few others but same situation, require root to use.
could you/someone recomend a stable recovery or whatever i need.
...my head hurts, ill revisit this tomorrow.

FIX HTC-U11☆corrupt☆relocked☆s-on☆

______________________________________________
REPAIR HTC U11 - CORRUPT - RELOCKED - S_ON
______________________________________________
I run a phone repair shop,
Customer brought a HTC U11 in to repair,
was soft bricked with an attempted custom rom installation then relocked the bootloader without flashing a working OS to it,
The os version was there but when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
this tutorial is how I managed to revive the dead device please read below.
Device specs on this model were :
______________________________________________
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
______________________________________________
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
_____________________________________________
Bootloader displayed killswitch enabled please disable,
Killswitch/frp
Killswitch/oem unlock
Killswitch/bootloader
when trying to unlock with provided original unlock_code.bin that was provided with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device, also couldn't receive the unlock code
_____________________________________________
I used tried the following programs to flash :
•htc_fastboot.exe
•minimal adb and fastboot 1.7msi
•power shell on windows 8.1
•minimal adb & fastboot
•fastboot binaries from htc_dev.com
couldn't get anything to flash to the customers phone with any of these so dont bother.
____________________________________________
NOTE
I downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case, so just download all relevant files with your matching CID main version shouldn't be an issue as it wasnt for me.
_____________________________________________
REPAIRING THE HTC U11
NOTE
☆Links are at the bottom of tutorial☆
#1 Go through the files in spreadsheet then download all with the same CID as you have even though the main versions might be different,
#2 try to flash them all with normal fastboot to see what is a signed or close to signed zip and what isnt, (you will know by the RUU errors you face anything but RUU security fail zip from USB command or RUU main version fail ) means it probably won't work but try anyway,
NOTE
I narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 Now the only flash tool that works for downloading to the device in RUU mode is the HTC 10 batch tool.
#5 Place the .zip into the "com" folder which is located where ever the batch tool is installed, in my case was C://Android/com
#6 Open the batch tool with administrator privledges,
select option 3 to open fastboot terminal with the purple screen
NOTE
when entered location of the terminal should be "example" C://android/com on the screen this is where you placed your RUU.zip file.
#7 boot U11 to download mode, with device off hold,
•Power
•Volume down
NOTE
plug the device into the computer & make sure drivers are installed properly and working.
#8 Type into the terminal "fastboot oem rebootRUU",
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
NOTE
do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
it flashed all 28 zips twice in my case as it needed to be flushed the first time, these same files would not work on any other fastboot terminal I would only ever receive RUU error zip from USB command or RUU error main version fail,
so there you go this helped me and now I hope it can help you all out with your broken U11 fix please enjoy and if this tutorial has helped you please dont forget to hit the thanks button
_____________________________________________
NOTES
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work.
WINDOWS 10 USERS :
you MUST disable driver signature verification or you will not be able to install any drivers for your U11.
_____________________________________________
FASTBOOT COMMAND SYNTAX
_____________________________________________
STANDARD SYNTAX
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
HTC SYNTAX
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
_____________________________________________
LINKS
_____________________________________________
HTC 10 batch tool (credits to sneakyghost ),
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
_____________________________________________
Google spreadsheet for your RUU (credits to 5m4r7ph0n36uru),
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
_____________________________________________
HTC drivers for your U11 (fastboot adb & mtp)
http://gsmusbdriverzone.xyz/download-htc-u11-usb-drivers-official.html
____________________________________________

☆☆☆EDIT☆☆☆
I have noticed in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install OTA updates up until 1.29.710.9 version before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks

Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Sent from my coconut frond hut using Tapatalk

mauiblue said:
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Click to expand...
Click to collapse
Hey mate,
No problem at all
Firstly though I would strongly suggest to flash the Unlock_code.bin you got from HTC dev to unlock your bootloader while you have a functional OS,
enable OEM unlock in developer settings then flash unlock code via bootloader or download mode, will save you the big headache of what I was going through when the bootloader is re locked only signed firmware can be flashed but if unlocked can flash unsigned firmware to the device,
I'd say HTC has not repaired the device correctly at all, I'd be pursuing reimbursement for any money you have paid to them,
not even I have had re corruption or anything works like brand new just my OS version in download mode is 2.33.710.9 but zip I flashed in RUU mode was 1.03.710.7 but let me OTA all the way up to 1.29.710.9 before it stopped installing them it downloads it just wont install it,
I'd switch OEM unlock on, flash unlock_code.bin to get unlocked bootloader will stop you from getting the corruption error, I'd also change the OS also just to see if HTC havent flushed something out of the device properly.
Just please whatever you do do not lock the bootloader without a functional OS
Hope this helps mate, if you need any more help dont hesitate
Thanks

Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!

I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.

korom42 said:
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
Click to expand...
Click to collapse
No problem mate ,
I'm not sure why,
but the customer locked his bootloader before having a workable OS, he had a viper rom with TWRP on it & from what he told me he wanted the oreo bootloader and modem so tried to flash a firmware package that did not flash, but did not take a nandroid backup prior with TWRP then locked the bootloader allowing only signed firmware to be flashed, dont asky me why lol, as even re locking the bootloader it stills shows as modified in bootloader mode, possibly he thought that it would go away if he re locked it I cant be certain he wasnt to sure what he did,
I also had to re lock the bootloader after unlocking it to receive the OTA Updates from 1.03 - 1.29 as they wouldnt install they would download but not install as soon as I re locked it again I could OTA all the way up to 1.29.710.9 before the same would download but not install,
But in my personal reference to everyone you would be better of keeping the BL unlocked your device wont corrupt
As for the re lock of the bootloader snd the exact ruu version as mentioned in the post OS this was corrupted and would not boot, had no recovery only fastboot, download & RUU , could not flash token or receive unlock code, main version on device was showing version 2.33.710.9 as oreo firmware but ruu that I got to successfully flash with the HTC 10 batch tool was nougat 1.03.710.5, which was also giving me RUU error main version in normal and HTC fastboot but same file worked in the batch tool fastboot with or without htc-fastboot syntax I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would , main versions and SDK were both diff and it definitely works I recreated and flashed the device over and over again just to be sure before originally posting

mauiblue said:
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
Click to expand...
Click to collapse
Have to use fastboot to flash device, or sd card,
Fastboot is diff from adb, but glad everything is working well now for you mate and you shouldn't hopefully have anymore problems with it

Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse

mauiblue said:
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
Haha patience probably not lol I'm surprised the phone ever started working again after some of the things it got called , no I'm just persistent in everything I do if I cant repair it I make it my goal to repair it ,
That's what I explained to the customer also never lock a bootloader when they system doesn't function as it should only bad things can happen,
I kept getting the OTA notification pop up to but you cant turn it off on HTC like you can with Samsung
I just flashed oreo and kept BL unlocked and no problems again so far
But it does pay off to read that is very true, I learnt the hard way when I first started out with mobiles I had a brand new S3 when they just came out and ended up flashing an S2 kernel to it and literally burnt the touch controller out on the board and made the touch non functional, I've always read up on everything ever since before attempting repair modification or customisation and havent gone wrong since pretty much,
Speaking of HTC did they charge you a fee to supposedly "repair" your device, as I could tell just from what you mentioned something wasnt flushed right in it, which makes you entitled to a refund, I'd file a dispute with them for the work order and reimbursement on the postage and what not as to be honest I've even been all over HTC websites in aus and America and spoken to they're tech support also (usless might i add) even they state that sometimes they cannot even fix this exact issue, and they charge more for the fact the bootloader is modified to repair them,
Click to expand...
Click to collapse

Aloha M. Fortunately HTC has didn't charge me anything. The frustrating thing is that they didn't include with my phone documentation on what they supposedly had done to the phone. Obviously they were able to get the phone to boot up at least once. But it seems like they didn't even test the phone so that it would consistently boot up. Flashing the latest OS update wouldn't have taken much time. I really like HTC phones and their GUI but their customer service SUCKS donkey balls.
Aloha!
Sent from my HTC U11 using Tapatalk

Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.

mauiblue said:
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
Click to expand...
Click to collapse
That's great mate, glad it didnt cost you anything then, apart from the 5 week wait though that must have been terrible,
I would have thought they would package it up a bit better but then again they have never been good for service,
Anyhow everything must still be working well then and all issues seem to be gone, , I'm yet to receive a U12 into my work for repair but I do agree battery is pretty good on the U11 I can charge it and it last me 2 days almost before I have to charge it again, but then again I've had it open aswell and the battery takes up 3/4 of the phone under the hood it's a very big battery even in actual size,
Anymore problems with U11 or any other makes and models feel free to contact me through pm or post if you need help and I'll get back as soon as I can

Thanks Matty. All the best!
Sent from my HTC U11 using Tapatalk

So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas or advice would be appreciated.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
Hey mate,
Yeah somethings going wrong with your OS
What version of android is it using ? 7.0 or 8.0,
As the bootloader is unlocked please KEEP it unlocked dont relock it under any circumstances if relocked only a very specific version of firmware can be reflashed and if flash fail the device will be bricked completely until the correct RUU is flashed
S-ON shouldnt be a problem when BL is unlocked and you can flash most firmwares that match your HTC u11 MID & CID
Recovery should boot without an SD card so if say recovery is corrupted aswell as part of the system is also,
What you need to do is plug it into the PC and using fastboot type the command,
fastboot getvar mid
fastboot getvar cid
with the device in download mode if you can,
If it wont boot to download mode with the button combination
Turn USB debugging on & connect to pc now your going to be using adb
Type this command to try and reboot to download mode to use the fastboot command to obtain your device info
adb oem reboot-download
Or adb reboot-download
It should reboot you to download mode now where you can obtain the necessary info with the fastboot getvar command,
Once you have that info head over to the google spread sheet and download the firmwares that match your MID & CID and then use the tutorial one page 1 to flash the phone,
Remember do not lock BL under any circumstances bad things will happen if the flash goes wrong.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
I had an nearly similar problem with my SD Card it always was seen corrupt from the system even after formating the SD Card. Then I did a factory reset, that did the trick for me.
It may take some time to set up the phone again, but for me it was the only way to make it reusable again.
Try to use different hardkey combinations, there are more then one to get into bootloader or downloadmode and even with the ADB commands you can treat your device to do what you want!
I hope this will help you.

So the links that I posted don't work because I don't have enough posts. I have factory reset the phone a few times in an attempt to get things working properly again. Here's the info since I can't put up the screenshots:
Android version:
8.0.0
Security level:
June 1, 2018
Software:
Bad Boyz US unlocked U11 v3.8 (I have a feeling I may have used the wrong one here)
Kernel:
3.3.78-perf-gbd700a6
[email protected] #1
SMP PREEMPT
Baseband:
8998-002772-1712182056
Build:
2.42.617.7 9.0_g CL1011554

Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka

kajfux said:
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have you tried the htc_fastboot command syntax mentioned in the tutorial also with the batch tool ? If so and its still not working Its 100% to do with the zip your trying to flash id say it contains header errors,
Has it given you an error somewhere along the lines of "
a terrible mishap happened with the original ret lens 0" thats another common error to receive to indicate that your .zip is no good,
Try another .zip that matches your PID & CID dont worry about the main version the htc batch tool fastboot command promt for bypasses bootloader security to allow rollback of the bootloader,
I successfully took mine back to nougat from oreo with a locked bootloader which couldnt be re unlocked due to all killswitches being on & S-ON, no recovery or working OS, only download, bootloader & RUU mode,
Deffo the .zip trust me sorry for the late reply aswell didnt get notification but i hope this helps you out a bit.

[How To] Enable Cam2API - simply, and keep OTA - NOT working with stable PIE

********** 11/17/18 sorry to say folks, this method of enabling cam2api does not, for some reason, work with stable PIE. Looks like root is the only option now ********
**** please note, the next comment, after this guide, has some 'condensed problem solving' tips from the 10 pages of comments - if you run into problems doing the following, look at the next comment for possible solutions *****
While this might sound similar to other 'guides', it's not the same. In this guide we'll enable Cam2API, not flash anything, and not install root then later uninstall it.
And we won't do it with a 'tool', that you have no idea what it's doing behind the scenes (they have their place, but not really needed for this imho).
Also, it's not my intention to knock Magisk. It's a great rooting app, and it has a lot of additional features besides root. But when deciding to use Magisk or not, if all you want to do is enable cam2API, and use none of it's other great features, it seems like overkill to me.
Prerequisites:
1) Your version of fastboot needs to be one that recognizes 'dual slot' phones (look at the version docs if yer not sure).
2) Your device needs to be bootloader unlocked, and adb debug enabled (research that if you don't know what it means).
3) You need the latest version of Tingyichen's TWRP, which currently is twrp-3.2.3-jasmine-20181020.img
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
1) Connect the device with adb, and verify it's working with 'adb devices'. Assuming it works type:
Code:
adb reboot bootloader
2) Once in fastboot (the bootloader), find out which slot is current with:
Code:
fastboot getvar current-slot
Make a note of which slot is current.
3) If the current slot is NOT 'a', then we have to set it to 'a'. Do the following to accomplish that;
Code:
fastboot set_active a
4) With the current slot set to a, do the following command:
Code:
fastboot boot twrp.img
(or the actual name of your twrp.img if you didn't rename it to twrp.img - you don't *have* to rename it, seems most people do though.)
At this point, let the device start and go into twrp. You will have to use your 'pattern' if you have one set on the phone. Also, you do NOT have to hold vol up to boot into twrp.
5) Now we'll do the 2 (or 3 if u have Pie) commands to set cam2 enabled.
Code:
adb shell
Code:
setprop persist.camera.HAL3.enabled 1
note: only do the following command for Pie or newer versions.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
exit
6) Our cam2 will be enabled the next time we reboot. So lets type this:
Code:
adb reboot bootloader
7) Now, if our original active partition was b, we have to set it back to b:
Code:
fastboot set_active b
8) Lastly, we simply reboot with:
Code:
fastboot reboot
That's it, boom, done.
Side Notes:
So why does this work? After so many have indicated TWRP didn't work for them? But it did for others? Wha Up? Simple, it seems twrp isn't very dual slot smart (and why should it be? it was originally written for single slot devices - it DOES give you an option to set the other slot active when you exit it, but all that's doing is running 'set active', nothing to do with installing it).
So I just verified this morning, even though I have cam2 working. My active slot is b, and 'fastboot boot twrp' would fail (even though others said Tingy's new version worked!). So what's different? Only thing I could think of was which slot was active. The active slot changes for ea device with updates, and thus we don't all have the same active slot!
But setting it to a, then doing boot twrp, works like a champ. setprop persist commands of course work also (I verified, even though mine are set). And simply going back to fastboot and doing reboot should avoid any trace of twrp having been used (we didn't 'flash' it, only booted it).
If anyone decides to try 'fastboot boot boot_a twrp.img', that *might* work, I didn't think to try it.
Cheers

updated 11/9/18
Some people have run into issues with twrp working as needed. The following are some of the solutions that have been found:
1) Some have used PBRP instead of TWRP, **BUT** it seems the most recent version of pbrp does NOT work.
2) Some have found that booting TWRP works okay but doing the 'setprop persist' commands didn't result in cam2api being enabled.
2 a) to fix the above, they went into the 'mount' section of TWRP and disabled the MTP option. They indicated they also enabled 'persist', but it's uncertain if that made a difference. (Special thanks to @lept_2014 for that!)
For most, it seems to work just by following the guide. I'd recommend this; ea and every time you go to fastboot, or to the device with adb, always be sure that fastboot and adb can see the device before proceeding. That narrows down the problems significantly.
If 'adb devices' does not show your device in the response, the problem is your PC and usb / adb drivers.
if 'fastboot devices' does not show your device in the response, the problem is with your PC and usb / fastboot drivers.
Thanks to all of the contributors. That's a big help to everyone.

Hello, perfect for me, like a charm.
My slot: A
Thanks a lot, best regards!!
PS: I use CMD. Problems in PowerShell with "fastboot flashing unlock_critical" command.

TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.

When the hell would xiaomi enable cam 2 api by default

kishd said:
TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.
Click to expand...
Click to collapse
Good to know. It's confusing why some of us get 'failed'. But it does work! As you point out also. I guess we can say that if you get a failed message, try setting the other slot active. It absolutely will work.
Yes, why don't they set cam2 by default sharingan, I wish I knew. But using twrp is pretty painless, so at least we have that.
Cheers

Can some pls make video tutorial for this...pls

setprop persist.camera.eis.enable 1 there is no need to knock

Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please

bojan1974 said:
setprop persist.camera.eis.enable 1 there is no need to knock
Click to expand...
Click to collapse
knock what? not making sense to me, sorry

nhmanas said:
Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please
Click to expand...
Click to collapse
Probably the 1st A/B phone for a lot of us.
But no, they don't have the same 'data inside by stock' (I'm not sure what you mean by that).
They use different partitions for many things such as; boot, system, vendor (the most important ones). But they do use the same one for data (is that what you meant?). The data one is where our apps, media files, etc are kept, and that doesn't change with an OTA update.
Another important difference is there is no longer a 'recovery' partition, which is what twrp use to be installed in. Now, with A/B, the 2 boot partitions and the rest of the 2 partitions are the old 'recovery'.
So what does the 'other' boot partition have in it? Well the old version of the OS before the OTA update. That doesn't change with an update. The other slot is updated and then made active. Then when a new update happens, the current one becomes the old one (again). And on and on.
the reason this works is because the setprop persist commands only change the data partition, not system. And since twrp mounts data (of course it does, it's a recovery tool), it can execute the setprop commands no problems.
good luck

When i boot twrp i get error: device '(null)' not found.

Ajakazema said:
When i boot twrp i get error: device '(null)' not found.
Click to expand...
Click to collapse
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?

AsItLies said:
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?
Click to expand...
Click to collapse
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Edit: when i type fastboot devices it just says list of devices attached

Ajakazema said:
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Click to expand...
Click to collapse
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?

AsItLies said:
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?
Click to expand...
Click to collapse
Did both of those things.

Ajakazema said:
Did both of those things.
Click to expand...
Click to collapse
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.

AsItLies said:
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.
Click to expand...
Click to collapse
Yea i tried that too, no luck.

Ajakazema said:
Yea i tried that too, no luck.
Click to expand...
Click to collapse
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...

AsItLies said:
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...
Click to expand...
Click to collapse
Yea. No idea what the problem is.

Newbie bricked his phone, has solution but cannot implement it ,needs Linux help, PLZ

Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *>
What I did to get here:
I use MX Linux
Accidentally wiped my phone while playing around with unlocking the bootloader. Decided to install Lineage Unofficial. Installed TWRP, Lineage, GAPPS, Magisk. Everything booted and worked fine, but pretty much hated it because so many apps won't work. Found lots of work arounds, but the core communication apps I have to have won't work. Decided to flash Oxygen back on the phone.
My adb backup turns out is probably corrupt and won't install. ADB extractor can't seem to work on my system so I cant fix my extract and fix the back up.
Downloaded the factory zip.
Opened TWRP flashed the rom......and here is where I messed up.......instead of rebooting to recovery and reinstalling TWRP I reinstalled TWRP and MAGSIK then rebooted. Now I can only boot to TWRP
You can stop laughing now. I NOW realize my mistake and the solution seems to be to adb sideload the image and reboot to system.
Oh yeah, for some dumb reason I did a wipe somewhere in there without tucking the os image somewhere safe 1st, so it is no longer on the phone to install from TWRP.
When I try to sideload I get the above error message and all of the guides for solving that error message are for windows......a system I haven't used for almost 3 years.
My semi educated/guessing stab at the problem is the file size. from my reading adb tries to load the entire file into ram. I need to overcome the 2g ram limit ( from my reading ) but can't find any instructions on how to do that for Linux.
Solution 2 would be find a really small, lite ROM to load, get the phone where it will boot, set up TWRP again, download the OOS zip and flash from TWRP.....the right way, but I am clueless as to what rom would be small enough to not get the above error.
Thank you very much in advance, Glockdoc

PattayaGlock said:
Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *>
What I did to get here:
I use MX Linux
Accidentally wiped my phone while playing around with unlocking the bootloader. Decided to install Lineage Unofficial. Installed TWRP, Lineage, GAPPS, Magisk. Everything booted and worked fine, but pretty much hated it because so many apps won't work. Found lots of work arounds, but the core communication apps I have to have won't work. Decided to flash Oxygen back on the phone.
My adb backup turns out is probably corrupt and won't install. ADB extractor can't seem to work on my system so I cant fix my extract and fix the back up.
Downloaded the factory zip.
Opened TWRP flashed the rom......and here is where I messed up.......instead of rebooting to recovery and reinstalling TWRP I reinstalled TWRP and MAGSIK then rebooted. Now I can only boot to TWRP
You can stop laughing now. I NOW realize my mistake and the solution seems to be to adb sideload the image and reboot to system.
Oh yeah, for some dumb reason I did a wipe somewhere in there without tucking the os image somewhere safe 1st, so it is no longer on the phone to install from TWRP.
When I try to sideload I get the above error message and all of the guides for solving that error message are for windows......a system I haven't used for almost 3 years.
My semi educated/guessing stab at the problem is the file size. from my reading adb tries to load the entire file into ram. I need to overcome the 2g ram limit ( from my reading ) but can't find any instructions on how to do that for Linux.
Solution 2 would be find a really small, lite ROM to load, get the phone where it will boot, set up TWRP again, download the OOS zip and flash from TWRP.....the right way, but I am clueless as to what rom would be small enough to not get the above error.
Thank you very much in advance, Glockdoc
Click to expand...
Click to collapse
Msm tool

Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.

PattayaGlock said:
Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.
Click to expand...
Click to collapse
Then you're screwed...

Idk about your backups but why not just run Windows in a VM? From there you could easily run MSMTool or the stock fastboot adb option. I've never had success flashing OOS via twrp coming from a custom rom.

The plot thickens.......
Well James, thanks. LOL.. I am amazed how many android developer, hackers, tinkerers DON"T use linux.
Demon Lord, thanks for the USEFUL heads up. Thanks for paying attention to the post that mentioned I use Linux. I had entertained that as a very last resort. I have 1 machine that is dual boot windows so I probably would have used that one.
On to the next chapter. .....
I am up and running with Oxygen OS again. Still not sure exactly how.
I turned my phone off and was going to swap sims into another phone so I at least have a phone. Pull the phone out of the case and the damn thing booted into lineage!! All my downloads and files were still there. Not sure how after a wipe, but they were.
My guess is the case was holding down the volume button and this is why it kept booting to TWRP. No idea why Igot into lineage as I installed and wiped last night before my booting to recovery started. Since Lineage booted up,and the OOS zip was there, I booted into TWRP recovery and installed OOS from the zip.
I still don't know how all of this worked out like it did, but I am up and running. I still have to set up all my settings and apps( this time without signing into or using my google account ), but I am good to go.
The original problem still exists so I will leave the post open so others can reply with a fix.
Looks like this was a case of having a just enough knowledge about what I was doing to get in trouble!!
Thanks for responding to my problem.
JC

PattayaGlock said:
The plot thickens.......
Well James, thanks. LOL.. I am amazed how many android developer, hackers, tinkerers DON"T use linux.
Demon Lord, thanks for the USEFUL heads up. Thanks for paying attention to the post that mentioned I use Linux. I had entertained that as a very last resort. I have 1 machine that is dual boot windows so I probably would have used that one.
On to the next chapter. .....
I am up and running with Oxygen OS again. Still not sure exactly how.
I turned my phone off and was going to swap sims into another phone so I at least have a phone. Pull the phone out of the case and the damn thing booted into lineage!! All my downloads and files were still there. Not sure how after a wipe, but they were.
My guess is the case was holding down the volume button and this is why it kept booting to TWRP. No idea why Igot into lineage as I installed and wiped last night before my booting to recovery started. Since Lineage booted up,and the OOS zip was there, I booted into TWRP recovery and installed OOS from the zip.
I still don't know how all of this worked out like it did, but I am up and running. I still have to set up all my settings and apps( this time without signing into or using my google account ), but I am good to go.
The original problem still exists so I will leave the post open so others can reply with a fix.
Looks like this was a case of having a just enough knowledge about what I was doing to get in trouble!!
Thanks for responding to my problem.
JC
Click to expand...
Click to collapse
Just a fyi. OP6T uses the A/B partitioning scheme. Would explain how you could boot into lineage with everything intact after a wipe. Say OOS is on Partition A and lineage on B. When you boot into Twrp you should be able to see which slot you're currently on.

You want stock? Boot into twrp, flash stock rom, twrp installer. Go to reboot menu and see what slot you are on. Reboot into recovery. Note again which slot you are in. Reflash stock rom and twrp. Reboot to recovery and note what slot you are using. Flash Magisk.Go to wipe menu format data. Boot system. Note!! BEFORE DOING THIS COPY ALL YOUR IMPORTANT FILES ON PHONE TO YOUR PC SO YOU CAN RESTORE THEM AFTER FORMATING DATA..
Sent from my ONEPLUS A6010 using Tapatalk

I can't believe how many people jump straight to the MSM tool, this should not be the first thing you use. These phones are so easy to fix without using something that locks your bootloader. That should be your last resort.
Also a Linux user here, and I've recovered my phone using the link below, something to keep in mind in the future:
OP6T Fastboot ROM
Not sure what you had not working though in Lineage, odds are you didn't enable some permissions in the Trust Center / Privacy Guard or something though. Everything should just work.

Agreed
OhioYJ said:
I can't believe how many people jump straight to the MSM tool, this should not be the first thing you use. These phones are so easy to fix without using something that locks your bootloader. That should be your last resort.
Also a Linux user here, and I've recovered my phone using the link below, something to keep in mind in the future:
OP6T Fastboot ROM
Not sure what you had not working though in Lineage, odds are you didn't enable some permissions in the Trust Center / Privacy Guard or something though. Everything should just work.
Click to expand...
Click to collapse
I agree with you. I bricked my phone a couple weeks back, the same as op. But I manual fastboot flashed every .img and still to no avail. But then I flashed all .imgs again then booted to twrp>flashed twrp installer> factory reset> the wipe data> flash rom>reboot twrp > wipe data again then I was able to boot in oos 9.0.14 with no issues. So if your still having trouble follow the steps from the fastboot ROM thread that the person I quoted said to then continue with what I said above. You will be back up and running in no time. BTW it took me about an HR total.

PattayaGlock said:
Howdy,
First the problem, then I will tell you what I have done to get here and what I have found to fix it........
The problem:
Adb sideload is saying:
sudo adb sideload OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip
loading: 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip'
* cannot read 'OnePlus6tOxygen_34_OTA_20_all_1904032212b6154bb7f26.zip' *
Click to expand...
Click to collapse
Waaaaaaaaaaaaaay too much work involved on your side...
All you needed to do was copy the ROM to the phone while it is booted in TWRP. It has MTP capabilities. From there just flash the rom like normal. If your linux is being hard with MTP, although it shouldnt, you could also have done an ADB Push command.
The error you are getting seems like its being caused by an old version of ADB however, I dont know that for fact.
Done!

So 9.0.15 wasn't working out so well for me, and I did something bone headed downgrading.... Guess what I'm doing right now.... No MSM tool needed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

PattayaGlock said:
Thanks James, but that is a mcirosoft based solution.
I don't use windows.
I can't seem to find a linux version.
Click to expand...
Click to collapse
Windows garbage install via Virtualbox... works like a charm.

[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case.
*** USE USB 2.0 Port and Windows Machine
!!! BEFORE YOU CONTINUE, POST #3 CONTAINS AN IMPORTANT MESSAGE SPECIFICALLY FOR THIS THREAD !!!​
Spoiler: Requirements = Install these prerequisites before proceeding
- 32-bit | 64-bit Qualcomm Driver
- OnePlus Drivers
- Google USB Driver
Part 1: Return to T-Mobile Stock Firmware via MSM TOOL​Turn on Test Mode, Disable Device Driver Signing via Powershell and set Time Date to 2017, then restart PC
Code:
bcdedit.exe /set nointegritychecks off
bcdedit.exe /set testsigning off
1. Launch MsmDownloadTool V4.0.exe.
2. On the login prompt select "Other" in the dropdown menu and click on Next.
3. Click on Target button and select TMO.
4. Press Start button so that it waits for your device to be connected
5. Power off your device
6. Put your phone in EDL mode
by completely turning off your device, hold vol up + vol down and plug in the cable
OR
via ADB command
Code:
adb reboot edl
7. Once phone is in EDL Mode, immediately Click ENUM button and then START button
Wait approximately ~250-300 seconds.
Device will reboot afterwards.
Part 2: Unlock Bootloader with no code and apply Dual SIM​After reboot, Turn on OEM Unlock in Developer Options before proceeding with the steps
1. Rename and move “instantnoodlet_15_O.16_201001.ops” from MSM Tool directory to somewhere else (e.g., Documents Folder)
2. Download "unlock.ops" and rename it to instantnoodlet_15_O.16_201001.ops
3. Move the "renamed unlock.ops" to MSM Tool directory
4. Launch MSM Tool and proceed using the steps from Part 1
MSM Tool will finish flashing in under 15 seconds and the device will reboot with the message, "<!> The device is corrupt.."
5. Unplug phone from PC and Force Shutdown device by simultaneously press and holding Power and Vol buttons till the device reboots
6. Let go of all buttons once you see device reboot with the logo FASTBOOT MODE, the big START logo will appear afterwards
7. Open SDK Platform Tools folder and launch Powershell/CMD from there
8. Copy and paste this command to check if device is recognized in FASTBOOT
Code:
fastboot devices
9. Once device isrecognized by terminal, copy and paste this other command
Code:
fastboot flashing unlock
10. A confirm bootloader prompt will appear, use Vol buttons to hover on UNLOCK THE BOOTLOADER and to confirm, simply press Power button
Once confirmed, device will reboot back to T-Mobile Firmware but now with Dual SIM and an unlocked bootloader. To use the MSM Tool again without the "unlock.ops", move the unlock.ops to a different place and put back the original ops.
Part 3: Converting to other regions (e.g., Global, EU, Indian) and lock Bootloader​*** Cannot lock bootloader after flashing Fastboot ROM. Will corrupt device ​*** As of right now, Dual SIM doesn't work on OOS12/13 Indian Firmware​1. Download this Fastboot ROM
2. Open Fastboot ROM Folder, click flash-all.bat and type and enter "y" to the terminal
Code:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
3. Reboot phone to FASTBOOT MODE and plug the phone back to the PC
4. Once the process is done, find an OTA ZIP from this thread to update to and download it
(You can use ota.zips from any region whether it be EU/India/Global, e.g., OxygenOS 11 Global 11.0.11.11)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. put the OTA ZIP in the phone, update it and reboot
After rebooting, you can either lock bootloader or stay unlocked to root
6. To lock bootloader, reboot to FASTBOOT and plug phone in to PC
7. Open platforms-tool and open a terminal from the folder
8. Copy, paste and enter this command:
Code:
fastboot flashing lock
9. Confirm the prompt LOCK THE BOOTLOADER and the phone will perform a factory reset and reboot.
There you go! What you can do at this point is stay and daily drive OxygenOS 11 or update to OxygenOS 12/13 or even ColorOS. Dual SIM will work on any Firmware Region. The phone's model will also permanently change to IN2015=OnePlus 8 Global Version Model unless you go back and use MSM Tool again with the original ops.

Thanks thattechguy_69 for the shout out much appreciate that, just glad I was able to help

Dear OnePlus 8 community,
This is my last time visiting y'all. Thank you for all the support and help you guys have gave me throughout the past year. You guys were the first community that I was a part of. I have now retired my OnePlus 8. This device is what entered me into the realm of XDA in the first place. This place will always be a part of my heart and I will cherish the memories I have experienced with it. This guide will be a step-by-step summary of all the guides scattered in the OnePlus 8 Guides Section. A reminder to the next OnePlus 8 users, don't let this community die and keep the old OnePlus Never Settle spirit, alive!
Sincerely, Aaron
22 November 2022​
Credits to these amazing people for making this possible:
@matteosaeed and his Guide.
Ms. user_ajusee's Guide
Mr. gregoryaul (@Aulgreg38) from HighOnAndroid Forums
THE MAN HIMSELF: Mr. Max Lee of HighOnAndroid Forums; link to his YouTube channel.
@MohmmadUzairKhan for figuring out the details for instant bootloader unlock that also came with dual sim
@Mason220 for providing unlock.ops for the Verizon models which also happen to work on T-Mobile models
@Some_Random_Username for the MSM Tool and instructions

Aulgreg38 said:
Thanks thattechguy_69 for the shout out much appreciate that, just glad I was able to help
Click to expand...
Click to collapse
Oh thank you Mister!

Hi man i do everthing like the post say and i got it. But i notices that when you convert t-mobile oneplus 8 to global you lose safetynet. so i was wondering 2 things. How can i get safetynet working again, and if i relock the bootloader with the global firmware will it boot or it will break? Thanks mate.

Adriancris7 said:
Hi man i do everthing like the post say and i got it. But i notices that when you convert t-mobile oneplus 8 to global you lose safetynet. so i was wondering 2 things. How can i get safetynet working again, and if i relock the bootloader with the global firmware will it boot or it will break? Thanks mate.
Click to expand...
Click to collapse
If you lock bootloader the system will say your phone has been corrupted and if you did happened to lock your bootloader. You are gonna have to use MSM tool to restore OS and your are gonna have to start again to step 1.
For the other issue which is safetynet, did you root your phone? From what I know you would only lose your safety net when you root your phone. I did root my phone 2 weeks ago and from what I remember my safetynet was fine. You are gonna have to ask someone about safety net man since I am no expert at that region.
Anyways, thank you for using this guide. Really appreciate it man

thattechguy_69 said:
If you lock bootloader the system will say your phone has been corrupted and if you did happened to lock your bootloader. You are gonna have to use MSM tool to restore OS and your are gonna have to start again to step 1.
For the other issue which is safetynet, did you root your phone? From what I know you would only lose your safety net when you root your phone. I did root my phone 2 weeks ago and from what I remember my safetynet was fine. You are gonna have to ask someone about safety net man since I am no expert at that region.
Anyways, thank you for using this guide. Really appreciate it man
Click to expand...
Click to collapse
Ok, I see.. I didn't root the phone. I just want to know. It's just I try to install Netflix in play store and the app didn't show.... So I install safetynet test and shows that it's not working... I don't have plane to root the phone. I only want to convert the phone to global... I don't know how to solve the issue of safetynet.. that why I ask you. Anyway the phone is working flawless no issue at all.

Adriancris7 said:
Ok, I see.. I didn't root the phone. I just want to know. It's just I try to install Netflix in play store and the app didn't show.... So I install safetynet test and shows that it's not working... I don't have plane to root the phone. I only want to convert the phone to global... I don't know how to solve the issue of safetynet.. that why I ask you. Anyway the phone is working flawless no issue at all.
Click to expand...
Click to collapse
Ok so I check my Play Store Certification and I just found out that my device has not been certified which means that's the reason why you couldnt install/update Netflix.

thattechguy_69 said:
Ok so I check my Play Store Certification and I just found out that my device has not been certified which means that's the reason why you couldnt install/update Netflix.
Click to expand...
Click to collapse
Yeah, that's what I told you. How can we solve the issue. It's the only bug I've found.

Adriancris7 said:
Yeah, that's what I told you. How can we solve the issue. It's the only bug I've found.
Click to expand...
Click to collapse
Download "Device ID" and copy Google Service Framework (GSF) and then paste it on this link
https://www.google.com/android/uncertified/ , just wait for Google to Verify your device. If it does not work then just download apk on apkmirror or revert back to T-Mobile ROM. I am in the process of trying to get mine also certified.

This worked for me, but had the same issue with the safetynet and thus can't use google pay. Just submitted the GSF for google to verify. Did google verified your device yet?

Oneplus8rooter said:
This worked for me, but had the same issue with the safetynet and thus can't use google pay. Just submitted the GSF for google to verify. Did google verified your device yet?
Click to expand...
Click to collapse
I changed my ROM to Pixel Experience because of OOS 11 battery issues and etc. But I dont think it did certify my device. Did some research on this before I switch and someone said it should certify your device but it wont say it. Another method I heard is to clear cache and storage cache on Play Store App and it should but I have never tested this one. The most sure method I saw was to root phone and bypass.

thattechguy_69 said:
I changed my ROM to Pixel Experience because of OOS 11 battery issues and etc. But I dont think it did certify my device. Did some research on this before I switch and someone said it should certify your device but it wont say it. Another method I heard is to clear cache and storage cache on Play Store App and it should but I have never tested this one. The most sure method I saw was to root phone and bypass.
Click to expand...
Click to collapse
Yeah, I tried the play store app and gpay cache and storage cache clearing with no luck. I use gpay with NFC quite often so it was a bummer that it won't work without being certified. Thanks you for writing the guide regardless!

Oneplus8rooter said:
Yeah, I tried the play store app and gpay cache and storage cache clearing with no luck. I use gpay with NFC quite often so it was a bummer that it won't work without being certified. Thanks you for writing the guide regardless!
Click to expand...
Click to collapse
So sorry man. Thanks for letting me know it worked tho! You should try pixel experience tho. It is certified

thattechguy_69 said:
So sorry man. Thanks for letting me know it worked tho! You should try pixel experience tho. It is certified
Click to expand...
Click to collapse
Yeah, everything else seems to work well besides that.
As much as I would like to try the other ROM, do they keep up with security patches? I just bought this phone used (Tmobile unlocked) and haven't rooted an android for a while and wasn't sure if they still get updates directly from google or some volunteer is maintaining the ROM. Would like to root it to whatever ROM that is the most maintenance free and would support security updates at least for a couple of years. I think oneplus support it up to 2023 for oneplus 8 if I'm not wrong.

Oneplus8rooter said:
Yeah, everything else seems to work well besides that.
As much as I would like to try the other ROM, do they keep up with security patches? I just bought this phone used (Tmobile unlocked) and haven't rooted an android for a while and wasn't sure if they still get updates directly from google or some volunteer is maintaining the ROM. Would like to root it to whatever ROM that is the most maintenance free and would support security updates at least for a couple of years. I think oneplus support it up to 2023 for oneplus 8 if I'm not wrong.
Click to expand...
Click to collapse
Yes they do keep up with updates but the people that are maintaing it are not from google. But I will assure you that it is way smoother and more optimized that the current oos 11. I also bought my phone recently 1 month ago as used! You can check some youtube channels if you are interested in pixel experience. Also changing rom does not require root so you dont have to tinker with safetynet and stuff

thattechguy_69 said:
Yes they do keep up with updates but the people that are maintaing it are not from google. But I will assure you that it is way smoother and more optimized that the current oos 11. I also bought my phone recently 1 month ago as used! You can check some youtube channels if you are interested in pixel experience. Also changing rom does not require root so you dont have to tinker with safetynet and stuff
Click to expand...
Click to collapse
Wow, that looks really good. I might just try that out instead of going back to t mobile stock. Thank you!!

Oneplus8rooter said:
Wow, that looks really good. I might just try that out instead of going back to t mobile stock. Thank you!!
Click to expand...
Click to collapse
Here are the instructions and Follow THE GUIDE AND I MEAN IT: https://wiki.pixelexperience.org/devices/instantnoodlep/install/
you have to be in the latest oos 11 and in the last part of the guide, you can lock back the bootloader by replacing avb key with a custom one. If you dont update to the latest. It will keep saying system ui not working. Learned it the hard way and was hard stuck for 3 days lol. The os itself is directly from the pixels but with added features that was unique from oxygen os so google will think you have a pixel.

thattechguy_69 said:
Here are the instructions and Follow THE GUIDE AND I MEAN IT: https://wiki.pixelexperience.org/devices/instantnoodlep/install/
you have to be in the latest oos 11 and in the last part of the guide, you can lock back the bootloader by replacing avb key with a custom one. If you dont update to the latest. It will keep saying system ui not working. Learned it the hard way and was hard stuck for 3 days lol. The os itself is directly from the pixels but with added features that was unique from oxygen os so google will think you have a pixel.
Click to expand...
Click to collapse
You are a godsend sir!! Looks like I'll be tinkering with it tonight! Thank you so much!

Oneplus8rooter said:
You are a godsend sir!! Looks like I'll be tinkering with it tonight! Thank you so much!
Click to expand...
Click to collapse
No problem!!! Just love helping people