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
Related
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!
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Ericarthurc said:
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Click to expand...
Click to collapse
damn thanks for the reply. I am on stock but bootloader is unlocked.
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
From what ive read you can. But requires a full wipe of data.
This was possible for me to do before 8.1 was officially rolled out. I was on 8.1 developer preview, I wanted to go back to 8.0 to take advantage of the kernels which at the time we're only for 8.0, so I opted out of the developer preview with Google, they sent an ota to my device, it of course would not take as I was rooted, however the original factory image for 8.0 could be flashed through fastboot.
Yeah I did it to, but it takes a full wipe
jrbxx7 said:
From what ive read you can. But requires a full wipe of data.
Click to expand...
Click to collapse
mac796 said:
Yeah I did it to, but it takes a full wipe
Click to expand...
Click to collapse
Does this mean factory reset first then flash? or do i need to run some adb commands.
tvdang7 said:
Does this mean factory reset first then flash? or do i need to run some adb commands.
Click to expand...
Click to collapse
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
No you cannot. Not even with twrp
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
State.of.mind said:
No you cannot. Not even with twrp
Click to expand...
Click to collapse
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
imnuts said:
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Isn't that what the instructions provided by @PhoenixPath (below) are meant to do?
PhoenixPath said:
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
Click to expand...
Click to collapse
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
cognitivedissonance said:
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
Click to expand...
Click to collapse
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
cognitivedissonance said:
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
Click to expand...
Click to collapse
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
PhoenixPath said:
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
Click to expand...
Click to collapse
Interesting, I would've assumed the new USB C standard would've worked much more reliably than the older methods. I wonder what causes the instability like that. Anyway, thanks for the heads up.
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
Str0ntium said:
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
Click to expand...
Click to collapse
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
cognitivedissonance said:
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
Click to expand...
Click to collapse
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
PhoenixPath said:
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
Click to expand...
Click to collapse
Yeah, the slots thing and the "unlock_critical" are both new to me, coming from a Nexus 6P. I'm going to do a bit of additional reading to just try and wrap my head around exactly what the changes are and what the additional commands do. Thanks again!
cognitivedissonance said:
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
Click to expand...
Click to collapse
Basically, yeah. I flashed the image to both slots without booting to OS. Then flashed twrp, magisk, etc...
PhoenixPath said:
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
Click to expand...
Click to collapse
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
uicnren said:
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
Click to expand...
Click to collapse
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
PhoenixPath said:
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
Click to expand...
Click to collapse
Well, its not an easy process, for sure, which is why I know I am in the very small minority.
Also, at the very least, your Chromebook will need to support (and you'll have to enable) developer mode.
Most do adb/fastboot through 'Crouton". Check that out.
On the PixelBook it can be done natively, but it is not an easy thing to do, as I said above. PixelBooks come with adb/fastboot already on them (once your in developer mode) however, they are out of date and will not work with newer Pixel phones, so, you need to go through a lot of hoops to update them to the latest.
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.
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
granosalis said:
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
Click to expand...
Click to collapse
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
roirraW edor ehT said:
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
Click to expand...
Click to collapse
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
granosalis said:
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
Click to expand...
Click to collapse
You're welcome! It's at least 50/50 chance that it would be better to wait. I have no problem on the .017 December firmware, but plenty of folks do, and I haven't had much of a problem at all with any of the firmwares so far.
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
Because it fixes some things for some people.
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
granosalis said:
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
Click to expand...
Click to collapse
You'll have to allow the phone to boot up first since you'll need access to the OS to perform some commands on your PC. You can just allow the phone to boot and skip a lot of the setup process, only because flashing the most recent factory image will put you back to stock, AKA wipe your phone back to where it was when it left the factory, and then once the new image has been installed you can do a proper phone setup from scratch.
If you're not familiar with using terminal commands and don't want to run the risk of messing up your phone, I suggest you use the Android Flash Tool since it'll do everything for you and is fairly simple. Just connect your device over USB and visit the Android Flash Tool using the link below. Android Flash Tool works with any Web browser that supports WebUSB, such as Chrome or Edge. The Android Flash Tool guides you step-by-step through the process of flashing your device - there's no need to have tools installed, but you will need to unlock your device and enable USB Debugging from Developer Options.
I've provided a link on how to enable USB Debugging and Developer Options, here - https://source.android.com/setup/contribute/flash
To flash the latest January Stock image on your device, simply visit this link - https://flash.android.com/build/8030436?target=raven-user&signed
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
RetroTech07 said:
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
Click to expand...
Click to collapse
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
They do the same thing, however the android flash tool is much easier to use.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
I forced it on day one and I guess I was one of the lucky ones that didn't have any issues.
granosalis said:
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
Click to expand...
Click to collapse
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
RetroTech07 said:
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
Click to expand...
Click to collapse
No my phone should arrive in about 10 days if everything goes as planned.
It is not easy to take a P6P 256gb white from italy , this model, in fact, is not sold in europe for what I know.
While waiting I try to keep myself informed. It's been a long time since my Galaxy Nexus.
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here