Related
I have been overloaded with so much information here on XDA, I'm having a huge issue being able to follow the tons and tons of steps I've seen in the forums.
The issue I am having,
Pressing the the camera and power buttons don't bring up fastboot options
it only brings a screen with a list of tests
If I hold down the Vol.Down&power buttons, it boots with:
"DT is in FASTBOOT_MODE"
From here my Device Manager (Win 7) shows:
ADB Interface-
Android Sooner Single ADB Interface
I've tried to type in the commands on CMD
I get nowhere after typing in the Vendor ID: Expample:0x413c?
says not found or something like wrong command
I am at worlds end, I don't want to give up trying to flash a new rom on here.
Again I seriously am lost and I can't say I haven't Searched because I have!
PLEASE HELP!!!!
My take on modding the Streak is here and a howto on using Streakmod recovery.
It sounds like the Streak has been put into native engineering mode. Does your screen look similar to the following video?
http://www.youtube.com/watch?v=Vbl8oI5CQts
Thank you, I will read up on your links here. I hit the thanks too.
BTW I have some pictures of what I am seeing and hopefully the link will assist me greatly.
Does it matter that the Dell Streak is an Engineering Model? lol sorry if I didn't mention this before...Just found out.
It makes a huge difference. Read this thread. The TL;DR version: before bricking his unit, the user rooted the phone but could not install any ROMs.
lilrepo said:
Thank you, I will read up on your links here. I hit the thanks too.
BTW I have some pictures of what I am seeing and hopefully the link will assist me greatly.
Does it matter that the Dell Streak is an Engineering Model? lol sorry if I didn't mention this before...Just found out.
Click to expand...
Click to collapse
Engineering models are in general not compatable with retail roms. If it stopped booting it might be a full brick now.
Which would be rather tragic. While I know I wouldn't be able to update an Engineering sample, I wouldn't want to anyway. I'd love to have one simply because they're scarce.
If it wasnt for the fact it was bricked and the rom nuked I would have asked for details of the pre-installed rom as eng streaks are exceedingly rare in working condition now seeing as the streak is (in phone years) very old.
Unless he finds a magic way to make it boot again it's likely completely worthless now. The amount of work to find out why it differs from retails streaks and porting a rom over would be much greater then buying another streak/phone
Well damn, I'm glad that I still have it but I Never said it was bricked.
Actually,
It is fully functional with everything original from the the engineering desk with all the Dev apps!!!!
Here's the link to the pictures I took today, disregard the date and time on the main screen of the dell streak as it is wrong.
http://s75.photobucket.com/albums/i306/DJLACES/?action=view¤t=2011-10-09_16-50-58_616.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-09_16-46-47_791.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-10_01-28-58_487.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-10_01-29-38_170.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-10_01-30-19_805.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-10_01-38-55_829.jpg
http://i75.photobucket.com/albums/i306/DJLACES/2011-10-10_01-40-58_766.jpg
Seems I am going to be helping you guys instead lol
It's all good, XDA has been great in providing so much help with nothing back from me, so whatever I can do, let me know!
I've accidently assisted in helping brick a few eng s5's before trying to flash a retail rom on them.
Good thing you didnt go though with (or at least get far enough) bricking it
Would you be willing to dump the rom? While you cant run any custom rec on it, you could use an older root tool (or newer one if it works) and root and manually dump it.
Just like previously stated working eng s5's are really rare.
I dont recall if i have that rom, I will check later today
Tears...
oh well, I was really hoping on gutting it inside out.
Don't mind dumping the rom but there has to be some way to push the file to the device and have it install automatically because there are issues with the D.S.
I'm sure you know this but this device is not a stable model, it's really sensitive and I wouldn't be surprised if it had split personalities
There are Errors!
We're talking- app errors and os errors. I got the streak like this and this is why I wanted to flash it.
I've tried installing apk's to the device and I get an error "No activity found to handle intent"?
This is on every file I try too open using the file explorer.
Either way let me know and we'll see what happens...
Wouldnt be surprised if the rom was feature incomplete. It may very well not have a complete set of frameworks/stuff since it's not ment for general use.
Does sound like the situation here....
Wonder if there's a way to even implement a fix or patch to address that issue...
If it was true it would require working on the code, which is what happened towards a release rom.
As an aside I checked and I do not have this rom either. Unless you're willing to spend years working on getting your eng s5 to work it's a waste of time.
As the retail streaks arnt even fully cracked when it comes building it from source, then multiply that by the fact eng ones are different and noone else owns one, much less would be willing to port a rom to it.
There might possibly be a simplier explanition in the rom, but without all the details it's somewhat hard to call
Like I said before, if you explain to me how to do a dump then I'm sure we can find out but I'm in no way savvy to software coding/writing...I wonder if a call to them would help? lol (if only it was that easy)
You will first need to root your device, i would recommend using one designed for 1.5/1.6 like universal androot or something for that era
slight problem, did you notice the apps in the link?
there's no Market app, I also mentioned that I get errors when trying to install from sd....
Unless there is someway to cmd or adb into it and manually push it then I'm SOL
Well they wouldnt be available on the market anyway, you would have to sideload it manually even on a normal functioning device.
if you have adb set up it's: 'adb install <path to apk>'.
Thanks for the info but unless you can spell it out for me, adb is my weekness.
I tried to look up ways to put that command in adb and have gotten no where. I'm putting this device up for sale...I'll see if it sells.
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
No adb access? That sucks, as it should be pretty easy to fix if you could adb push. Were it mine, I'd go ahead and try to replace the screen on the functioning tablet. Not what you want to hear, but I think that's the only way to get working again. Best of luck.
Valence1981 said:
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
Click to expand...
Click to collapse
You're done if device is running 4.5.2 w/no adb access. There are a few last resort unbrick methods/tools but they are geared toward older versions of FireOS (v3.2.6 and below). Replacing the screen on a 7" HDX is difficult; copious use of glue makes for a tough job. Might check auction sites; prices are pretty low for 16GB models. Also consider the latest 7" tab from Amazon (2015 Fire). Specs are awful vs HDX but it really isn't that bad, especially for video and with apps designed for lower resolution screens (many are). Fully rootable with option for custom roms. FireOS v5 is a nice step up from v4, faster and more 'android like' (although still heavily skinned).
THANK!YOU OK guys once again and at the same time, in advanced, THANK!YOU
so i am in serious need of some help or someone to just give it to me straight and just put me out of my misery. its been a couple weeks now and ivr put in huge amounts of time trying to search out a solution. Now it's just cruel, if I were and animal they would have put me down weeks ago
I already apologize, I'm going to do my very best to keep this short ( as possible ) and to the point, I have a tendency ( more like debilitating compulsive disease ) of rambling while simultaneously over descriptive, and my effin' phone is broken!!! Give me a break. Ok here we go I promise
This is my first thread / post, believe me I have searched independently, finding a TON on parts but no real conclusion or fix, or of it was there I meed my hand held. So I am, was, running a Verizon galaxy s4, rooted (king root), lollipop 5.1.1
Situation of my phone right now
Ultimately the phone won't boot past the Verizon logo / loading screen, whatever that phase ( if it even is one ) is called. No amount of time has done anything for it. It leaves me with only 3 different options ( attempting to boot normally being the first )#2 I can get info "Odin mode" <holding Vol Down + Power + Home>as its named at the top of the prompt. Where basically I've deduced that it's trying to update or install a custom operating system, from where? I'm not sure, the cloud I reckon, since it warns me not to turn it off and I dont have it plugged in, or anything else provided for it to do much of anything, don't think I even downloaded Odin that I know of. I'm thinking I forgot to mention I do not have access to a computer currently. Quick update: or I just forgot to mention but if you haven't guessed it, I have no immediate access to a computer, and while I'm here I also was not far enough to save a backup. Thanx
continuing. . 3rd and final pathway open to me Recovery Booting<holding Vol Up + Power + Home> I'm sure you guys know the one, where I have tried every option ( more than twice ) to, unnecessary to say I'm realizing, no avail. Had even come to terms with what appeared to be my only hope in sigbt and attempted the wipe / factory boot. And if that worked and changed anything I guess I misunderstood the whole concept of factory wipe. So that's about where I stand currently.
Events leading up to disaster. ..
I was in the overall process of installing xpose of course! I had already performed a successful Root thanks to kingroot, verified with root checker. Had moved onto the slow going process of learning to get TWRP going, here's where it starts to get a little messy... So it goes without saying that I was having.. let's say difficult time with TWRP. I went through one of the pains of the overall process and located my version of framework ( or so I had thought, quite a few people thought actually ( ok so thinking back on it I never really looked at the date on any of the threads so this whole chain of events could have been last year for all I know, and I just started at the beginning and got the full ride and experience everything those in this community running lollipop 5+ had to go through. And when I say chain of events I'm talking about the first rounds of xposed for Samsungd and lollipop. And the nightmare left in its wake. Evident in the step by step UPs and DOWNs left in the threads) so being not 100% correct i had the right framework I put that on hold awaiting a few replies. I then began to attempt twrp once again, this time for a backup . Once again I found myself hating twrp. Defeated I put it all aside for a few days.. upon retire I began reading up on everything all over again. Came across a very helpful ( helpful now, very much not so in the time I'm currently speaking of ) app I bought "Super-Sume". Which sounded like it was going to help out and make things not only easier but get me back on track and going in the right direction again. Well somehow as it was performing it's first stage of removing kingroot and all the extra goodies that they have been accused of adding in as well, the app froze. Not sure I I froze exactly but it had not moved or gained any progress in quite a while, I believe some or most of this to be caused, I recently found out as I was attempting the whole adventure over again on another ( older, less expensive) phone. The one I'm currently on. Just a galaxy lite or something. But come to find out you cannot use the latest , or those after like 4.90 versions of kingroot, or the super-sume won't work, and possibly do what it did to me maybe? ?? But after it froze or whatever it restarted when I shut if off and we find ourselves having come around full circle now.
Once Again ! Thank You I really just want to thank those of you that made it all the way through this never-ending thread. Just being dedicated / motivated enough to get this far, gives me high hopes we will be able to get through this ! The hard parts over, right?
Once Again ! Thank You
Hi,
I, like many others, got forced onto Android 11. I have a lot of problems with it. With or without root. The most annoying of which is the wifi aggressively dropping/changing. Bluetooth failures. Volume drops that don't return to normal, forcing a reboot to fix. Clock and background/screen saver problems. System UI crashing. Keyboard freezing and lagging on certain sites with textareas. I used my phone without root for a couple days after the forced upgrade and all of these issues were present with or without magisk modules.
I'm interested in going back to Android 10 and blocking the a11 OTA in Hosts.
I'd like to get some help with a couple things. I'd like to make a FULL flashable backup of my current device as is. Just in case I mess something up, I can get back to this current state as worst case, very easily. Do I use the MSM tool and copy something? Do I boot twrp and push something over? Please advise the safe and smart way to get right back to a 1:1 of current install. I want to be very sure about this part.
After I know which way I can safely get back to current state, can I use the MSM tool to wipe and flash an older build of Android 10? Or is it a problem after being on 11 because of some restrictions (partitions, RO, twrp no mount) somewhere?
If I can get back to an older build of Android 10, I have a couple options (grayhat and httpcanary) to monitor the traffic to see what we need to block in Hosts for sure.
I'm open to other suggestions also. Someone in the root thread said they proactively tried to disable some services around update and it was still forced on them.
OnePlus 7T Pro 5G McLaren TMobile
Android 11.0.1.2HD61B
(Carrier unlocked, bootloader unlocked, magisk root)
Thanks for any help
Disable the T-mobile update app or ask them to disable it on their end, they can.
Backup all critical data by direct file transfer and verify... just in case.
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
starcms said:
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
Click to expand...
Click to collapse
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Appreciative said:
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Click to expand...
Click to collapse
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
starcms said:
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
Click to expand...
Click to collapse
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Appreciative said:
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Click to expand...
Click to collapse
Post the Magisk module for high-speed tethering and I'll take a look at it. It'll either be really simple to get it working on OOS11...or not lol.
All credit to the authors and yadda yadda.
There's another one floating around.
In this one, I changed it to be /product/ but didn't have success.
If you do have success on a11 with it, that'd be cool. I can find out if a reset will clear up these other issues I have or not
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Sorry to hear that.
Do fresh installs for the apps.
Do direct file transfers to/from the PC for all other critical data. "Restore it all" apps can fail miserably and are hard to verify the data they supposedly stored.
11 is a mess but this might help... or not.
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
starcms said:
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
Click to expand...
Click to collapse
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Appreciative said:
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
You can block OTA a couple different ways. I've done it for over 5 years with AT&T, no root needed.
My 10+ is still running happily on Pie.
Appreciative said:
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Xiaomi/Redmi/Poco meets the root and ubl friendliness. In some countries, they still have warranty coverage after unlock bootloader.
Good specs or not is vague between different phones.
Check XDA Xiaomi category and see the reply and thread count. It's to some point a sign of better price to the specs.
Use GSMarena to compare the spec.
Appreciative said:
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
Click to expand...
Click to collapse
Sadly, OnePlus hasn't been typical OnePlus in well over a year. Look how slow updates are now even for their latest non-carrier flagships beginning around 7T time (and can start to be seen as early as the 6T).
Appreciative said:
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Oppo and OnePlus are merging, like you said, so won't they still continue producing flagship phones at a manic rate, like Samsung? At least Samsung has gotten much better with the speed of OTA updates, while OnePlus has tanked.
We're guaranteed Android 12 for our phones. Let's see how long it takes for us to get it, probably more than a year after I make this post. The 6T is still waiting for OOS11.
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Appreciative said:
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Click to expand...
Click to collapse
That's one reason I got this phone, OnePlus's prices are thru the roof. And no, I don't want any Nord crap. I want a flagship phone at a reasonable price. Got my 7T Pro 5G Mclaren for $500 brand new from eBay the day after the OP8/Pro launched. I just couldn't justify spending $1000 on a phone and I never will.