Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[Q] MTP USB Device: ADB lists no devices

Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.

Witchunter said:
Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.
Click to expand...
Click to collapse
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.

Mirhawk said:
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.
Click to expand...
Click to collapse
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?

Witchunter said:
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?
Click to expand...
Click to collapse
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.

Mirhawk said:
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.
Click to expand...
Click to collapse
While waiting for your answer, I found the video detailing instructions to install drivers on Windows 8.1 x64:
Nonetheless, thank you for your answer, now I can continue to try to install CM12.1.

ADB can't recognize my Asus Zenfone 2 phone - Please Help!

Sorry, I have checked with many forums, but couldn't find any solution to this problem...
I shall present a detailed step-by-step recollection of events...
1.) I am running Windows 7 (64-bit) on my PC.
2.) I have recently bought an Asus Zenfone 2 (ZE551ML) on 05-July-2015.
Specs: 2.3 GHz, 4 GB RAM, 64 GB in-built memory, Android 5.0 Lollipop.
OEM Firmware no. that the phone came with is: <WW 2.15.40.13_20150506>
3.) The first thing I did upon receiving the phone is to set a password and encrypt the phone (encryption took only 30 seconds or so).
At that time, my phone did NOT have any SIM card or External SD Card.
Phone was also NOT rooted.
4.) Enabled USB Debugging on my Zenfone 2 (in MTP mode).
5.) Downloaded latest updated Firmware from Asus Support Centre: <WW V2.19.40.22> dated 03-07-2015
The firmware is in ZIP format and is stored on my PC's harddrive.
6.) Downloaded "ASUS Android USB Drivers for Windows" v2.0 dated 05-03-2015
7.) Downloaded "Intel USB Driver for Android Devices" v1.9.0 dated 29-Apr-2015
8.) Downloaded latest ADB FastBoot Drivers v1.4.2
9.) Installed the Intel USB Driver (from step-7 above).
10.) Restarted PC.
11.) Went to Windows Device Manager, updated driver from ASUS Android USB drivers (from step-6 above), even though Intel's drivers are more recent.
After installing Asus's own drivers, my Device Manager looks like this (see image):
{
"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"
}
12.) Restarted PC.
13.) At this time, Zenfone 2 is connected to Windows via both MTP (Media Files) and PTP (Camera files) modes.
14.) Installed ADB drivers into System-wide Mode (C:\adb) in Windows.
15.) Turned-off the phone and restarted phone in Recovery Mode.
16.) Connected the phone to Windows PC by OEM cable.
17.) On phone's recovery menu, selected "apply update from ADB".
18.) Opened Windows Command Prompt in the ADB folder (C:\adb),
and typed: "adb devices".
19.) This is where I am stuck. The CMD screen looks like this (see image)
20.) After reading some forums, I have switched to PTP Mode in phone's Settings->Storage USB Settings.
But the problem persists. I cannot get ADB running in Windows to detect to my Android phone even after connecting to it.
Can anyone tell what have I missed? If someone knows the solution, please please help me.

Simple straightforward way to update firmware on Asus Zenfone 2 without ADB
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
1.) First, make sure that you can transfer files from your Android phone to Windows via USB cable (install the necessary drivers – see my post above.)
2.) You must also have downloaded the latest firmware in ZIP format from ASUS support page (for links, please refer to my above post).
Rest of the stuff I am paraphrasing from ASUS Support section:
3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!

But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.

xbox-er said:
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!
Click to expand...
Click to collapse
xbox-er said:
But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.
Click to expand...
Click to collapse
Seriously this method was there since ages... Nothing new.. And how is it possible that the tool which worked for every android user didnt work for u i didnt even install "ASUS Android USB Drivers for Windows" on my PC just installed "Intel USB Driver for Android Devices" and "15 sec adb installer" and eveything works fine from adb to MTP/PTP... Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all

mhp1995 said:
Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all
Click to expand...
Click to collapse
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.

Harfainx said:
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.
Click to expand...
Click to collapse
I know but sometimes when i also enter adb devices i also dont get anything... But then if i enter adb reboot recovery etc or just sideload the zip file it works...Maybe he has the same problem...

I had this problem this morning, tried three different micro USB cables and the third one worked. The first two would charge but not let the device get detected by ADB.

I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk

Try this
http://forum.xda-developers.com/showthread.php?p=61528830
OTA links for stock ROM
yemnic said:
I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you're in adb the code is
adb sideload
Not
fastboot sideload
Sent from my ASUS_Z00AD using XDA Free mobile app

Nope..am trying to flash my recovery SKU to WW...cos mine is CN,
Sent from my ASUS_Z00AD using Tapatalk

My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!

ione2380 said:
My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!
Click to expand...
Click to collapse
did you first select " apply updates from adb " on your phone before " adb sideload filename.zip " from PC command prompt
select " apply updates from adb " on your phone first, then the phone say's give the zip file from your pc command prompt using " adb sideload filename.zip ".... at the time only the sideload code work.

Yes, i did that, of course.

ione2380 said:
Yes, i did that, of course.
Click to expand...
Click to collapse
Nothing new here? i have the very same problem..

I think i found the final soloution.
Download the newest ADB Tool here: http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
(its an old one mentioned in the guide on XDA how to flash Zenfone2)
Also - use the latest Intel (IntelAndroidDrvSetup1.10.0) driver found here: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Then try again. If you search for devices in ABD (by typing "abd devices") it might still not show your phone, but all the commands will work and you will be able to flash your phone in recovery mode.

Have you found a solution for this? I'm experiencing the same thing on my zenfone 2 (z00ad) on 2.20.40.139. I've tried 4 usb cables and 2 pc's one 64bit win7 and one 32bit win7. Both setup the same way with latest drivers/adb/fastboot and adb system wide installed. This isn't my first android, but it is the first android to leave me stumped with no fastboot/adb access. Also tried with mtp selected, then ptp selected, then none selected. Still the same "Fastboot devices <waiting for devices>" developer mode is enabled with usb debugging enabled

Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!

3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
View attachment 3392841
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
View attachment 3392842
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
View attachment 3392843
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy![/QUOTE]
Do you think can work if i want to substitute de cn firmware with ww firmware?

juanpirata said:
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!
Click to expand...
Click to collapse
Please can you tell me exactly what you did step by step and can you include download links please

Jade Remix OS ROM for NEXUS 10

Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta

You are the man!

Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.

Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.

I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?

its totally a new dev rom! the best out there! Love this rom!

How to add other languages, for example, russian?

So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.

For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?

For some odd reason Tapatalk doesn't work on this ROM for me.

How do we root? Anyone know?

I've found this YOUTUBE link, but didn't test yet

EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?

Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk

I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.

drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.

blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.

This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.

⭐[GUIDE] How to Convert OnePlus 7T T-Mobile HD1907 to Global Firmware OxygenOS 11.0.9.1

Credits:
Click to expand...
Click to collapse
@mauronofrio
@Superboy58
@OnePlus_Team
@Google_Team
Make sure to Backup your Phone Data before Converting your OnePlus 7T!
Click to expand...
Click to collapse
Conversion Requirements
Click to expand...
Click to collapse
A Desktop or Laptop with Windows 10-11 OS
OnePlus OEM Cable Recommended
Make sure you have OnePlus USB Drivers & Bootloader installed properly before you start the Tutorial Highly important before starting. If if not installed properly you will have fastboot adb errors. [Tutorial Linked Below]
Click to expand...
Click to collapse
⭐[GUIDE] How to Properly Install OnePlus 7T Official USB Driver & Bootloader Drivers!
Updated 06/03/23 Download OnePlus USB Drivers❗ 1▫️First Disable Driver Signature Enforcement on your PC. 2▫️Press and hold the Shift key on your keyboard and click the Restart button. 3▫️Choose Troubleshoot > Advanced options > Startup...
forum.xda-developers.com
Turn on USB Debugging in Developer Settings now plug the phone into the PC.
Click to expand...
Click to collapse
{
"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"
}
Please make sure you have everything required & prepared before you start the Conversion Tutorial
Click to expand...
Click to collapse
[Conversion Tutorial]
Click to expand...
Click to collapse
1Download the Patched MSM download tool & Platform Tools, extract both to your desktop.
Patched MSM Tool Download By Superboy58
Click to expand...
Click to collapse
https://drive.google.com/file/d/1ayMLNbBmwtQYjDWq9-T27iGiuexBG47N/view?usp=drivesdk
Platform Tools Download By Google Team
Click to expand...
Click to collapse
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2Download & Extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip to platform-tools root folder.
OxygenOS 10.0.13 Global Rom Download By mauronofrio
Click to expand...
Click to collapse
https://sourceforge.net/projects/fastbootroms/files/OnePlus%207T/10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip/download
3Run the Patched MsmDownloadTool V4.0.exe with Administrator Privilege now click start.
4Now put the Phone into EDL Mode
Turn the phone off completely! Take your OnePlus Cable plug the the USB side into the PC while leaving the Type C port unplugged from your phone. Now hold vol up & vol down buttons at the same time about 5 secs...while doing that plug the Type C port into your phone immediately
Do not let go of vol up & vol down while plugging the cable into your Phone!
Click to expand...
Click to collapse
MSM Tool should detect & begin the installation process if you entered EDL Mode correctly.
5Once the Patched firmware finishes installing! Your phone will boot up a message that says.
"Your device is corrupt. It cannot be trusted & will not boot" Then it will boot into Fastboot Mode after a few seconds. This is completely Normal.
Click to expand...
Click to collapse
6Now while on the Fastboot Screen, Go to Platform Tools root folder on your PC. Type CMD in the top address bar and hit enter a command prompt will appear.Type this Command: fastboot flashing unlock_critical and hit enter. Now look at your phone and click on UNLOCK THE BOOTLOADER!
7The phone will reboot back into Fastboot Mode & Now your Bootloader will be unlocked
8Remain in Fastboot Mode! Now go back to your PC where you extracted the
10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip files and click on flash-all.bat
9The Phone will install the Global Rom firmware. When finished it will boot up and you will see the
(Hi there) displayed on your Screen! Now hold the power key & turn off the Phone immediately Now put the phone back into Fastboot Mode by holding vol up & down plus power key!
10Keep phone plugged in...go back to your PC and run flash-all.bat one more time! Press Y to format data again. Now it will put your phone into (Fasbootd Mode Recovery Menu) this time & finish installing the Global firmware! The Phone will finally boot up with the (OnePlus Global Boot Animation Logo) indicating the Conversion was successful. It will take a long time to boot up into Android that's normal for the first boot!
Note: If it didn't boot your phone into (Fastbootd Mode) when you clicked on flash-all.bat the 2nd time That's ok. just turn the phone off again. Boot back into Fastboot Mode and try again and click on flash-all.bat once more. If it fails on second Flash you need to update your Bootloader driver!! So go back & check out the USB Driver's Guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/
Click to expand...
Click to collapse
11Once Global Firmware is installed successfully, Setup your Phone & skip Wi-Fi setup keep it turned off!!
Download OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip.jar onto your PC. Then rename it to .jar to .zip
Now plug your phone into your PC. Turn USB Debugging on & turn transfer mode on.
Copy OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip from your PC to the (Root System) of your Android.
Now Open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode".
Go to Settings -> System -> System Updates -> top-right corner button select the cogwheel Select Local Upgrade and now select the OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip & let the Installation Finish.
OxygenOS 11.0.9.1 Global Firmware By OnePlus Team
Click to expand...
Click to collapse
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip
12After installing OxygenOS 11.0.9.1 make sure to boot into Recovery Mode and perform a Hard Reset!
Power off your device. Press and hold volume down + Power button. (The device will boot into recovery mode).
Select language. Select Wipe data and cache > Erase Everything (Music, pics, etc) > Tap on "This can not be undone, continue?". Now Reboot system from "Reboot" option."
13I recommend locking your bootloader once completed with the guide, unless you plan on rooting or installing custom roms.
Plug your phone into the PC, Turn USB Debugging on then Boot into fastboot mode.
Open a cmd command prompt in platform tools root folder.
Type fastboot flashing lock hit enter.
It will say do you wanna lock your bootloader hit continue
14Last step is to Disable your updates thats if u don't want Android 12 update Notifications! I've made a guide here https://forum.xda-developers.com/t/guide-disable-system-updates-permanently.4592381/
Tutorial Guide written by @xxlMVPlxx
The Benefits of Global/International Firmware Conversion
Click to expand...
Click to collapse
Completely removes T-Mobile Apps and any underlying Software (there aren't a lot, but why not completely gone!)
Use Dual Sim supported by the hardware & the ability to use other carriers.
Get on the faster firmware release schedule of stock Global firmware because it doesn't need to be certified by T-Mobile, which are always generations behinds.
You can now Root your OnePlus 7T & install Magisk & use Magisk Modules.
You can OEM unlock your Bootloader & put TWRP & install Custom Roms if you like.
Conversation will NOT change your Model Number it will remain a "HD1907"

Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?

Birdflyer said:
Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?
Click to expand...
Click to collapse
Nope not at all. It's an upgrade in my opinion better battery life as well. Just dnt upgrade to Android 12 or 13 on a Converted 7T & your golden.

Birdflyer said:
Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?
Click to expand...
Click to collapse
I used metro PCS after conversion & I never lose connection neither does my wifi which is Comcast.

@Birdflyer Did you try to convert over to global yet?

Hello, I am having a lot of trouble with the MSM tool. I can get the phone into edl mode and start the msm tool, but it quickly disconnects the phone ("status of connection" shows "N/A") and the status of communication is "setting firehose communication data transmission ". On the device manager it shows the phone as unknown USB device (device descriptor request failed). Could this be because my phone is on android 12 or is it a problem with the PC? Luckily, this seems to result in nothing happening to the phone, and after plugging it into the charger I can reboot normally

billybobjoe512 said:
Hello, I am having a lot of trouble with the MSM tool. I can get the phone into edl mode and start the msm tool, but it quickly disconnects the phone ("status of connection" shows "N/A") and the status of communication is "setting firehose communication data transmission ". On the device manager it shows the phone as unknown USB device (device descriptor request failed). Could this be because my phone is on android 12 or is it a problem with the PC? Luckily, this seems to result in nothing happening to the phone, and after plugging it into the charger I can reboot normally
Click to expand...
Click to collapse
That means you need to install your OnePlus 7T drivers properly here's the guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/

xxlMVPlxx said:
That means you need to install your OnePlus 7T drivers properly here's the guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/
Click to expand...
Click to collapse
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!

billybobjoe512 said:
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!
Click to expand...
Click to collapse
Lmk if you get it fixed? You could try Optional Updates.. The bootloader driver could be in there, Update & restart PC. If you see it available?

billybobjoe512 said:
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!
Click to expand...
Click to collapse
You need all 3 of the following drivers. OnePlus USB driver, Bootloader Driver, Qualcomm HS-USB QDLoader driver.

xxlMVPlxx said:
Lmk if you get it fixed? You could try Optional Updates.. The bootloader driver could be in there, Update & restart PC. If you see it available?
Click to expand...
Click to collapse
Yes thank you I got it fixed, I think the bootloader driver wasn't installed correctly so I reinstalled that, and I updated usb drivers through the windows update (these were just the drivers for my PC, not related to the drivers I needed to install to convert the phone). It had some trouble at first connecting to my PC in fastboot but I got it working eventually and now the phone has been converted!

xxlMVPlxx said:
@mauronofrio
@Superboy58
A Desktop or Laptop with Windows 10-11 OS
OnePlus OEM Cable Recommended
⭐[GUIDE] How to Properly Install OnePlus 7T Official USB Driver & Bootloader Drivers!
Updated 06/03/23 Download OnePlus USB Drivers❗ 1▫️First Disable Driver Signature Enforcement on your PC. 2▫️Press and hold the Shift key on your keyboard and click the Restart button. 3▫️Choose Troubleshoot > Advanced options > Startup...
forum.xda-developers.com
View attachment 5853149
[USB Debugging Example]
View attachment 5848755Check the box for always allow!
View attachment 5853287
1Download the Patched MSM download tool & Platform Tools, extract both to your desktop.
https://drive.google.com/file/d/1ayMLNbBmwtQYjDWq9-T27iGiuexBG47N/view?usp=drivesdk
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2Download & Extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip inside Platform Tools Root folder!!!
https://sourceforge.net/projects/fastbootroms/files/OnePlus%207T/10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip/download
3Run the Patched MsmDownloadTool V4.0.exe with Administrator Privilege now click start.
4Now put the Phone into EDL Mode
Turn the phone off completely! Take your OnePlus Cable plug the the USB side into the PC while leaving the Type C port unplugged from your phone. Now hold vol up & vol down buttons at the same time about 5 secs...while doing that plug the Type C port into your phone immediately
MSM Tool should detect & begin the installation process if you entered EDL Mode correctly.
5Once the Patched firmware finishes installing! Your phone will boot up a message that says.
View attachment 5853185
6Now while on the Fastboot Screen, Go to Platform Tools root folder on your PC. View attachment 5853151Type CMD in the top address bar and hit enter a command prompt will appear.View attachment 5853153Put this Command: fastboot flashing unlock_critical and hit enter. Now look at your phone and click on UNLOCK THE BOOTLOADER!View attachment 5853175
7The phone will reboot back into Fastboot Mode & Now your Bootloader will be unlocked
8Remain in Fastboot Mode! Now go back to Platform Tools root folder on your PC where you extracted the
10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip files and click on flash-all.batView attachment 5853235
9The Phone will install the Global Rom firmware. After it boots up to home screen hold power key & turn the phone off...immediately Now put the phone back into Fastboot Mode by holding vol up & down plus power key!
10Keep phone plugged in.. go back to Platform Tools root folder run flash-all.bat one more time! Now it will put your phone into Recovery Mode this time & finish installing the Global firmware! The Phone will finally boot up with the OnePlus Global Splash screen indicating the Conversion was successful. It will take a long time to boot up into Android that's normal for the first boot!
11Once you setup your Phone turn on your wifi download OxygenOS 11.0.9.1 onto your OnePlus7T then copy it from downloads folder to the Root folder of your Android then go to Settings>System>System Updates>Click on the Cogwheel >Local Upgrade
Select your firmware & let the Installation Finish.
If that fails update threw Android System Update.
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip
12After installing OxygenOS 11.0.9.1 make sure to boot into Recovery Mode and perform a Hard Reset! Clear cache & erase everything. Congratulations your done! Your OnePlus 7T will boot back up, Now setup device setup & connect back to your wifi you are finally done with the Tutorial Guide written by @xxlMVPlxx
Completely removes T-Mobile Apps and any underlying Software (there aren't a lot, but why not completely gone!)
Use Dual Sim supported by the hardware & the ability to use other carriers.
Get on the faster firmware release schedule of stock Global firmware because it doesn't need to be certified by T-Mobile, which are always generations behinds.
You can now Root your OnePlus 7T & install Magisk & use Magisk Modules.
You can OEM unlock your Bootloader & put TWRP & install Custom Roms if you like.
Click to expand...
Click to collapse
I followed everything but my OnePlus7t seems to have lost WIFI functionality, please help!

Ramover3 said:
I followed everything but my OnePlus7t seems to have lost WIFI functionality, please help!
Click to expand...
Click to collapse
That's means you didn't completely convert over! Power the Phone OFF then boot into Fastboot Mode by pressing vol up & vol down plus power at the same time. Then go to Platform Tools folder on your PC & click on flash-all.bat again it should boot your phone into Recovery Mode on the second flash all! Then it will boot your phone into Global Firmware finally & your wifi will be restored.

@Ramover3 You need to re-read over steps 8-12 very important. That's where you messed up.

@Ramover3 Take your time & read over if you still have issues report back thanks.

@Ramover3 Did you get it fixed?

xxlMVPlxx said:
@Ramover3 Did you get it fixed?
Click to expand...
Click to collapse
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.

Ramover3 said:
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.
Click to expand...
Click to collapse
You need to unlock the bootloader first that's step 6-7 you cannot flash a rom with a locked Bootloader that's the results you'll get.

Ramover3 said:
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.
Click to expand...
Click to collapse
Make sure to follow all the instructions from the top. Your skipping ahead of yourself take your time step by step...

xxlMVPlxx said:
You need to unlock the bootloader first that's step 6-7 you cannot flash a rom with a locked Bootloader that's the results you'll get.
Click to expand...
Click to collapse
I unlocked the bootloader, then I followed the next steps. I'm going to restart everything from the beginning and then report back.