I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
Did you convert your tmobile to international ? I guess you did. So either root it and install magisk or livr without Google pay.
Sent from my [device_name] using XDA-Developers Legacy app
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Krzysiek_CK said:
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Click to expand...
Click to collapse
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
Well you can't do really anything but if you have not had it too long you could return it.
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
You have 3 options:
1. DO nothing and hope OnePlus will fix it down the road. I actually lost hope with this one.
2. Load T-Mobile version, and loose dual sim capability. Google Play will pass certification and Google Pay will work.
3. Use Magisk, at your own risk, to trick SafetyNet check.
I have one of those scammy "no warranty" T-mo -> Intl. OnePlus 6T and, with enough work, it is possible to convert to the most recent Intl. android 10, and get root and Google pay working. I don't think at this time it's possible to watch Netflix in HD while having your cake and eating it too, sadly. The A/B situation on this phone is painfully confusing and leads to brick after brick as you learn the ropes of this phone. Not sure that's TMo's fault. Thankfully the bricks are fixable. You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
So that gets you to an equivalent to a locked Global 9.0.11 rom with no OTA updates. From there you can do developer mode -> unlock bootloader instantly from fastboot -> (loose all your data) -> TWRP; now the a/b stuff gets really confusing AF but if you do TWRP from fastboot->flash 10.3.2 -> TWRP from fastboot again (it's like ms windows!) -> flash TWRP .zip installer -> TWRP from fastboot yet again -> Magisk, you can finally boot system.
To pass CTS profile you'll need to use the command-line signature changer Magisk module and Magisk Hide. Once the play store says it's "Certified" (certifiable more like...) and Magisk is giving you two green checkboxes, you are ready for more suffering. Now you need to freeze the Google Pay/Play apps and Google Play services and blow away all their data. At least that's what I did. Then make sure Magisk hide has all the Google play/GMS/AR/pay stuff hidden in Magisk, one more reboot for good measure, and you're off to the races. This gets Google Pay working and even lets you watch DRM at Widevine L3 level... it's still not all your cake and all your eating I suppose... hopefully you're not a big Netflix guy. Otherwise you kinda bought the wrong phone.
GL! Oh btw I have not found any way to restore an encrypted TWRP backup on this device. Starting to suspect it's literally impossible at this time -- but, if I'm honest, probably I just haven't gone through enough suffering, yet, to figure it out.
anonywimp said:
There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
Click to expand...
Click to collapse
Nope. Just completely dis-confirmed the above recipe. I am clearly still well in the cargo-cult phase of my OP qdl client tools education
All I can say for sure is randomly frobbing with the buttons and the phone-side usb-c cable for long periods of time will usually eventually start the process. And one sure-that-I'm-not-sure---but-still-fairly-confident correction: It probably helps to /un-/plug the phone from the PC, once it starts giving the meaningless red "Sahara quintessence frobnitz poop" error message (or whatever equally meaningful thing it actually says). If you find yourself in TWRP, you can use the "Reboot edl" button. Likewise, I believe the stock recovery has an interface to jump to qdl mode... could be making that up though Anyhow I think from there you want to turn the phone entirely off, which I believe can only at this point be achieved through continuous, uninterrupted mashing of the power button. So just after your get the error and disconnect, is your opportunity to impress the phone by bleeding all over it.
anonywimp said:
You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..."
Click to expand...
Click to collapse
OK, I think I figured out an actual recipe now, or the beginnings of one. It is still a bit fuzzy in places. It goes like this:
If you're not in qdl mode, or you are there but it won't talk to the proprietary flasher software, get the phone completely turned off. Often this is the hardest part. I have sometimes managed to brick my phone where it will Boot and insta-freeze at the infuriating-yellow-triangle screen¹. Then it will just sit there, indefinitely, and never bring up any sort of USB or wifi connectivity (nor does it show any sign of boot-looping, judging by dmesg output on my computer. It's just cold, and dead. Probably a bootloader bug/secure boot fail). In every semi-brick-like circumstance like this, I've found the following enables me to get the phone to turn itself off reasonably quickly, in fact, in just a couple of seconds, usually: unplug any USB-C cable (so I'm running on batteries), hold down all the buttons* until fingers bleeding or something happens -- if nothing happens, release all the buttons briefly and try again; once off, release all the buttons immediately.
Now get the phone back on, and in qdl mode. Somehow. Usually, if the phone is unplugged and off, I can get it there by holding all the buttons and plugging it into usb. If I'm soft-bricked, I'm already there, so nothing to do. From TWRP I can easily "reboot edl" to get there. Maybe there's ways to do it from fastboot, stock recovery, and system as well, via adb/fastboot commands.... My preferred way is holding "all the buttons" for about 1 second, and plugging in the usb cable, which will cause it to enter qdl mode "just one time" without actually bricking anything.
Now, finally, we run the proprietary flasher tool. Press start and it will go until it gets to the "sahara bingo yip-a-dee-ha" error (or whatever it really says... definitely not exactly what I wrote ).
Now turn the phone off again. Same recipe, but this time it seems to almost-always suffice to keep the phone connected to USB, while holding all-the-buttons. If that isn't working, then I go ahead and unplug, power cycle, and get into qdl mode like above. During this, the computer software is maybe completely disconnected from your phone, *****ing and moaning the whole time about Sahara or whatever. Ignore that, it's fine.
If the phone was fully powered off (rather than power-cycled in place), be sure to next release all the buttons, so that the phone has no usb or button-press input of any kind for at least a fraction of a second. Then press "all the buttons" again (nb: I suspect just vol+ and vol- suffice here, and the power button is superfluous? Maybe even detrimental depending on ordering? If I screw this up (sometimes it winds up booting into recovery or bootloader), then I find a way to ask it to reboot from there into qdl mode, if I can, or else power off from there and try again to use the three buttons.
pro tip said:
It is possible to hold all the buttons for too long. In which case, you may find yourself booting system. From there you may need to start this guide over from the beginning, sorry. The correct period of time to hold all the buttons down is about a second. Two seconds is probably too long.
Click to expand...
Click to collapse
Using your fourth hand, Plug in a USB-C cable, what leads from your computer, to the phone, while continuing to hold down all the buttons with your other three hands (or, if you entered qdl via software, just plug it in, now).
That's it, done. Kick back and enjoy as the tool's progress bars go wild and unbrick your phone tut suite. The qdl process should be able to go all the way to the end where it says "100%" (although when you close the program it will still treat this like you are interrupting it in the middle; I think that's because it does multiple phones at once, and you only ever fed it the one phone, so it is alerting you that, hey, phone #2 never got processed).
I am doing the above in a non-FOSS emulator under desktop linux, using the patched client referenced from xda threads.
I imagine qemu would work, as well. Obviously native Windows is going to be your best bet. I def. wouldn't trust Oracle (VirtualBox) USB emulation with my qdl flashing needs, if I were me -- which I am. Phones tend to look like huge USB hubs, full of an ever-changing kaleidoscope of peripherals. Which I don't think the VirtualBox USB stack is really ready to cope with right now. (Not even with the proprietary USB add-on pack or whatever that is -- I simply don't trust Oracle not to hard-brick my phone; VirtualBox has seemingly perma-bricked one device for me, already. That was some time ago but I'm not going to feed it any more devices and I doubt the USB was fixed in vbox. It think it's paravirtualized, or something, so as to be super-fast, but unreliable when the bus topology changes in meatspace.
-- rants / footnotes ---
¹ You know, that warning screen for "security." Which, currently, happens to be punishing me for trying to put the newest stock security updates onto my phone that I just purchased a month ago¹*².
* Not an "All the things" meme -- by "all the buttons" I literally mean all the hardware buttons: [vol+], [vol-], and [power].
¹*² I imagine the person who made the decision to require this in Android would explain it something like this:
straw man said:
(California accent) "Um, like, why? Are you a criminal or something? You know, you could just buy a new phone for like $899 US. Oh, you're, like, poor, or something? Well, OK, I guess there's no way for us to stop you from doing that. But we, like, won't be able to support you in any way. Also, sorry, but we're just going to need to put a brief warning screen on your phone, as a safety measure? No, it's not really a warning for you. More, like, in case other people might be around you for some reason? It just says, 'Hey, no judgement, but it seems like maybe a poor person owns this phone? And they're definitely doing some really weird stuff with it. So just be careful. Like maybe tell a friend where you're going, if you're going to spend time with them.' What? No, I'm sorry, there's no way to remove it. We paid millions to have it fused into the microchips or something? If you could just remove the warning, that would defeat the purpose. So, I'm sure you'd want the people around you to be safe, right? And, like, so do we! So we, like, locked that down pretty tight, yehh-...!'
Click to expand...
Click to collapse
Related
Hi everyone!
I'm wondering, how risky it is to flash new firmware to the tab? Is it really brickable, I mean, is it possible to really really brick the tab to a point where it's not possible to fix it? I'm asking partly because I'm a rookie, but mostly because it seems that everyone who manages to brick their tab around here, is somehow able to restore it. Or am I mistaken?
Where I live, the tab has a starting price of $1100. And thats gotta be one of the most expensive bricks in xda history. And if I brick mine, I know I won't be able to resist buying a new one, which adds ut to a $2200 pricetag and a very VERY angry gf..
thanks btw to all of you who make this place what it is
As risky as any other device. Simple. The risk doesnt just lay on the devices shoulders, its the user and the rom maker.
Sent from my GT-P1000 using XDA App
Okay, I'm so confused with the brick-terminology being used here. In all posts regardig new firmware to the tab you'll see at least to guys saying that they bricked their tab. Only to say that they fixed it/unbricked it moments later.
I thought that if you bricked your device, whatever device it is, then it's dead, period. No more usefull than a brick like the ones you'll find in a brick wall, just a hell of a lot more expensive. Heck, the word "unbrick" shouldn't even exist by this definition.
So, let me rephrase:
If I brick my tab, can't I just unbrick it? And if not, why? Is it even possible for the tab to be totally and permanently bricked forever? Is the tab in any way safer to fool around with than other devices? Do we know anyone who have bricked their tab permanently? Should I be afraid of fooling around with my tabs firmware for real?
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
paulshields said:
A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
It's in the works, just not quite there yet.
As Paul said, there's always going to be a risk it COULD happen. But following documentation and fully understanding the task at hand before diving in helps to limit the risks to a minimum.
Thanks to all of you for enlightening me
When I was flashing the different files to get calling on my ATT Tab I managed to flash the wrong file and get the device not to boot up but there was still the "download mode" to go into and I was then able to flash the correct file. I find it is very rare to actually "brick" a device requiring the device to be replaced or cracked open & reprogrammed manually. Most of the time now when a device is described as a brick it just won't boot the OS like it is normally supposed to.
paulshields said:
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
Lol @ "brickie" - I guess you have to be British to get that one?
As for "bricking" , quite right, the device isn't "bricked" if it can be fixed by the user.
People have gotten sloppy with the term, but really it means that you could build a house with it if it were fat enough, but it's no more useful than an expensive paperweight.
The worst you can do without bricking is boot-loop/no-boot which can usually be fixed. The point is, if the device shows any signs of life whatsoever, it's usually fixable.
I thought I bricked my tab, I got the infamous "phone-!-pc" screen
http://forum.xda-developers.com/wiki/index.php?title=File:Samsung_Galaxy_S_Black_Screen_of_Death.jpg
I thought I was screwed. However, I still had it connected via USB and Odin still running and I saw that the com port popped up. I though, hmmmm
clicky and bam, its flashing.
Got it back.
This was after a stupid botched flash attempt on my part.
So, I think you REALLY gotta mess it up to be proper "bricked"
I did a lots of tries and I thing that is not that easy to brick, but I can give a suggestion: Backup the EFS folder!!!!!!!!!!!!!!
I deleted by mistake with root explorer the nv_data and relatives backups, and I had a corrupted IMEI that is not a brick but I think is one of the bad things (and hard to recover if not impossible if you don't have a backup) because if the carriers ban double IMEI the phone (tab) will not work + is not legal
Forgot to say: seems that some SGS firmware upgrades corrupted the IMEI too, I didn't see something flashing the TAB, but restoring the EFS folder will fix (almost always) the problems
I have not tried to brick my GT, but the JM6 gave me a scare... I have been flashing it for a while now.
The one thing you have to give up for now is SWYPE. I se you have a norwegian flag... And norwegian is not included in any flash I have found. So if you ever decide to try flashing. Say goodbye to SWYPE in norwegian for now...
Yeah, the loss of the Norwegian keyboard is the only thing stopping me from flashing jm6. Lucky for me, I'm very patient.
Sent from my HeTC Desire using XDA App
Apparently, you can brick it. I succeeded !
I flashed with Odin and a custom made PDA package including boot.bin but no repartition.
Odin flashed without problems but the Tab did not reboot and simply 'died'.
Black screen all the time, no recovery/download mode, not seen by the PC, does not charge on ac/dc (neither the charger or the PDA ever gets hot, no sound on connection, ...).
I'm letting the battery discharge completely (but how long can that take when it's not using any energy...) to test again tomorrow but I will probably RMA it on monday.
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
alias_neo said:
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
Click to expand...
Click to collapse
A little un-nerving isn't it... I have deep thoughts of not being able to get the Tab to drop out of memory by not being able to remove the battery and flush.
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Running down the battery is an option... but it would take an age seeing as you're not doing anything with the phone except looking at two icons on a black screen.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
That thought passed me by as well.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
I did . I was fooling around with the button definitions of the tab, I lost all my buttons so to speak (also the powerbutton) and couldn't get into the system. A simple adb reboot got me out of there without any problem.
Yes, I believe adb can connect with the Tab in very unresponsive states and still issue commands. I've seen it also with my old galaxy S. A bad flash and a blank screen still gave me access to the system shell with adb.
My lesson learned is: alway have "USB Debugging" turned on.
Hello all; apologies in advance if this is retreading old ground, but I couldn't find anything about this on the forum as is.
So, while taking some video the other night, my Razr M (all recent software/OS updates, stock software + commercial apps , no flashed ROM/no root/hell, I wasn't even using GoLauncher anymore) decided to freak out on me. By the end of the night, it got itself stuck on booting, and by the next day, it's more or less bricked. Called, got my replacement phone from Verizon, but before I ship this off, figured I'd plug it into the PC and see if there was anything I could do to salvage data -- most things are backed up, but the video/things from that day obviously aren't.
So, no screen. When I plug in, I get the little green light intermittently. For fun, I tried getting to a boot screen (Vol down/Vol up/Power), and now I have this fun thing where my PC tells me it's installed "Fastboot SMQ S" drivers, and is "searching preconfigured folder drivers". Every few seconds, the phone's light will be green, a few seconds later, it will go off. Likewise, my device manager keeps trying to recognize a Human Interface Device, and now and then Windows tells me a connected device has failed. (Once every now and again it tells me it can't recognize it, for about a half second.)
I should note that at no time during any of this does the screen on the phone itself give me any sort of image or feedback.
This leads me to think there's still something inside the phone fighting to work -- as stated, I don't need it to get back to functionality per se, but if there's enough left to work with to at least pull data off of it before it clinks out, I'd be quite happy.
This seemed like a question for the XDA folks, even though it isn't mod/dev related, because you guys are usually the forum I read when I have questions, as you all seem to really know the insides of the phones and systems. If there is a better forum/place for asking this question, please just let me know. I'd be grateful for any sort of advice/insight you may have.
Thank you, and have a great afternoon!
p.s. I assume, based on other similar threads, that the whole "stealthily open the case, yank out of the flash and kitbash it into my pc while somehow not voiding the warranty" route is unfeasable/undoable. If this is not the case, I'm game for that. I'm not a phone dev, but I've seen the inside of an electronic device or ten in my time, so I might be able to pull it off.
Android 8 prev 3 or whatever they call it. Never unlocked the bootloader. USB debugging is on I think.
I assume it is hopeless but just in case something to try, here's where I am now:
I think I was seeing "Phone is not available" and such on startup. I went to clear cache partition having not done it before on this 6P, after clearing call cache did nothing. The odd thing was it was instantaneous, meaning I assume it was doing nothing. Did a few of those. Somewhere in there I saw "No command" which I'd never seen but a button or 2 later was at recovery screen again.
Then just the google logo laughing at me. Or if looping: a flicker, black..., flicker, black... Won't shut off either. Has anyone's magically booted after a day and been fine?
I maybe can't get to the recovery screen. I did once in this state with some button mashing but normally it just goes straight to the logo when selecting recovery mode even with mashing about. I assume that alone ensures my complete and utter defeat.
I don't know the significance but on the power-Volume Down start up screen (not sure the name of that screen?) it says "Plug in USB data cable." I think I have USB debugging on so that was my only hope but I have no PC handy to check. On ChromeOS it does nothing plugging in.
I read that even locked bootloader could use a full OTA to flash but I think only for those on an older Android version.
So... Damn. My 2nd 6P after a screen failure. I'll certainly try anyway having read threads, but should I have a year on the RMA unit or only the time that remained on my original purchase?
Btw, has anyone heard of Hauwei excepting to exchange perhaps with additional cash for a new model (Mate 9, 10 Plus)?
Has anyone heard of Hauwei accepting a phone bought in another country? Not in the US now.
Thanks.
Hunter O. Unicorns
I don't like to bump a thread but before tossing $500 in the garbage I hope one little bump is acceptable if not addictive, just in case any new news.
Does anyone have any knowledge of my particular mess that could help on the questions above? Much appreciated if so.
Thanks
So one day I was using Samsung Smart Switch to restore my firmware from Lineage OS to default Samsung. Everything was going well until the application gave me some kind of error box.
It said something along the lines of, “Update mode failed to initialize.” After that, my tablet went dark. I couldn’t power it on, or anything. Couldn’t even get it to go into download mode. If anyone could help, please do. Thanks in advance.
龍88 said:
So one day I was using Samsung Smart Switch to restore my firmware from Lineage OS to default Samsung. Everything was going well until the application gave me some kind of error box.
It said something along the lines of, “Update mode failed to initialize.” After that, my tablet went dark. I couldn’t power it on, or anything. Couldn’t even get it to go into download mode. If anyone could help, please do. Thanks in advance.
Click to expand...
Click to collapse
Have you tried holding the Home, Vol down and Power buttons for over ten seconds? It could be that, even though the screen is black, that the tablet is still on.
4929york said:
Have you tried holding the Home, Vol down and Power buttons for over ten seconds? It could be that, even though the screen is black, that the tablet is still on.
Click to expand...
Click to collapse
Yes, I have. And I know the screen isn't just black, because every time I attempt to plug it into my computer no input is detected.
Nevermind, it was actually just my charging universal serial bus port that was broken. I guess I had no battery that time so it ran out during the process of restoring my tablet.
龍88 said:
Nevermind, it was actually just my charging universal serial bus port that was broken. I guess I had no battery that time so it ran out during the process of restoring my tablet.
Click to expand...
Click to collapse
Yeah, I was gonna say, probably the greatest thing about Samsung devices, which almost makes up for the slow updates and the difficulty ROM developers have historically had in supporting Exynos, is Download Mode. It's hardcoded onto a read-only chip, will boot even if you lack a bootloader, and always works perfectly with Smartswitch or Odin as long as your MicroUSB port works, thus making is literally impossible to hard-brick a Samsung device except by causing physical damage (dropping, water damage, sledgehammer, etc). I don't know of any other OEM that has something similar. HTC's S-On sort of did the same thing, but it was on the regular NAND chip which made it less noob-proof than Download Mode, could theoretically be turned off, and was much more restrictive in the partitions it gave developers access to. I'm not loyal to Samsung or any other brand, my current Tab A 10.1 is my first Samsung device and could still be my last if someone else has better specs and better software for a better price in the next generation, but this is one of my favorite features. The moment you suggested you'd hard-bricked it with a simple attempt to flash something onto the regular NAND, I knew something had to be wrong with the battery or MicroUSB port.
Seanthedroid said:
Yeah, I was gonna say, probably the greatest thing about Samsung devices, which almost makes up for the slow updates and the difficulty ROM developers have historically had in supporting Exynos, is Download Mode. It's hardcoded onto a read-only chip, will boot even if you lack a bootloader, and always works perfectly with Smartswitch or Odin as long as your MicroUSB port works, thus making is literally impossible to hard-brick a Samsung device except by causing physical damage (dropping, water damage, sledgehammer, etc). I don't know of any other OEM that has something similar. HTC's S-On sort of did the same thing, but it was on the regular NAND chip which made it less noob-proof than Download Mode, could theoretically be turned off, and was much more restrictive in the partitions it gave developers access to. I'm not loyal to Samsung or any other brand, my current Tab A 10.1 is my first Samsung device and could still be my last if someone else has better specs and better software for a better price in the next generation, but this is one of my favorite features. The moment you suggested you'd hard-bricked it with a simple attempt to flash something onto the regular NAND, I knew something had to be wrong with the battery or MicroUSB port.
Click to expand...
Click to collapse
While DOWNLOAD mode is fairly robust it actually can quite easily be killed by a bad flash.
Speaking from experience. Aboot is responsible for booting the kernel or DOWNLOAD mode.
ABOOT should always be flashed with its corresponding SBL.
If not then the SBL may reject ABOOT as it wont have the correct signature. This breaks a chain of trust which is started from when the device is turned on and the firmware initialized.
(basically this is what is meant by secure boot seen in download mode)
If the SBL rejects ABOOT the device simply will not boot and will appear dead. No DOWNLOAD mode nothing.
Unfortunately I did this by accident when trying some mods out and flashed the wrong ABOOT thus killing my T555.
If you're lucky the device will drop into qhsusb_dload mode, however I think this mode only activates if the SBL believes ABOOT is corrupt not if it's failed the chain of trust.
Unfortunately this didn't happen, so the only option I have is to flash the EMMC direct using something like RIFF BOX in ISP mode(which I already have, but needs an update).
Failing that there is a little trick with an SDCARD adapter that could work with limited success I may try.
So just to sum up anything beyond flashing bootloaders is unlikely to brick the device as this will ensure DOWNLOAD mode is always accessible.
Sorry for venting.
Don't know where to post this, but after the last November update, my Mi A2 broke. It gets into a boot loop or won't boot at all and urges me to do a factory reset.
So I did and it didn't fix a thing. The problem still exists. The only way to 'fix' it, is to remove my SIM card. Cause why would I need a SIM card in a phone, right?
This is the third Xiaomi product that I own (out of three in total), that has update troubles. My Mi Pad 3 doesn't get international updates, so I have to look outside the official channel (I use miui.it for that, bless those guys). My Mi Box 3 is a total disaster. WiFi drops all the time or it won't boot at all unless I unplug it and replug it again. And now this with my Mi A2.
I can live with having troubles with my tablet and TV box, but not with my phone. Even though it's my second phone, I still need it for daily usage. And now I can't use it, due to a messed up update. Again.
I don't know how to fix it. I don't even know if there's going to be a fix at all since most people don't seem to have this problem.
In that case, I will probably have to wait till the next update and hope it gets fixed by then.
If it doesn't get fixed very soon, I will return this phone and get me another one. I don't think this will be much of a problem, cause I can't use my phone for what it's meant to do right now. As I said, it's the third Xiaomi product I own that has update troubles and I'm done with it. I'm not expecting any support coming from Xaomi, cause apparently, they don't care much about giving support over there.
This is the last Xiaomi product I will ever buy. My next phone will be a normal and trustworthy brand again.
I gave Xiaomi a try, cause it looked promising, but it seems it's better to pay a bit more for a proper phone (or tablet or TV box or whatever) instead.
Honestly, don't buy Xiaomi.
Oodles47 said:
Sorry for venting.
I gave Xiaomi a try, cause it looked promising, but it seems it's better to pay a bit more for a proper phone (or tablet or TV box or whatever) instead.
Honestly, don't buy Xiaomi.
Click to expand...
Click to collapse
Wrong place to vent and sorry I don't have a solution.
But I couldn't agree more with your point on pay more to buy a proper phone. It seems xiaomi are slowly missing the consistency from their value proposition.
Yeah seems like the wrong forum to me also...
but, I'd guess, assuming you've done no other mods to the device, the update failed. Normally (or as designed), the device should try to boot the update once or twice, if it fails (as it has), it should then set the other slot to active and boot the previous version OS without the update (obviously).
One thing re returning the device; they sometimes turn it on to verify it boots up. Because your's won't (at this time), that *could* be a problem.
What u want to do next is try to get the device to boot from the other slot (the one that was previously working). I'd try booting it a few times first, to see if the automatic resetting of the slot eventually kicks in.
If that doesn't work, try booting into Recovery (hold vol up and power at same time) and see if there is an option to change the active slot. If not, try booting into fastboot mode (hold vol down and power button at same time), it may have options to change the slot, and if you can connect it to yer computer with usb, and fastboot see's the device, you can then change the active slot with fastboot commands.
The problem is still present after you flash latest fastboot image with miflash?
Change the language of your phone to English, insert SIM and try again.