Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
H4X0R46 said:
Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
Click to expand...
Click to collapse
I just use the regular minimal adb drivers that you can get from here on XDA
H4X0R46 said:
Hey guys, coming from a Nexus device and thinking about getting either the OnePlus 3t or the new 5, and I was wondering, for fastboot mode to work correctly, do I use google's usb driver from the sdk or do OnePlus devices have their own driver I need from somewhere else? Thanks and sorry for the quick noob question, I'm coming from a Nexus so it's a little different.
Click to expand...
Click to collapse
The drivers you have for Nexus devices should work fine with the OnePlus 3(T). I tested it myself, I don't need to switch drivers after getting the OP3, Fastboot detects it just fine with the old driver I had for Nexus 6P.
F4uzan said:
The drivers you have for Nexus devices should work fine with the OnePlus 3(T). I tested it myself, I don't need to switch drivers after getting the OP3, Fastboot detects it just fine with the old driver I had for Nexus 6P.
Click to expand...
Click to collapse
Awesome thanks! I hope to get the 5 when it releases! Those Pixel phones are just....... bleh. One more quick question, what is firmware all about? On a Nexus, you never had to worry about it at all for some reason, I notice with OnePlus devices, a lot of the rom threads say "make sure you have the newest firmware installed" and it's something I never had to mess with before. Thanks for all your help guys! Much appreciated!
With each OOS release there is a Firmware integrated, and if you switch to a custom ROM the firmware will not get updated so you need to flash it manually (there is a thread with all firmwares collected).
PlayingLikeAGenius said:
With each OOS release there is a Firmware integrated, and if you switch to a custom ROM the firmware will not get updated so you need to flash it manually (there is a thread with all firmwares collected).
Click to expand...
Click to collapse
So simply put, just keep it updated yeah? Is there any harm in flashing a newer rom and keeping an outdated firmware?
I don't think it is a problem but the devs often test their rooms with the newest that's why they say you should use the newest, because they know it works
PlayingLikeAGenius said:
I don't think it is a problem but the devs often test their rooms with the newest that's why they say you should use the newest, because they know it works
Click to expand...
Click to collapse
Awesome! Thanks for the reply! Hopefully will be getting my hands on the 5!
H4X0R46 said:
Awesome! Thanks for the reply! Hopefully will be getting my hands on the 5!
Click to expand...
Click to collapse
Drivers: The OP3 when connected to the PC/Laptop creates a CD drive on the PC/Laptop. It contains all the drivers you need for adb to work. As Puddi Puddin said, the minimal drivers themselves work, the CD drive is there just in case you need it.
Firmware: Some custom ROMs refuse to work without the firmware recommended for it. So just go by the recommendations of the developer and remember to check the firmware when you change/update the ROM.
tnsmani said:
Drivers: The OP3 when connected to the PC/Laptop creates a CD drive on the PC/Laptop. It contains all the drivers you need for adb to work. As Puddi Puddin said, the minimal drivers themselves work, the CD drive is there just in case you need it.
Firmware: Some custom ROMs refuse to work without the firmware recommended for it. So just go by the recommendations of the developer and remember to check the firmware when you change/update the ROM.
Click to expand...
Click to collapse
Cool, to change the firmware, is it an img you flash with fastboot? What's the file name and command?
H4X0R46 said:
Cool, to change the firmware, is it an img you flash with fastboot? What's the file name and command?
Click to expand...
Click to collapse
It is a zip file. Check the thread for Collection of Firmware and Modems by Jamal (for OP3) here in XDA.
tnsmani said:
It is a zip file. Check the thread for Collection of Firmware and Modems by Jamal (for OP3) here in XDA.
Click to expand...
Click to collapse
Awesome thanks! Getting used to the way these phones work lol thanks a million!
Related
See attached for the developer version drivers (32bit) and flash app (RSDLite 6.1.4).
Unzip, install, ?, Profit
UPDATED to remove password on ZIP file. Sorry!
The zip archive is password protected it appears.
cellzealot said:
The zip archive is password protected it appears.
Click to expand...
Click to collapse
Sorry, Updated with a password free ZIP. Thanks for catching that.
Thanks but these drivers are 32bit and won't work with Win64. Here's a link to the Motorola drivers direct from Moto.
BTW, any chance of getting an SBF? Be nice to have a stock image to got back to :cyclops:
rooting
I got my droid razr m two days ago, and I am really interested in rooting it. I have never rooted before, so I know i have a lot to learn. I have read up on superoneclick and cryogenmod, but I cant find the phone listed there. I am assuming that is because its so new. Does anyone have any information that could get me started with rooting my phone?
zsouthpaw said:
I got my droid razr m two days ago, and I am really interested in rooting it. I have never rooted before, so I know i have a lot to learn. I have read up on superoneclick and cryogenmod, but I cant find the phone listed there. I am assuming that is because its so new. Does anyone have any information that could get me started with rooting my phone?
Click to expand...
Click to collapse
To my knowledge there is no root available at this current time for it and might not be.
Hey guys Im new to moto Im a adev coming from the galaxy s2 skyrocket and the verizon galaxy s3 ,so sorry if this is a stupid question but what do these drivers do ,are they able to unlock the bootloader ?
remf4i said:
Hey guys Im new to moto Im a adev coming from the galaxy s2 skyrocket and the verizon galaxy s3 ,so sorry if this is a stupid question but what do these drivers do ,are they able to unlock the bootloader ?
Click to expand...
Click to collapse
Nope, need a developer version at this point to have an unlocked bootloader. This is just the drivers from pre-release... the Retail release are nearly identical (Link above). This does however have the flashing app which will come in handy if you don't have a developer login to Moto Mobility.
compnird said:
Nope, need a developer version at this point to have an unlocked bootloader. This is just the drivers from pre-release... the Retail release are nearly identical (Link above). This does however have the flashing app which will come in handy if you don't have a developer login to Moto Mobility.
Click to expand...
Click to collapse
I see, thanks for the reply, once this is rooted and we have a recovery then I'll get to work on a ROM, oh yeah anyone having problems with their WiFi cutting out all the time?
Sent from my XT907 using xda premium
Just got RAZR m today. So my question is this device writable?
Sent from my XT907 using xda app-developers app
commuterbox said:
Just got RAZR m today. So my question is this device writable?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
The bootloader in unlockable for the developer edition as well as the international version. But not for the $99 version.
As for "writable" part, once we have root, you should be able to access your system partition.
http://androidadvices.com/root-motorola-razr-4g-lte-firmware-tutorial/
theabnormalone said:
http://androidadvices.com/root-motorola-razr-4g-lte-firmware-tutorial/
Click to expand...
Click to collapse
From the comments at the posted link this method does not work.
compnird said:
See attached for the developer version drivers (32bit) and flash app (RSDLite 6.1.4).
Unzip, install, ?, Profit
UPDATED to remove password on ZIP file. Sorry!
Click to expand...
Click to collapse
Could someone post 64 bit drivers please?
Driver Question
compnird - Cool to get straight USB drivers for RAZR M. Have had trouble with MDM on XP. Question - will these drivers apply to XP or just Win 7/8? My old flagship box is still on XP.
TIA,
SoftDad
Dang nobody gonna post the 64 bit drivers ? Can anyone convert the pre-release drivers to x64?
Thanx. Your a life saver!
These don't install on 64bit Windows 10.
Can someone point me in the right direction for the drivers I need? I can't find them anywhere.
Where I can download the firmware Sir?
Hello All,
I am running into a bizarre situation.
My XT907 has bad usb connector prints and I cannot connect it to computer to flash it using RDS etc.
It is on stock ROM (Not Rooted) and stuck on "Animated EYE"
"Wipe Data/ Factory reset" does not seem to work for me.
Nor It is getting update from the "SD CARD UPDATE"
Is there anyway i can use Update From SD card option (No Root)
I have Tried Many Stock Roms (Almost All Versions) using SD card, it only says
Android System Recovery <3e>
KDA20.62-15.1
--Install /sdcard ...
Finding Update Package...
Opening Update Package...
Verifying Update Package...
Installation Aborted.
Hello,
Any help would be appreciated. I'm not extremely comfortable yet with rooting, and as such, would love if someone could point me in the right direction to a proper tutorial on how to root my Pixel XL. I purchased it from Google directly, which has an unlocked bootloader. It is the N2G47E Build Number, and I OTA updated it to 7.1.2. I have a Windows PC on Windows 10 64 Professional, original cables, etc.
Thanks so much for any help, and I'm hoping this is possible.
1984world said:
Hello,
Any help would be appreciated. I'm not extremely comfortable yet with rooting, and as such, would love if someone could point me in the right direction to a proper tutorial on how to root my Pixel XL. I purchased it from Google directly, which has an unlocked bootloader. It is the N2G47E Build Number, and I OTA updated it to 7.1.2. I have a Windows PC on Windows 10 64 Professional, original cables, etc.
Thanks so much for any help, and I'm hoping this is possible.
Click to expand...
Click to collapse
Third post in the thread below, follow the part about setting up adb and fastboot. Skip the part about downloading the factory image and flashing it.
Just get the tools set up.
Then follow the second​ to last post in the same thread to root it.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
It is possible, sir.
All the answers you need should be here https://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
1984world said:
Hello,
Any help would be appreciated. I'm not extremely comfortable yet with rooting, and as such, would love if someone could point me in the right direction to a proper tutorial on how to root my Pixel XL. I purchased it from Google directly, which has an unlocked bootloader. It is the N2G47E Build Number, and I OTA updated it to 7.1.2. I have a Windows PC on Windows 10 64 Professional, original cables, etc.
Thanks so much for any help, and I'm hoping this is possible.
Click to expand...
Click to collapse
Why do you want to root?
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Why do you want to root?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I would like to block ads everywhere. That's a big one. I have used adaway in the past and liked it. I also like to learn the process. I've been jailbreaking iphones/ipods/ipads for years and am interested in learning more about rooting as it interests me. I also want to have more control over functions of the phone, and there have been a few apps and such that I liked in the past that I felt enhanced my phone (it was a galaxy s6).
my snapchat is still working now in 7.1.2 with root..didnt in 7.1.1
bobby janow said:
Why do you want to root?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Why would one NOT want to root?!
Sent from my Pixel XL using Tapatalk
335Deezl said:
Why would one NOT want to root?!
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Lots of reasons. Come on, you don't need me to lay it out for you. I'd be hard pressed to ever root again.
TonikJDK said:
Third post in the thread below, follow the part about setting up adb and fastboot. Skip the part about downloading the factory image and flashing it.
Just get the tools set up.
Then follow the second​ to last post in the same thread to root it.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm looking at the dates and it seems like the SuperSU has a version 3,4, and 5. which should I be using? I'm finding it all a bit confusing.
bobby janow said:
Lots of reasons. Come on, you don't need me to lay it out for you. I'd be hard pressed to ever root again.
Click to expand...
Click to collapse
Brother, I don't need you to lay out anything for me. I've been rooting since the OG Droid A855. That was probably when you were in grade school. I like a faster phone, better battery life, no ads, and endless customization. That's why I root. You want stock? Buy an iCrap.
Sent from my Pixel XL using Tapatalk
A week or so ago I used twrp.img rc1 with SR3-SuperSU-v2.79-SR3-20170114223742 and it worked just fine.
I did not flash twrp, just flashboot to it and flash su zip.
335Deezl said:
Brother, I don't need you to lay out anything for me. I've been rooting since the OG Droid A855. That was probably when you were in grade school. I like a faster phone, better battery life, no ads, and endless customization. That's why I root. You want stock? Buy an iCrap.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Are you 7.1.2? What methods/tutorial did you use (or can point the way towards) for me to root my Pixel XL? I would appreciate any help. Lots of the terms are very foreign to me and I'm attempting to follow the directions, but half the time I have to google what the instructions even mean. This is not my main device, so if I have to reset, etc. it's not the end of the world. Thanks so much!
It's all right here: https://forum.xda-developers.com/pi...to-unlock-root-flash-pixel-xl-t3507886/page24
Sent from my Pixel XL using Tapatalk
1984world said:
I'm looking at the dates and it seems like the SuperSU has a version 3,4, and 5. which should I be using? I'm finding it all a bit confusing.
Click to expand...
Click to collapse
Like my link said, 2.79 SR3
TonikJDK said:
Like my link said, 2.79 SR3
Click to expand...
Click to collapse
Ok, and how about the twrp? The instructions state to use the RC1 version, but there is now a RC2 version. Suggestions?
1984world said:
Ok, and how about the twrp? The instructions state to use the RC1 version, but there is now a RC2 version. Suggestions?
Click to expand...
Click to collapse
I used rc1 img (twrp-3.0.2-0-RC1-fastboot-marlin.img)
gordonlw said:
I used rc1 img (twrp-3.0.2-0-RC1-fastboot-marlin.img)
Click to expand...
Click to collapse
ok that helps. So I've installed ADB and platform tools and drivers. when i open a command windows to install twrp (fastboot boot path/to/twrp.img) it gives me the "cannot load : no such file or directory. not sure what im doing wrong with this, followed the instructions to the letter.
335Deezl said:
Brother, I don't need you to lay out anything for me. I've been rooting since the OG Droid A855. That was probably when you were in grade school. I like a faster phone, better battery life, no ads, and endless customization. That's why I root. You want stock? Buy an iCrap.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Brother? Yikes, I hope not. The question of why root was not directed at you so I'm not sure why you answered. The OP had already answered it. I don't care what you have done in the slightest. Your assumption of your maturity level due to your age leaves much to be desired as well.
There are many reasons not to root, I'll say it again. So if you don't know the reasons you might not know as much as you think you do. Don't make me lay it out for you. If you take a few minutes you will find a lot of others that used to root but find no need to any longer. The iPhone discussion has nothing to do with this neither does your denigration of a very capable phone. Where that came from we can only imagine. Oh yeah, age.
1984world said:
ok that helps. So I've installed ADB and platform tools and drivers. when i open a command windows to install twrp (fastboot boot path/to/twrp.img) it gives me the "cannot load : no such file or directory. not sure what im doing wrong with this, followed the instructions to the letter.
Click to expand...
Click to collapse
"path/to/" is where the files are located!
I create a folder at the root of c called "adb". go inside that folder and shift right click. that will give the option to open command prompt from that folder. then your adb commands are already in the correct folder so it would be adb fastboot twrp.img (if you renamed the img to twrp)
TonikJDK said:
Like my link said, 2.79 SR3
Click to expand...
Click to collapse
Ok, fair enough. I've done all of that. my only issue now, is how to do the follow through. The guide doesn't seem to be fully explanatory, or I'm simply not comprehending all the nuances of it.
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Very cool!
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Just watch what you flash and use anykernels, not boot images. The Pixel 2 bootchain isn't as fragile as you think once you flash TWRP into the ramdisk. Protect TWRP and you'll hopefully never need to fastboot from a companion device.
MishaalRahman said:
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Click to expand...
Click to collapse
YOLO.
The way I see it, there are two kinds of developers, the kind that need testers because they have no idea what they're doing, and the kind that test themselves, because they are the only ones that know what they're doing.
I'm about to yolo flash a taimen build I just made, it will most likely fail, but that log and debug info I get from it will be valuable lol.
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
jlee08517 said:
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
Click to expand...
Click to collapse
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Surge1223 said:
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Click to expand...
Click to collapse
I had a device that made use of that fastboot over tcp protocol ;p
Moto G3 Prototype. Comically, it was actually a boot mode with an extended LK (as in when I used a non-proto boot image, the feature was not operable).
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
TheSt33v said:
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
Click to expand...
Click to collapse
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
osm0sis said:
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
Click to expand...
Click to collapse
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
TheSt33v said:
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
Click to expand...
Click to collapse
Well you can try, but probably not then. You'll just need to use a newer device as the host device to flash from.
@Surge1223 I realize this is an older thread but I'm going to ask anyways because after searching around, most I can find are x64 files. I've ordered an arm based Chromebook, am I correct in that this is what's needed to get fastboot and adb working? Thanks
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
jcmm11 said:
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
Click to expand...
Click to collapse
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Surge1223 said:
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Click to expand...
Click to collapse
I normally wouldn't ask, and if you can't (for whatever reason) that's fine. But you did say you'd try to get this updated. New security patches are due out Monday and it would be real nice if I could apply them ?
If not, I'll live. Thanks, no matter what.
Surge1223 said:
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Click to expand...
Click to collapse
Sorry for bumping an old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Fe Mike said:
Sorry for bumping all old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Click to expand...
Click to collapse
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
cubzfan68 said:
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
Click to expand...
Click to collapse
It may, are you using fastboot from op on the phone from another arm device or a PC?
Fe Mike said:
It may, are you using fastboot from op on the phone from another arm device or a PC?
Click to expand...
Click to collapse
I use it from a pc
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.
I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and have accepted all normal OTA updates as of 9/8/22, you should be on C.19 firmware.
Assuming you have already unlocked your bootloader, you can safely upgrade to EU C.62 firmware found at:
OP9PRO_Android12_C62_EU_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
I completed this process while already on Nameless but it should work for others too. No more dodgy modules, hacked MSMDownloadTools or sorta working phones. Note, firmware and local updates are NOT the same. You are not cross-flashing to an entirely new software but ONLY required firmware modules for latest custom ROMs. Hope this helps!
P.S. if you receive any error while sideloading your new firmware, DO NOT unplug or reboot your phone. Repeat the process until it's completed successfully.
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
nextbigleap said:
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
Click to expand...
Click to collapse
That's exactly what I am saying, fastboot flash the firmware only and say goodbye to data issues.
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
MudaTrucka said:
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
Click to expand...
Click to collapse
No user data removed.
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
SaintZ93 said:
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
Click to expand...
Click to collapse
I will do my best!
Why does this work where the eu msm converter has problems with the modem? After you flash this firmware can you take future ota updates without modem issues as well?
The latest firmware from non-branded OnePlus 9 Pro is now available!
OP9PRO_Android12_C63_NA_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
This finally brings those of us on T-Mobile, especially closer to the bleeding edge.
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
rageoner said:
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
Click to expand...
Click to collapse
Of course, it's modified because OnePlus doesn't create firmware packages for our community. However, the files within the package are original dumps.
You can easily sideload this fix through your custom recovery using adb sideload OP9PRO_Android12_C63_NA_Firmware.zip for example.
Ok, one last question, are we able to take ota updates after doing the sideload? I know this is the latest firmware so there won't be any but in the future are we able to take ota?
Question:
1-what room is best for my LE2127 for daily use
2-Hasselblad camera exist a app
3-what TWRP are we using now
thanks in advance
Could someone please post steps to sideload Le2127 to EU / Global C.62EU / C.63NA No data loss ?
can I sideload this from t-mobile c.17? Also what recovery can I use? TWRP is for android 11
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
luckylui said:
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
Click to expand...
Click to collapse
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
MudaTrucka said:
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
Click to expand...
Click to collapse
Do the other option and go from there.
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Bulauski2005 said:
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Click to expand...
Click to collapse
You can't help folks that don't want to help themselves.