Seems like that I would never make it to unlock it.:crying:
super0dd said:
Seems like that I would never make it to unlock it.:crying:
Click to expand...
Click to collapse
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!
sbdags said:
No not right now.
Remind me where you are getting stuck?
The tricky part is updating to 4.3 if you are on 4.2.2 and then you unlock, but if you are locked on 4.2.2 then just upgrade to 4.3 and then unlock, fastboot flash cwm and use my superuser zip to root. Easy!
Click to expand...
Click to collapse
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:
super0dd said:
All right, just let me tell you my whole story.
Someday I seemed to overcharge my tablet and thus broke the power management chip on the motherboard and then I found it stuck on the boot screen and was only able to boot to recovery. After I finally surrendered to it, I went to have Asus's guy replaced it a new motherboard, which took me like 230 bucks(much close to a new nexus 7).When I got my tablet back, it was already on 4.3 (10.26.1.18 CN), then I found it incapable to be unlocked. But I still want to root it anyway since the stock Chinese firmware is not even with GApps and lacks a lot of features that others possess. At least, I need Play Store!
Problem1: I am not sure if Asus's server records the existence or S/N of the current motherboard, which is most likely to incapacitate the unlock process.
Problem 2:
Code:
Unknown error occured, which may a network error
Please try later
That's the problem I meet all the time. I don't know if the official unlock tool is available for 4.3(the official webpage says that it is for 4.2.2 only and I can't find any other similar unlock tool for even ME302c:crying, as the firmware version is already 4.3 when I got it and it doesn't seem to be feasible fo downgrade it.
Problem 3: I have tried every root tools I know, and failed. Not possible to use the masterkey…
Thank you anyway.:victory:
Click to expand...
Click to collapse
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.
sbdags said:
Ah OK - the issue is Asus have replaced your motherboard so the mac address you are now supplying does not match the serial number of the device that they have in their database.
The ONLY way to proceed is to contact asus and get them to update their database with your new mac address - stating that you can't use their online web services like device tracking etc until they do so. They will eventually do it but if you can hold of a rep in Taiwan that will speed things up.
There is no other way.
Click to expand...
Click to collapse
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.
super0dd said:
Uh, do Asus guys have my MAC address? I am not sure.
Okay, I'll phone them tomorrow. It's quite a warm Sunday night now in China.
Thanks a lot.
Click to expand...
Click to collapse
Of course they do - it is tied to your wifi hardware.
I am sorry if this is the wrong place or forum.
I have an HTC 8XT on an MVNO of Sprint. Sprint apparently seems to be withholding a firmware update that would allow this phone to update to 8.1, Sprint 8XTs are running 8.1, but not a single 8XT on my MVNO has gotten it yet.
The current firmware I have is 3030.00.10008.651.
According to HTC the latest is 3030.00.31009.651.
I have taken this phone off my MVNO and left it in a drawer for several months hoping that it would roll off whatever database it might be in. I tried to factory reset and then let it update it over wifi (I know Lumias can do that).
It still says no update found. I chatted with an HTC rep online and reading between the lines, he seemed well aware of Sprint's shenanigans. He hinted that ROMS were 'out there' and an updated ROM, even if it weren't the latest, might be enough to trigger an update. I started my Google Fu. Nothing.
Then I read the FAQ in this forum that said if I needed an HTC ROM I was out of luck.
I know enough about flashing and rooting to be dangerous to my phone . This is not my daily phone, but it's frustrating to buy a device that says "ready for 8.1" and then not be able to roam or send MMS. I'm willing to try some warranty voiding behaviors to update it.
All that to say, is there anything else I can try? Again, apologies if this is the wrong forum. I did try a thread search and saw some close topics, but nothing like this.
Thanks
Well, the simple question is "have you tried the Developer Preview program?" because that bypasses the MO gating when your phone gets updated. Developer-unlock your phone (you don't have to sideload anything, the app just checks to see if you're unlocked), install Preview for Developers from the Store (free app from Microsoft), run it, and enable the installation of preview releases. That *should* let your phone get any relevant updates.
If that doesn't work, then I can't help you any further; I'm not a ROM guy.
GoodDayToDie said:
Well, the simple question is "have you tried the Developer Preview program?" because that bypasses the MO gating when your phone gets updated. Developer-unlock your phone (you don't have to sideload anything, the app just checks to see if you're unlocked), install Preview for Developers from the Store (free app from Microsoft), run it, and enable the installation of preview releases. That *should* let your phone get any relevant updates.
If that doesn't work, then I can't help you any further; I'm not a ROM guy.
Click to expand...
Click to collapse
Thanks for your reply.
I have been enrolled in the Developer Preview and have never gotten an update on this phone. I think I got this phone shortly after 8.1 was pulled from the DP due to the WiFi issue. Then I read on some Sprint boards that those *with* the Developer Preview were having issues installing the 8.1 when it was rolled out, so I wiped the phone. It has been several weeks since I tried Developer Preview on this phone. I thought it was on to WP10 and it wouldn't help me much.
Still, can't hurt to try to install it one more time, but I am not hopeful.
Thanks again for your time.
Edit: I think in my earlier attempts I missed the registration and unlocking of my phone. Trying that now.
Edit 2: Now it seems that sometime in May, Microsoft shut down the process for unlocking 8.0 phones with SDK
You might try to unlock the phone with the Chinese utility, but I am not sure that developer preview program really checks if your phone is unlocked. Is there a new firmware for your model in navifirm?
Lanex777 said:
You might try to unlock the phone with the Chinese utility, but I am not sure that developer preview program really checks if your phone is unlocked. Is there a new firmware for your model in navifirm?
Click to expand...
Click to collapse
My phone is made by HTC. Isn't navifirm exclusively Nokia?
I had kept my bootloader unlocked for flashing new ROMs but unfortunately i lost it on train and now i can understand that the theif can easily flash a new rom and so i can never retrive my device as far as i understood that i have to keep my bootloader locked but this means that i have to unlock and relock my bootloader each time i want to flash a new rom so this is very problematic for losing internal data too every time.
Also i don't have a job else i would have brought a new OP3T. I hope that in future OP can introduce some hardwire based tracking for lost devices , what do you people suggest?
samwidd said:
I had kept my bootloader unlocked for flashing new ROMs but unfortunately i lost it on train and now i can understand that the theif can easily flash a new rom and so i can never retrive my device as far as i understood that i have to keep my bootloader locked but this means that i have to unlock and relock my bootloader each time i want to flash a new rom so this is very problematic for losing internal data too every time.
Also i don't have a job else i would have brought a new OP3T. I hope that in future OP can introduce some hardwire based tracking for lost devices , what do you people suggest?
Click to expand...
Click to collapse
I suggest that if the thief is able to flash a new ROM, he will be perfectly able to open the bootloader. So I recommend that you do not worry about having the bootloader open.
As for the tracking system, I think Google has already developed certain functions aimed at this use. When I have time I will investigate about this topic and update this post.
Please, be awere.
idcampo95 said:
I suggest that if the thief is able to flash a new ROM, he will be perfectly able to open the bootloader. So I recommend that you do not worry about having the bootloader open.
As for the tracking system, I think Google has already developed certain functions aimed at this use. When I have time I will investigate about this topic and update this post.
Please, be awere.
Click to expand...
Click to collapse
Try Google device manager. Thats the tracking tool you searching for. ?
not a big deal to reset FRP. Samsung and LG FRP takes only few minutes to be removed with z3x box. i think even stock rom have some bugs to bypass FRP. Best way is not to loose your phone.
It won't help you now, but take a screenshot of your imei, then back it up to your photos. If your phone is lost or stolen report it and depending on what country you live in, it will be black listed. Then it won't work on any carrier, no matter which rom is flashed.
Bjarne73 said:
Try Google device manager. Thats the tracking tool you searching for.
Click to expand...
Click to collapse
Since I had kept my bootloader unlocked I believe that can easily flash a new rom so Android device manager won't be useful at all
Jowhee said:
It won't help you now, but take a screenshot of your imei, then back it up to your photos. If your phone is lost or stolen report it and depending on what country you live in, it will be black listed. Then it won't work on any carrier, no matter which rom is flashed.
Click to expand...
Click to collapse
Ya I know that I have already submitted FIR in police with the IMEI number but I believe these days they remove all the parts and sell the parts differently so very less chance in recovery
acmerw said:
not a big deal to reset FRP. Samsung and LG FRP takes only few minutes to be removed with z3x box. i think even stock rom have some bugs to bypass FRP. Best way is not to loose your phone.
Click to expand...
Click to collapse
Ya I know but if there is very strong FRP in apple iPhone devices i hope it comes to Android too
I'm not really sure what I'm doing, I changed my country code from "demo" to eu and I'm on EVA-L09C432B182. There's so many different versions and I don't know which is good or even compatible. What would be the next thing you guys would do in order to get the most from my phone?
Edit - I just jumped in at the deep end and everything wen't well, I'm now on Nougat with emui 5.0, if you're in the same boat as I was, I used the Huawei Update in the second post of this thread: https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754"]https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754
worked a bloomin treat for me!
C900 country demo ?
Thorpy4p said:
I'm not really sure what I'm doing, I changed my country code from "demo" to eu and I'm on EVA-L09C432B182. There's so many different versions and I don't know which is good or even compatible. What would be the next thing you guys would do in order to get the most from my phone?
Edit - I just jumped in at the deep end and everything wen't well, I'm now on Nougat with emui 5.0, if you're in the same boat as I was, I used the Huawei Update in the second post of this thread: https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754"]https://forum.xda-developers.com/p9/help/p9-7-0-nougat-update-eva-lo9-b182-t3539754
worked a bloomin treat for me!
Click to expand...
Click to collapse
I have an eva-L09 with C900B190 and have country "demo" ??
I read a lot of posts how to get from the C900B190 to a Rom that has ota updates.
Before I start and because I am a bit of a noob I want to be absolutely sure I get all steps correct...please help me out and confirm/correct this
1) set develloper usb debugging
2) make sure phone connects to pc
3) install latest twrp
4) unlock boot loader with tool (https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358)
5) make note of unlock code
6) use twrp to flash B136 (still have to find zip)
do I get ota to android 7 or I have to flash latest Rom meself (what is the best version for eva-L09?)
After that can I lock the boot loader and stay on android 7 or will the phone reset with locking and revert to android 6 again?
Thanks for helping
Contacted huawei, they were very helpful I will probably go to the service center to hopefully reset my phone to receive updates.
I also asked for an unlock code in case I need a plan B.
djaccob said:
Contacted huawei, they were very helpful I will probably go to the service center to hopefully reset my phone to receive updates.
I also asked for an unlock code in case I need a plan B.
Click to expand...
Click to collapse
Seems I have no warranty (I got the phone from a friend and have no papers or anything) and have to pay for service centre. So I will try unlocking myself...
If anyone can help me out with all the steps in the right order I would be very grateful.
!!! This is a HIGH RISK method of performing any form of modification, if you are on a T-Mobile ne2217 !!!
There are unidentified files that your device might have conflict with, and cause a bootloop!
Proceed at your own risk! You have been warned!
OK, first lemme explain. The NE2217 (10 pro) itself does not have any special restrictions on it, unlike the CPH 2419 (10T) which is an exclusive T-Mobile variant. My guide on region swapping the CPH2419 (10T, link below) is still valid for the NE2217 (US- NA) . But there are conditions required or you will enter an infinite bootloop which becomes un-recoverable, without an edl flash. I do not have the specifics as to exactly which partitions cause this, but basically the bottom line is, IF YOU HAVE NOT UNLOCKED YOUR BOOTLOADER, EVEN IF YOU ARE SIM UNLOCKED, do not attempt to region swap.
There are a couple of partitions that are specially locked, that ONLY become write capable using the fastboot command, "Unlock Critical". Without a Bootloader unlock, the Oxygen Updater/Local Update programs, CANNOT make the needed changes to the Kernel, as well as these other important partitions, which have instructions that implicitly block changing to other regions. I cannot confirm if this exists in other countries with carrier locks, but i do know for a fact that T-Mobile has this enforced on all of the 10 Pro (ne2217) purchased through them.
As mentioned in previous threads that ive replied in, I suspected that the apps Oxygen Updater and Local Update, do not have the permissions capable to make direct changes to the boot.img, or recovery.img directly, primarily because those partitons cannot be altered while the system is currently running. These images can only be altered through Fastboot, or EDL thus the need for an MSM Tool if you cannot unlock your bootloader via conventional methods. So what happens is upon "Pre-boot" those special instructions i spoke of, take authority and put the carrier specific files, into an untouchable state that are locked behind the USERDATA partition, so these applications just copy the updated files to the inactive partition and performs the changes during the next boot, and even a hard wipe factory reset does not have the authority to erase the carrier instructions. The only way they are removed is by Unlocking your Bootloader! When you do that, the Qualcomm Processor has an embedded command, which is required to ERASE the entire Userdata partition, to protect the encrypted files protected by the bootloader lock! You can read about that by googling "Qualcomm Bootloader Unlocking".
Hope that makes sense to the majority of you. So again, the ONLY requirement for you to be able to go from 'ne2217', to any other fw is YOUR BOOTLOADER MUST BE UNLOCKED!
Failure to follow that one requirement will indeed force your device into an unusable, infinite bootloop, which can be resolved only by an EDL flash, which as of right now we do not have the tools that can perform this on CONSUMER level. You will have to RMA, your device, or go thru third party channels, which in itself is very risky, and puts you at risk of viruses/malware/wormholes/zombie-apocalypse because you must give someone full access to your computer remotely, and pray that the person only does what you requested. (NOT IDEAL).
Now if you're on a T-Mobile locked device, you are NOT hopeless... as I am on a T-Mobile locked device, and i am now bootloader unlocked as well! These two conditions are independent of each other, but trust me when i tell you that YOU DO NOT WANT TO GO THRU WHAT I HAVE EXPERIENCED, IN ORDER TO REACH THIS GOAL!
In so I will not publicly disclose how i was able to enter the real Fastboot Mode, so that i could pull the unlock code needed to request the unlock token from T-mobile.
(If you are so inclined to do this that you are willing to forgo ALL precautions and risk the possibility of bricking your device, or you have already landed yourself in an unrecoverable bootloop state, and are willing to try ANYTHING, you can join Bootloopers Anonymous, by clickiing it, and drop a message. This is a brand new telegram channel, and i will try to watch it for your requests. And again i strongly advise that you DO NOT embark on MY adventure, but if Unlocked Bootloader by Any Means Necessary is your ultimate goal, and nothing less is acceptable, i will try to help you achieve it... *** YOUR DEVICE WILL ENTER A COMPLETELY UNUSABLE STATE FOR A MINIMUM OF 7 DAYS!! *** but bear in mind that EVEN IF you have to use my method, you will be still subject to the 7-day waiting period outlined by OnePlus company policy. No one can overcome that, as the unlock token comes thru a separate division of Oppo/Oneplus that only generates the token through an automated request which is pushed after the expiration of 7 full days (1-week) has passed. YOU HAVE BEEN WARNED!)
The 10-Pro doesn't require the "In-Depth Testing" app to get your BL unlocked. That said, it also does not mean that OPPO has not designed one for this device because indeed they have. That application is individually encoded with device specifications so that only devices and regions EXPRESSLY AUTHORIZED by Oppo, can submit a request to unlock. DO NOT TRY sideloading any "In Depth Testing" apk floating around on the internet, as these can be altered to contain malware or worse, and then if your device becomes corrupted by it, Oppo can deny you an RMA on your device, thus charging you for the repair as there are warnings that you must acknowledge to even run the app, and attempting to circumvent the safeguards that this app already has in place is considered a violation of ToS.
If OPPO adds your device/region to the list of allowed devices, you will be able to download this application through OFFICIAL channels, and it will be made known to the public.
Once you are completely knowledgeable that your BL has indeed been fully unlocked, you can proceed to follow the instructions in the link to my guide below. The guide is for the CPH2419 (10T), but the instructions are completely compatible with the 10 Pro entire series, assuming your BL is unlocked. On the 10T this is not a requirement, and i honestly do not understand why this enforcement was put into our 10 Pro model, released almost a year earlier. Probably just an oversight by T-Mobile which might be corrected in future builds.
How to use Oxygen Updater + Local Update apks to switch regions.
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
again, what most ppl are failing to do is follow my guide exactly as i defined. The VERY 1st thing you MUST DO... prior to unlocking the Bootloader... Prior to even downloading ANY rollback packages is, you MUST go and Download ANY of the Android 13 beta updates that are available in Oxygen updater. Turn on advanced mode, and select the whichever model you prefer... Its actually best to choose the region you plan on swapping to, for easier transition with the rollback package. IMHO i would always pick the EU model whenever attempting this, simply because that one usually has more bands available. But the main idea behind this is to make the phone, first BREAK the connection it has with T-Mobile's custom kernel, and modem... which is done just by upgrading to an Android 13 beta, as T-Mobile does not EVER release any beta builds, so by doing an actual OS upgrade, your phone must load the OS kernel, and several other partitions/files which i am sure that T-Mobile has branded in the 2217. Upgrading to a newer OS will without a doubt overwrite the carrier locked files, because the Upgrade comes from a higher authority in the chain of trust. Until TMO releases an update, then this is a requirement so that the rollback package of that region can safely downgrade the files, in their correct partitions. If you download a beta 13 thru oxygen updater, you can local update flash it, without problem. I did it myself to several demo devices at Tmobile stores here in Texas to test the technique, after i bricked mine by using a rollback package first!
Remember the 2217 is a T-Mobile EXCLUSIVE! No other carrier may sell this same model... but ALL of the internals are the exact same, and as im sure we are all well aware of, T-Mobile doesnt have the fastest adaptations when it comes to OS updates.
But there are several key identifiers which point to a custom made BL, Kernel, and Modem: 1. The build for all T-Mobile versions is on a revision that no other model has released... This alone could cause BL because if you flash a build that is older than the one you have currently, several files have anti-downgrade measures built into them. This is why we need the signed rollback packages to downgrade. But even if OPPO signed a rollback, unless they released one with T-Mobiles file specs, then anything you flash can create a conflict with an existing file... BL! But i know of about 13 ppl who have attempted my method, plus i just did another one myself last night for someone who contacted me and offered to compensate me royally if i would meet them since we were local logistically. 2. AFAIK, when installing a different rom to a device, you cannot downgrade the modem version. I know this is apparent with Samsung... as if you try to flash a rom with a lower modem version, it usually bricks, and you have to use odin to flash the newer modem back, in order to boot. Again this is taken care of by installing the NEWEST beta for Android 13, unless you had my situation which is, my phone CAME WITH updated security, and build already installed for October 2022. I havent heard of anyone who has said they even have the option to update theirs past August. So new purchases have to be careful. T-mobile sold mine with a blocked Fastboot, that doesnt respond to the button combo. Which clearly identifies they modified the recovery partition. 3. E-fuses have become a staple in Android devices for the past 5+ years.
Sure we have not heard of anything being in the T-mobile fw... but also who here can say that they have a FULL BUILD of the Tmo fw to examine? No one.... there is a generic 2217 build floating around that claims to be official, yet it is the ONLY build that does not have an OTA formatted file structure. All the 10 Pro OTA have been in payload.bin format, yet this happens to come only as a decrypted OFP, or a compressed OFP. *** OPPO is not directly supporting the 10 Pro 2217 or 10 T 2419 ! As these are proprietary T-Mobile builds. This is why you cannot find either of those models fw in the Oppo repository. So if OPPO doesnt release builds for TMO, then how exactly did an "Official 'OFP' for 2217" get released? *** OFP is an Official OPPO format for all the OPPO model phones. 10 Pro is still branded Oneplus, thus just about any OFP file you find in the wild, is almost 100% guaranteed NOT to be an official released build for our phones. Every package for this and the 10T that they have OFFICIALLY released, has been in Payload.bin format, because they havent released any full images yet! So in theory, who's to say that TMO didnt place an efuse into their specific model? Its only code, and if set, then it could have been burned during the initial release, or a later update, like AMAZON did with updates to the Firestick/FireTV devices, which would ONLY allow newer updates to certain files in THEIR build. That would totally explain a bootloop, because the rollback packages all push you back to 11_A.013 .... that build is from Feb-March 2022. Rolling back would almost guarantee that some files are overwritten with older components, which would cause a brick by e-fuse standards. We had to be lucky enough to catch it early in the FIrestick forum, to stop ppl from installing the update. Everyone who did, had their ability to unlock/load custom fw to their devices blocked, and there is still today no way to circumvent it. Sure new methods to mod became available, but only minimal changes, cuz the e-fuse blocked downgrading to exploitable builds. Since TMO has gone this far to stop us from modifying this phone, you can bet solidly on the fact that they have several safeguards in place to protect their investment.
Now im not trying to discourage anyone or discredit anything anyone has said or experienced regarding this phone, but look at the NUMEROUS unanswered replies to handfuls of problems that only happen to 1 or 2 ppl... they all have the same final result, but its astounding how many different scenarios ppl have found, that no one else has experienced, yet it leads to another bricked device. If this problem was rampant among a significant number of users, and it was triggered by the exact same scenario, then TMO would have to address it with an update... But all we know for sure is that there is some file(s) that is not compatible with any other model except the 2217. Til we have an EXACT culprit identified, all we can do is speculate, which is why I am going to re-label this as HIGH RISK in the OP. It has about a 40-50% chance of causing a bootloop, and about a 10% chance to leave your device unresponsive! There have been several released guides for other devices that have close to the same success rate / risk factor. All i can do is share what I have done, and what i know from personal exp.
Im sorry if anyone lands themselves on the wrong side of that equation, but it is a risk that only you can decide if its worth taking. For me, that answer is and always will be YES because i will not own a device that i do not OWN! For others this may be a touch more out of their league, and if thats true they should steer clear, until I or another user can get hold of an official TMO OTA, to examine the diff files in each.
****** Now all of that being said.... if ANYONE wishes to contribute to finding a solution to this dumpster fire, I am not asking for donations.... What i am asking, is for SOMEONE who might have a T-Mobile 10Pro on the release build, or any build PRIOR to 11_A.13 and is looking to help, we NEED an exact copy of an OTA update that might be sitting in your notifications. All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot. No loss to you, but EXTREMELY HELPFUL to us, because we will have something from TMO to work with, which may give us a clue as to what we need to remove from the updater script ! *******
and FYI the signatures used to sign some of the OTA we already have, are already deciphered and as such can be used to create new signatures after making some changes to the respective regions package. But to make having these be of any value, we need to know what to take out or change in the manifest, that will prevent alterations of the files causing bootloops. If anyone can help with an upload of a TMO-OTA please share publicly or dm myself or one of the other devs who have expressed interest in this issue.
Thanks
I can probably pull the update from my wifes phone. She never updates anything. I did get my 10 pro to boot to android 13 but everything just says its disabled. This is only the 3rd phone ive done this with so ill warranty another one if i have to lol.
supercobaltss said:
EDIT: Local Update downgrade it currently installing
No Go, The update installed and downgraded but it just loads to the welcome screen and crashes and boot loops
Click to expand...
Click to collapse
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
GuyInDogSuit said:
Yup, this happened to me as well. Setup wizard crashes before I even get very far in it, and I've wiped multiple times trying to complete it somehow.
Click to expand...
Click to collapse
Ive tried to convert multiple different ways. Upgrading to 13 basically screws you with the disabled apps BS, Downgrading just crashes the device. Either way its broken. I've went through 3 devices now messing around.
So I guess it's time to replace it, then? Crap.
GuyInDogSuit said:
So I guess it's time to replace it, then? Crap.
Click to expand...
Click to collapse
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
FML.
I've gotten it working for the most part, but what's most concerning is that there's no IMEI. And it doesn't charge or even acknowledge the cable. Fantastic.
jeffsga88 said:
Start a RMA on OnePlus website, don't go through T-Mobile. They will have you send in phone and then either reflash your phone and send it back or just send you a new phone which is what they did when I had to do it. All that bs about voiding warranty when unlocking bootloader is just that, bs. They fix or replace without any issues but you have to go through OnePlus.
Click to expand...
Click to collapse
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
GuyInDogSuit said:
I can't even request an RMA as I don't have an IMEI to provide. It's blank in the phone. I think I'm screwed. Or try T-Mobile. Dunno. This sucks.
Click to expand...
Click to collapse
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
jeffsga88 said:
The T-Mobile version has your IMEI sketched into the back cover of your phone. You should be able to use that.
Click to expand...
Click to collapse
Oh. Uh.... completely forgotten about that.
I just updated to Android 13 on the TMO NE2217, device not unlocked, still financed. And now have the option to unlock the BL.
beatbreakee said:
All updates download to the /sdcard/ partition of your phone in a folder that is accessible without root permissions. If you accept the download for the update, and DONT begin the install immediately, you can locate and pull that OTA to your computer, then delete the file from your phone, and it will cancel the update on reboot.
Click to expand...
Click to collapse
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
deleted
psm321 said:
Is this still useful, with the NE2217_11_C.26 update? And either way, how can I delete it? I couldn't find anything big in /sdcard. Thanks!
Click to expand...
Click to collapse
^
^
^
^
^
THIS Please my phone ignored my saying no and next reboot the damn thing will go off on me ... so frustrating that even when you set the darn thing to OFF on auto update and such it STILL does this BS...
Damn TMobile and their special lock junk UGH ...
anyway ... please can one direct with a screen shot and file manager they used to find this file so I can delete the thing? ... I have tried to find it and struck out ... but having got the notification today and the Oxygen app is showing 'REBOOT' instead of 'resume' when I ignored the update previously has me thinking if I reboot I will see android 13 pop up and in this case means I will lose my whoop as something with it breaks pairing my wearable ... whoop has offered no timetable for a fix