So here is the thing: I'm from Brazil, and HTC does not sell devices here anymore. I ended up buying an AT&T HTC One M8 from Amazon - a friend of mine brought it for me.
I had to unlock it to use with the carriers around here. I have been using the device just fine for months. For some reason, my device never updated - it was always at Kitkat 4.4.2. This week I decided to try to fully unlock and put a ROM in the M8 to get the most recent OS. I went for the ARDH, the most recent one - with Android 5.0 and Sense 7.
I used Sunshine to bootload and s-off my device. Everything worked perfectly and then I installed the ARDH ROM. However there is one small problem that I stumbled upon since then: my wifi, from time to time, just stops working, and usually comes back when I restart or turn off/on my device. It usually works fine for a few hours, and then just suddenly stops working.
Can anyone help me with this problem? I read some articles saying that maybe the problem is related to the OS not being updated to 4.4.4., but I'm not sure how I could go back now. Can I just download the ROM in HTC website and try to install it over the current one?
I humbly ask of you to try and explain things as easily as possible, since I'm not too familiar with "jargons"
Change your cid to BS_US001,BS_US002 And flash developer version ruu...no need to change mid as they are the same device and then youll have a clean device,no carrier bloat from ATT AND get your updates from HTC. You will never get updates from ATT due to not being on their network.
haimondlafis said:
So here is the thing: I'm from Brazil, and HTC does not sell devices here anymore. I ended up buying an AT&T HTC One M8 from Amazon - a friend of mine brought it for me.
I had to unlock it to use with the carriers around here. I have been using the device just fine for months. For some reason, my device never updated - it was always at Kitkat 4.4.2. This week I decided to try to fully unlock and put a ROM in the M8 to get the most recent OS. I went for the ARDH, the most recent one - with Android 5.0 and Sense 7.
I used Sunshine to bootload and s-off my device. Everything worked perfectly and then I installed the ARDH ROM. However there is one small problem that I stumbled upon since then: my wifi, from time to time, just stops working, and usually comes back when I restart or turn off/on my device. It usually works fine for a few hours, and then just suddenly stops working.
Can anyone help me with this problem? I read some articles saying that maybe the problem is related to the OS not being updated to 4.4.4., but I'm not sure how I could go back now. Can I just download the ROM in HTC website and try to install it over the current one?
I humbly ask of you to try and explain things as easily as possible, since I'm not too familiar with "jargons"
Click to expand...
Click to collapse
Thank you for your help. Unfortunately, I did not understand what you asked for me to do - like I said, I'm not too familiar with the names.
Could you maybe try to explain a few steps?
haimondlafis said:
Thank you for your help. Unfortunately, I did not understand what you asked for me to do - like I said, I'm not too familiar with the names.
Could you maybe try to explain a few steps?
Click to expand...
Click to collapse
S-OFF ONLY! How to get supercid
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111" (has to be 8 one's)
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
Be warned you can do some bad things to your phone with super cid if you don't know what you're doing. I'd head over to the international forum for the m8 and do some reading up on it.
Credit to: skulldreamz at http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Related
Hi all,
I've spent a rather frustrating week or so in the throes of searching Google and XDA to figure out how to get my brand new RS988 upgraded to the 21c software version on Nougat. Here's what I've done so far:
-Check for OTA updates using the OS. No dice...it went from 11a to 11c and will not find any further updates.
-Use LG Bridge to try to update the software. No dice. The software tries to get the current OS version and then says "cannot find operating system version" and won't contact home base to get the new files.
-Reboot into boot loader to install TWRP. No dice...the phone will not reboot into the boot loader for some reason. I've tried using both the ADB method of "adb reboot bootloader" and "adb reboot-bootloader", but both just have it reboot into the full OS. I've also tried powering on the phone while holding the volume down button, to no avail.
-All root and TWRP methods, and even getting the official bootloader unlock require booting into the boot loader
The one thing I *have* been able to get to work was re-flashing a KDZ of the RS98811c software from autoprime's linked repository.
As best as I can tell, I am stuck. Without being able to install TWRP via the boot loader I don't know how to update the software. Please help me figure this out!
Edit: additional device info added
Android version: 6.0.1, 2016-07-01 security patch
Baseband version: MPSS.TH.2.0.c1.4-00010-M8996FAAAANAZM-1.43591.5
Kernel: 3.18.20
Build: MMB29M
Configuration: F15.LGE.RS988.0
Software version: RS98811c
Security software: MDF v2.0 Release 1
Thanks!
Use lg up
It's possible that you have the RS988.BPT version (Brightpoint), which only got updated to 11h, I believe. I sent in a RS988.USA version, and they swapped for a new BPT motherboard. I've since sent it back yet again to get that resolved.
It appears to be a Tracfone Wireless version, according to the box, at least. It was supposed to be new, not refurb, so fingers crossed that's all good as well. Even if it was the Brightpoint version, wouldn't that have been fixed when I flashed the USA stock ROM?
I also don't see how to use LG UP to reboot into boot loader mode. It only shows me the phone, with nothing clickable, and a selection of 4 processes: refurbish, upgrade, phonesetting, and FOTA upgrade. Not wanting to mess up my phone, I am trying to be cautious about just trying either of the latter two options. Especially without a file there. Thoughts?
You did unlock the bootloader am I correct?
Matthew_Jay said:
You did unlock the bootloader am I correct?
Click to expand...
Click to collapse
Nope. I can't get into the bootloader (unless I've totally missed a method to do that). Even the instructions on LG's website pre-suppose that you can enter the bootloader. Step 9 on their bootloader unlock instructions say:
9. Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Click to expand...
Click to collapse
Unfortunately, issuing that command simply reboots the phone without a bootloader in sight. Any commands issued by fastboot after the "adb reboot bootloader" command just sit there saying "waiting for device". I think if I could get this far, the excellent instructions elsewhere on these forums would have me sorted the rest of the way, since then I could use TWRP to flash a more recent OS version. Thus far, it's only LG UP which works, which also requires a .KDZ file, but I can't find one for any version > 11c.
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
AdamDG said:
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
Click to expand...
Click to collapse
Simple answer is "You can't". I am in the same boat, stuck on 11c with no OTAs in sight. The ability to boot into the bootloader wasn't added until a later version (11h, I think?) So until/unless LG releases a KDZ of one of the later versions, you (and I) are out of luck.
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
AdamDG said:
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
Click to expand...
Click to collapse
Hey AdamDG, were you able to solve your issue? I am stuck with the same situation and asinine LG folks won't help me out because Total Wireless/Tracfone are supposed to take care of the matter. But the latter are not responsible for software updates because they are MVNOs and don't (need to) care.
Truly jokers, but more importantly, taking customers for a s(laughter) ride!
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hello,
I'm new to using this website, just made this account like 20 minutes ago. I'm not sure where to put this exactly so I'll just do me, and somebody will give a hand.
Anyways, I was attempting to root my LG Tribute HD about all day today and just one thing has stopped me is that the OEM Unlock doesn't seem to work. I know what it's suppose to do but its just not rebooting to it when I type from command prompt: adb reboot bootloader. It simply just comes back to the everyday-screen I interact with. I'm not sure what I'm doing wrong, really but it seems like it doesn't have a bootloader when there is an OEM Unlock option. I haven't gotten pass the first step yet to rooting. I wanted to get TWRP as a recovery, but I just can't it seems. I'm also not sure if I am the only one with this problem. Would greatly appreciate some help with this.
- Sleeper Johns
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working
Ok , lemme cover my bases here... OnePlus 10t, Android 12, T Mobile. .
I have usb debugging on, oem unlock on, and device appears in ADB ... Newest platform tools, updated drivers.... When I run 'adb reboot bootloader', the phone shuts off, then I see 'fastboot mode' for like half a second , and it goes off and boots up normal. I can enter fastbootd .. but regular fastboot causes instant reboot! Can ANYONE help me with what I need to do? You can't unlock bootloader in fastbootd... So I need help figuring out how to make it NOT kick out of fastboot when I enter the command. (Usb 2.0)
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
I haven't heard about this before, is it a T-Mobile only thing? That seems really bad for oppo to do that...
Hurt Copain said:
OPPO locked the bootloader permanently. They do this on the find series as well.. basically bootloader mode is disabled.
Click to expand...
Click to collapse
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
beatbreakee said:
ok , so how then can i either re activate this mode or root this device? because that is a deal breaker for me! I wont keep the ONLY model of this phone that has Fastboot disabled, and therefore is unable to be rooted! I have about 8 days left to package back up and send back to Tmobile for refund! Now i can fully reach EDL mode, so if there is a software that can let me flash the EU Unlocked FW , then please direct me. I saw some success written about here with the new MSM, but it requires some authentication. I am 100% fully committed to any method, no matter how complex, to rectify this travesty! The ONLY reason i jumped from Samsung to OnePlus years ago was because of how Developer friendly they were... Easy unlock of bootloader... yadda yadda! Now the curse of Beatbreaker has struck again, and the impossible has happened in that SAMSUNG bootloaders are now easily unlockable via purchased token... and Oneplus has become part of an asshat dictatorship.
Please advise if there is ANYONE here who can either help me with this situation, or can direct me to instructions/software that can flip this situation around. I mean, the fact that Fastbootd reports my device in "Fastboot" when running 'Fastboot devices' ... AND that even if only for a glimpse of a second i can see FASTBOOT MODE, before it kicks me out and reboots, tells me that there must be some glitch, exploit, or workaround that can re-enable it! I only state this because some phone companies (carriers) like Metropcs were pre-installing FW that made Download mode disabled for quite a few devices, but thru some low level (edl) actions, we were able to reverse that and load a global fw to the phones, restoring all functions!
ok long posts.... ANYONE... I am up for ALL suggestions, because i can fully brick this phone and return it , but my window closes in 7 days!
Click to expand...
Click to collapse
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
maamdroid said:
Dang! This is a messy situation for yah! I contacted support for an MSM tool and they said I have to send it in for them to flash it.
I think trying to have them flash some other variant would take you past your 7 day window and they may not do it anyways.
I would say least send an email to OnePlus support and ask if they would flash to other variant otherwise you will be returning the phone. You should get a response soon. Otherwise I'd lean towards returning it... Sadly.
Then buy straight from oneplus if you still want a 10t. They may have a good blackfriday deal on this phone as well.
Click to expand...
Click to collapse
thank you ... i was waiting for the response from someone who had been in contact with them. I will mail them right away.