Hi Guys!
New to the OnePlus! Been wanting one since they came out but wasn't till the OP8 that they supported Verizon here in the states.
So after a huge ordeal (My stupid self FLASHING the boot.img and not booting from it and spending hours figuring things out as i'm still old school and not use to there being a million versions of each phone) finally got it working again and rooted!
My next questions is with my Droid Turbo and the Moto G5s+ they have Logo.bin that could be flashed and make that message go away for the most part. That exist at all with the 8T KB2005??
I do not believe you can remove this message while unlocked.
Related
I am strongly considering getting the Verizon m8 today, but before I do there is one thing I need to clarify:
If I get this phone today is flashing a custom recovery/ROM possible?
I am asking this because before I got my current phone (Verizon S4) I checked on the forums and saw all the talk about custom recoveries and custom ROMs and got all excited and bought the phone. When I got the phone however I became aware that all of this was only possible up until some OTA update after which custom recoveries became impossible, and since I had a newest phone straight from verizon withg the latest updates I could not do any of those things.
So, can someone confirm that to the best of the publics knowledge all this is still possible? This will make or break my decision to get the phone.
Thanks
P.S. if there anything else that you think I should know, like stuff you wished someone told you before you got the phone, please dont hesitate to mention those things as well.
Yes this phone is able to be unlocked (soff) and load a custom recovery. There are two methods one is free Firewater and the other is $25 sunshine if the Free option fails to work for you for some reason.
Have you ever heard the term, "I know just enough to be dangerous"? I truly know what the "dangerous" part of that phrase means now.
I have been surfing the lists of xda forums and reading through them for guidance for days in order to preventing clogging the forums with my pain. However, I'm finally completely stuck and need some help trying to SIM unlock my HTC One E8 (Sprint). In an attempt to my root phone with the old guidance available on-line, so I can unlock my Sprint SIM, I have, hopefully only temporarily, bricked my phone.
Phone Origin: Sprint USA (Dual SIM capable) See: https://www.frequencycheck.com/models/AaJ6a/sprint-htc-one-e8-td-lte-htc-e8
Model: Sprint HTC One E8 TD-LTE (HTC E8) 0PAJ50000
Bootloader installed: 3.19.0.0000
Latest OS: Marshmallow 6.0.1.
Build: 3.10.651.6
S: S-off via Sunshine
TWRP recovery Installed and still active despite boot failure.
Current OS Boot Status: Bricked. Will not boot past the "HTC One" boot screen.
My main goal was to unlock the SIM so I can use this USA (Originally Sprint network) phone on the Australian Telstra Network. A lot of the guidance on this process is several years old, understandably as the phone is discontinued. I was following a great method, published on xda, via senior member OMJ (who also credits briankariu), 28NOV2014. Link: https://forum.xda-developers.com/one-e8/development/ruu-sprint-htc-one-e8-1-22-651-1-stock-t2952981/post57116360#post57116360
In the guidance it recommends "-if not already on 1.22.651.1, flash the RUU in OP". Being the NOOB that I was, I located file "Sprint_HTC_One_E8_1.22.651.1_stock_rooted.zip" online, and installed via TWRP recovery as recommended. I now understand the stupid rookie error of installing a stock rooted zip that is not compatible to my loaded marshmallow build that it has. Due to this knowledge based error I have, hopefully temporarily, Bricked my phone. It will not boot past the "HTC One" Boot screen, and therefore cannot continue with the process OMJ published those years before.
I have two goals from here.
1.) Hopefully recover the phone from brick and be able to boot again, Ideally in a rooted status.
2.) Unlock my SIM. Sprint has given it their best shot, I suppose, but will not techincally support the SIM unlock on any phones older than 2015. They gave me an MSL number via email, put up their hands, and literally said, "good luck".
I am incredibly grateful for the wealth of knowledge available on these forums. I have learned a great deal from it. But with the phone being so old, I can no longer find the exact right recipe to be successful in my quest. Any help would be incredibly well received!
Update:
Thanks to xda member "xXminiWHOOPERxX", I have flashed a compatible ROM onto my E8 and now it's alive again.
Stock_Sense7_MM-v1.0.0-SE8.zip
Android MM - 6.0
Based on 6.12.1540.4 release keys for One M8
Full Sense 7 Interface
Almost Stock Like Kernel
Pre-Rooted & DeOdexed
Now, I am hoping to continue with a good way to SIM Unlock!
Again, any help would be immensely helpful!
I had an HTC 10 w/Sprint and it's getting old and full, but I liked how easy it was to unlock the bootloader. I enjoy having a rooted phone and I'm seeing that the S8+ (US Version) can be rooted, but I'm assuming there's prerequisites that used phones might/might not have to do so. So I'm just wondering if there's any questions I should ask the sellers of an S8+ on Swappa or eBay to make sure that root is possible when I decide to buy one? I don't wanna wind up w/a LS997 situation, where I got the phone but it was too upgraded that the methods to root were patched up. Thanks for any help.
Brian23MAC said:
I had an HTC 10 w/Sprint and it's getting old and full, but I liked how easy it was to unlock the bootloader. I enjoy having a rooted phone and I'm seeing that the S8+ (US Version) can be rooted, but I'm assuming there's prerequisites that used phones might/might not have to do so. So I'm just wondering if there's any questions I should ask the sellers of an S8+ on Swappa or eBay to make sure that root is possible when I decide to buy one? I don't wanna wind up w/a LS997 situation, where I got the phone but it was too upgraded that the methods to root were patched up. Thanks for any help.
Click to expand...
Click to collapse
No boot loader unlock. There is a method for root. It's system only root and only on nougat.
Coming from LG you've seen anti roll back we have the same. But they're is a method to downgrade the system only even on the latest boot loader to have rooted nougat https://forum.xda-developers.com/galaxy-s8+/development/root-t3909782/post79500078#post79500078
Safestrap is like fish on the lg g4. once safe strap is in place you can then flash a older system image from older boot loader revisions.
Even on the latest boot loader we're have Samsung's test firmware called combination files. Which include a nougat bootloader that is a permissive kernel and allows for root.
I ran lg all the way back from g2 to g5. So I've been in your shoes too. that's pretty much how I ended up here. From a sprint g2 g4 and g5
So even if the phone is upgraded, there's a method to roll back to an environment to root an S8+? So I can basically just cop an S8 w/no worries then and not ask any prerequisite questions?. That's good to see. I appreciate the assist.
Brian23MAC said:
So even if the phone is upgraded, there's a method to roll back to an environment to root an S8+? So I can basically just cop an S8 w/no worries then and not ask any prerequisite questions?. That's good to see. I appreciate the assist.
Click to expand...
Click to collapse
yea pretty much the bootloader must remain the same increment but the system does not
obviously newer pie and even oreo where all bit 5 BLs but the firmware needed for root is also bit 5 but a nougat bootloader
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613
is the perquisite to rooting
this allows a type of twrp for locked bl
we can flash pretty much all but boot img and non stock based custom roms
Bl6 hasnt been released yet so as long as you get it soon your good as
since this is edl I doubt it can be patched but always a possibility
I have a motorola z play droid I'm trying to get rooted twrp and rom on but now I'm reading that verizon phones can not be boot loader unlocked so is this true that no verizon phones can have custom rims or recoveries on them? Or can I do this without a unlocked boot loader? I'm really confused. All of this stuff seemed so much easier about 6 years ago when I was more into it. I see people putting recoveries and roms on moto z plays addison and mine says addison in device info but then I don't want to flash something that's going to brick my phone as I'm a single father and can not afford to buy another phone at the moment. Any answers are greatly appreciated and sorry for such a noobish question. This site rocks btw thank you devs for all you do for us.
AFAIK Verizon don't want to get the bootloader of their phones unlocked because dumbasses will root their phone, mess it up, and then they want to flood the tech support lines expecting Verizon to fix it.
Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?
You probably need to unlock your bootloader?
fastboot flashing unlock
AlmightyGrapefruit said:
Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?
Click to expand...
Click to collapse
You will get fastboot errors about unlocking critical partitions if you try to flash partitions other than boot, recovery and a few others while you're in bootloader mode.
For the rest you must be in fastbootd mode.
Chances are you need the unlock token from OnePlus themselves it takes a week