I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images
https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"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"
}
Sent from my Pixel 2 XL using Tapatalk
I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.
Damn Sir! Thank you very much for the help!
WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!
Related
I just got a used E980. idk what he's done to it. but appeared vanella. I tried rooting, from the proper thread with the right files. suposedly right for the e980. so I tried to just reboot recovery, but all i get is an android with a red triangle and an ! inside it of.
the error i get when trying to root is -
{
"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"
}
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
cougar214 said:
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
Click to expand...
Click to collapse
yeah i can't get into TWRP, or the other one. it keeps giving me dude with red !. version is jz054k.
I did a full wipe and install of an origonal build of the software, was able to root it sucesfully now. but still can't get into the bootloader menu. tried cammand line to tell it to boot into it, tried rom manager. no dice. just keep getting little dude. i remember seeing a thread about him, i don't know what he means :\
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
cougar214 said:
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
Click to expand...
Click to collapse
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Honestly, your best option is to wait for the kitkat update to hit in a month or so. You get what you're looking for in one stock update. Hassle free. That's what I'm doing. The more I learn about this phone, the more I am hesitant to flash anything to it. Mostly because there are so many variants for this phone. Everything can't be compatible so why risk it.
eviling said:
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2703029
Read the whole thing then you'll be ready to go
Its the kitkat Korean update, I'm using it on my e980 , pretty sweet
yeah i agree, i havn't found many rom's i like. ive found roms always fail after awhile. so idk. they always bloat up and start to fail than they need the update to be stable blah blah than your reinstalling all apps and backing **** up. idk, was just looking at what phones offer these days for modding but nothing seems to of changed. this phone inparticular is a rather unstable device none stock, seems to be allota issues and a good reason to have bootloader locked.
Un locking the bootloader only allows for custom kernels on any given device. In some cases you will get greater stability. But for the most part you will still have glitches, performance decreases, etc. because you are STILL flashing custom Roms. And in allot of cases your phone will go completely nuts because custom kernels have their glitches too. So in short, sometimes, Custom Rom=glitches. custom kernel=glitches. That all adds up to a totally unstable Rom. Keep in mind all devices are not the same. What runs great on his might crash your phone completely. Just my 2 cents....lol
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"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"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"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"
}
Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.
Yes please that would cut down a lot
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!
randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days
Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.
Yes - He should be allowed to root it again - He needs practice
fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.
First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good:
Have a decent understanding of how to unlock/root/xda, just want to make sure, so any help would be appreciated.
Still on 7.1.1, (Google edition? Bought on eBay and not really sure because oem unlock is greyed out, no Verizon apps though) wondering best way to get to android O/P with the bootloader unlocked. Should I OTA then try the Verizon unlock method? Or try the unlock method on 7.1.1 then flash a android O/P rom/modem/baseband etc? Got some reading to do....
Any other tips would be appreciated as well, thanks for your time.
{
"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"
}
So if your Button is greyed out... It's a Verizon variant.
https://www.facebook.com/IsMail.AmZdak reach out to that guy and donate what ever you can and ask if he can bootloader unlock your phone. it doesn't matter what version of Android you're on.
Once he unlock your bootloader proceed to downloading developer preview 4 and run flash all command.
Once it has finished flashing Android p the phone will then reboot let it get to the main screen and then reboot the phone and put into bootloader mode.
Download TW RP image and run Fastboot boot ( twrp image ) and wait for it to boot twrp. When you're computer reads the phone, drag and drop twrp installer into phone and the install. Reboot to recovery >> flash magisk >> boot up
You can use the Verizon method on 7.1.1 or newer as far as I know.
lafester said:
You can use the Verizon method on 7.1.1 or newer as far as I know.
Click to expand...
Click to collapse
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
lordodin912 said:
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
Click to expand...
Click to collapse
Are you on Verizon? The apps only load with their sim.
lafester said:
Are you on Verizon? The apps only load with their sim.
Click to expand...
Click to collapse
Yes on Verizon, still no apps, rebooted multiple times and updated all playstore apps......no vzw stuff anywhere (not complaining, ha) just seems odd.
Is it better to OTA update to 8 then unlock/root, or is there another way (flash rom/modem...etc over 7.1.1, might not play well with bootloader though, jw).
Thanks.
Screens for proof....
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
lordodin912 said:
Screens for proof....
Click to expand...
Click to collapse
lafester said:
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
Click to expand...
Click to collapse
Gotcha.
Edit: CID getter shows rom.boot.cid:[VZW_001], also checked verizon account, shows up as Pixel XL, not "non vzw device" which someone said it should say if it's google edition.
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Edit: Got root/twrp, no problems.
Thanks again.
lordodin912 said:
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Click to expand...
Click to collapse
Not sure if this was answered already, but no. The bootloader being locked is the only difference.