Related
Just a random thought .. Has anyone heard of any viruses/trojans/worms etc for Windows Mobile 5?
nope.
When I first got my phone I err.... how shall we say.... tried to 'extend' the trial duration of a particular piece of software by installing a cracked version which I am convinced had some kind of malware embedded in it.
After installing the cracked version of the app the phone would automatically try and make a GPRS data connection and transmit / recieve data every time it was powered up - even did so after deleting the app. I never let it stay connected for more than a few seconds so didn't have a clue what it was trying to send or recieve but I'm convinced it wasn't an anti-piracy measure.
Eventually I hard reset the device and manually reinstalled everything minus that one cracked app - I've never had the problem since and yes I did buy a genuine version of the software afterwards (less hassle in the long run ).
Most worrying thing is that at the same time I was evaluating most of the Antivirus/Malware packages for WM5 and none of them picked it up or flagged any errors/problems - even those supposedly supporting Heuristics.
Like I said I'm convinced the file was some kind of trojan/malware and as a note of caution to anyone considering playing around with warez'd stuff - remember play carefully!!!
Your antivirus software didn't pick it up, because it's not a virus.
Unfortunately, the hacked product you were using was doing exactly what it was programmed to do... There is definitely something to be said for using only "Signed" applications from legitimate vendors!
I hate to say it, but "it serves you right..." Don't steal software!
@goestoeleven
The original poster actually asked about viruses/trojans/worms etc. not just viruses, hence my reply to him.
Regarding your comments...
Firstly, at least two of the antivirus/security software packages I was testing supposedly also detected Trojans and other malware so your somewhat conceited reply is factually incorrect.
I'd also like to point out that very few of the applications I have purchased from legitimate vendors are actually 'signed' - this was certainly the case with original vendor supplied CAB file of the 'infected' application that I eventually purchased.
Finally, I would like to remind you that I did state that I eventually bought the software concerned as I have done with all the software I use on my phone (and my PC for that matter) and therefore I resent the implication that I have 'stolen' anything.
I appreciate your comments may have been well intentioned and somewhat 'tongue in cheek' but I don't feel your comments of 'nope' and those you listed above really contributed to the discussion regarding the possibility of WM5 malware being out there...
regards...
Xerxes
Well, I'm glad you received my message in the light-hearted manner in which it was intended.
Back to spyware/viruses/malware: people that write these things want to access/infect as many machines as possible. To do so, and to ensure their maximum bang-for-the-buck, their best bet has always been the Windows desktop install base. There's a reason why you haven't seen too many (if any) viruses for OS/2, linux, or Mac... it's simply not worth it.
Now the PPC platform is certainly growing, and contributors to this board are certainly a big part of that. Do I think that there could be a potential for bad stuff on WM5 devices? ABSOLUTELY, and you've seen it yourself.
But do I think it's an imminent threat and/or "clear and present danger?"
Nope! (tongue-in-cheek again)
We protect our desktops - and leave our GPRS/UMTS-PDAs wide open? Not me. Using http://www.protectstar.com/englisch/home.shtml firewall for WM5. Developed in Germany.
Not exactly a steal at 40 dollars I believe, but protects from phonehome, dialer and - in the Pro version - from viruses.
Hi, I'm hoping someone can help me.
I switched on my HD2 earlier, to be greeted with a screen reading:
"
This concludes the beta test of this
software release. Thank you very much for
your time and effort in helping make this a
great product for our customers.
To obtain a newer release or further
information, please visit the web site that
you used to obtain your current beta
release.
"
This writing is on just a plain white screen, with the task bar at the top. My connection is showing as disconnected (both icons), my volume, battery, and clock icons are also showing.
I cannot get past this screen, no matter what I try.
I cannot connect to active sync, instead, it goes straight to mass storage/disk drive mode.
Hardware keys do nothing except the power button, which will only put the handset into standby.
I am prepared to flash to a new ROM if I have to (nothing new there ), but I need to retrieve a few texts and numbers I have added since my last PIM backup.
Is there anything I can do to solve this, or is it just a case of swear a lot, and throw a new ROM at it?
Thanks.
Steve.
http://forum.xda-developers.com/showthread.php?t=673920
Seems like there are people who experience the same thing.
Not sure if there are any other way out apart from hard reset.
F*cking M*ther F*cker!!!!!!!!!!!
Ok.
Thanks for at least pointing this out to me.
Time to start all over again
I believe this screen appears on HTC and carrier test and sample models given out to internal staff for evaluation and feedback.
Where did it come from?
stabloid said:
Hi, I'm hoping someone can help me.
I switched on my HD2 earlier, to be greeted with a screen reading:
"
This concludes the beta test of this
software release. Thank you very much for
your time and effort in helping make this a
great product for our customers.
To obtain a newer release or further
information, please visit the web site that
you used to obtain your current beta
release.
"
This writing is on just a plain white screen, with the task bar at the top. My connection is showing as disconnected (both icons), my volume, battery, and clock icons are also showing.
I cannot get past this screen, no matter what I try.
I cannot connect to active sync, instead, it goes straight to mass storage/disk drive mode.
Hardware keys do nothing except the power button, which will only put the handset into standby.
I am prepared to flash to a new ROM if I have to (nothing new there ), but I need to retrieve a few texts and numbers I have added since my last PIM backup.
Is there anything I can do to solve this, or is it just a case of swear a lot, and throw a new ROM at it?
Thanks.
Steve.
Click to expand...
Click to collapse
NRGZ28 twitter from last night mate
It seems the older ROM of November.. December.. even January are starting to expire. Even the patch that all chefs apply only extends the >beta testing period, not eliminate it. So I advise you to either upgrade to a newer ROM, or flash one of the 21XXX ROMs that never expire..
Hello to all good guys in xda-developers forum.
This is my very first post and I really feel desperate and need your kind help.
New Acer iconia with stock firmware 3.2.1 was nicely running this morning until I tried to root the device.It was supposed to be very simple process and not to get into dirty complicated procedures but the gingerbreak.apk did not work as expected so I tried alternative methods.What I read in various forums was that the gingerbreak application is not able to root the new firmwares version so I tried to downgrade the firmware to 3.0.1.
Downloaded the Acer stock recovery firmware EUUs_SBK_Acer_A501_0.017.01_PA_ATT.exe and attempted to flash onto my tablet .I think I did all necessary pre-installation checks.The process started but it stopped on 10 percent for about 30 minutes without any progress.Only Acer logo was displayed and 'entering file downloading mode' at the top of the screen.
After long time no change I finally gave up and unplugged the device from the USB port and restarted but nothing works since then.
1. No vibration on Start
2. Black screen
3. No new USB device appear on my PC
4. No sign of any activity other then power button light
I guess the original firmware was wiped but the new firmware was not flashed...for whatever reason...perhaps the worst scenario.
I will really appreciate If anybody may give me advice how to fix it.
So it turns on but does not display anything? Have you tried to hold the power button and volume down button at the same to when you turn it on to try to get it into recovery. Also there is a little reset button on the side you can try to push.
Sent from my A500 using xda premium
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
acera500 said:
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
Click to expand...
Click to collapse
Try this thread. Look about halfway down, and you'll see almost the exact thing you did, and how this guy got it going.
http://forum.xda-developers.com/showthread.php?t=1291747
Basically you can run a search for APX in the main forum threads and find some other posts, but hopefully this will get you going.
I pulled this from the general forum (eventually), but you can also search the Q&A main forum page as well, and the dev forum.
Another link;
http://forum.xda-developers.com/showthread.php?t=1255519&highlight=apx&page=2
If its new just return it to the store for another one.
Sent from my A500 using xda premium
Acer or the store did not brick it
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Piece of cake to fix if you kept you USB serial number (from the downgrade tool)???
===== If you have your USB serial number ====================
1. Lets assume you know your USB serial number. If not, then you might be able to get it from your registry.
2. Download my flashing tool at http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
a. Open up the readme.pdf for the instructions on how to flash
3. KEEP your acer unplugged and run the program
4. The program will install the APX flash drivers and will tell you to plug in the USB. Ignore this step. It will not work. In the instructions skip steps 3, 8, 9, 10.
5. Eventually the flashing tool will timeout because you do NOT have the tablet connected. It will then display a message box telling you how to use a paperclip and the power button to get you into APX mode. THIS IS THE secret to getting the tool to flash your ACER. However, once you get it into APX mode you will need your USB serial number (without it, you are fubar).
a. Plug in the tablet to your computer with the USB and paperclip yourself to fastboot.
6. Now in step 11, enter your USB serial number
7. Now just follow the rest of the instructions.
====== NO USB Serial number ==========
If you do not have your USB serial number than you are going to be out of luck, unless you have ever connected the device to your computer. If you did, then your registry will have a history containing your serial number.
Google usbdeview tool and download it. This will show the serial number of any USB device you've connected to your computer.
===== No Serial number, never connected it, what to do ==========
If you have no serial number and cannot get it, then hopefully you can get to recovery mode (power & volume) and flash using a signed update.zip from ACER. Download one of the update.zip's and put it on your external SDCard and then boot to recovery.
=== Bricked and No serial number, never connected, and you fubar'ed the recovery image ===
If you never connected your table to the USB and your computer to get the USB serial number then you are NOT going to be able to flash it to fix it.
If you fubar'ed the recovery image then you won't be able to get into recovery to run the ACER update zip.
At this point, you can still get your tablet into APX fastboot mode using a paperclip and the power button. But I know of NO way to flash it without the USB serial number and I know noway to get the USB serial number from the APX driver. I've tried and looked at getting the serial number from just APX mode, but I cannot determine how to get it. Someone out there might know.
Hope this helps,
TD
Your CPUID can also be found in the uid.txt file in your cwm backup folder - /mnt/external_sd/clockworkmod/backup/ - just remember to drop the 0x when you need to enter it
erica_renee said:
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Click to expand...
Click to collapse
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
wade7919 said:
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
Click to expand...
Click to collapse
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Why locking a bootloader will cost ACER billions
Moscow and wade7919, you both make good arguments.
But it is what point of view you're coming form. If I bought a car and changed the RIM's on all 4 wheels and the engine blew up, would GM refuse to honor the warranty?
However, if I put jet fuel and alcohol in for gasoline and blew the engine why would they honor the warranty?
So, the question here is does rooting a device cause actual damage to the device thereby preventing rooting saves them warranty issues? Or is the device also considered to include the software and is covered under warranty?
I'm not taking sides here, but you both are making very good points but with different examples at different points of view.
So, lets look at other items and see if we can draw a parallel. If I buy a brand new Dell computer and send it in for Warranty and there is nothing wrong with the hardware they charge me (correct?). So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty.
So, why does an Android MFG take the warranty one step further and include the OS and take steps to lock it so you cannot change it? Well, this is because nobody owns the OS (it's open source) therefore they take ownership of the build. Because there's no Microsoft to blame, they lock the software and consider it to be part of the overall device (Apple claimed this in their lawsuit). So, in the MFG's mind, there is no difference from the screen, keyboard, or the firmware & software.
So the question is what do you think should be covered under warranty? Most people think it should be just the hardware like a PC. Others see the whole device which includes the OS.
My point of view:
What follows is my rant and my opinion (you are warned )
In my opinion, I had NO problem until they decided to lock the bootloader. I have no problem with them claiming warranty from A-Z and if I change anything they won't warranty it. No problem, I understand that and accept full responsibility. But by ACER locking the bootloader they went too far.
To me this would be like GM welding the hood shut on my car. Better yet, it would be like me waking up one morning and opening my garage to get in my car and discover that during the night GM welded the hood shut. This, in my opinion, is illegal. Matter of fact, in my opinion, it violates US Federal hacking laws because they enter a system and destroyed data. I eventually think OEM's will get a class action suit filed on them for this.
Secondly, Windows 8 is going to be the game changer. OEM's can now make a hardware device and sit behind only warranting the hardware. You have a problem with the OS, call MS. Also, there is a HUGE (I mean HUGE). Did I mention HUGE, demand for tablets in business. Businesses will NOT put a device that has all these consumer games and social networking loaded into the workforce. There are billions in business applications that can be made, but you cannot sell them if they only run on a tablet that cannot have games removed etc.
Example might help: Medical field <- Think of all the applications a tablet can be used to save costs in hospitals. Do your really want your doctor or nurse etc using this tablet on facebook? Insurance company's, law firms, retailers, traveling sales, etc etc (Government). The list goes on.
Developers will see this huge opportunity and will write applications because they can sell them to A-Z and the business buying them will buy them because they can remove facebook and gmail from their company owned tablets. Now, as more and more developers move to Windows they'll drop Android. Want another example, read about Netflix and the issues they have had supporting a fragmented Android OS. So, business applications will move to Windows, but you might say so what, the consumer market is still there. True, but all you need is one killer application that everyone will want and for that to only be on Windows 8. Want some examples, here's my list, NFL (or sports), Netflix, Skype (gee owned by MS now isn't it?), or something new.
Bottom-line is this, if ACER and the others want to lock their bootloaders then they have just taken themselves out of the game for any business sales. Can you imagine walking into a boardroom showing the Government how your new VA application will save the VA Hospitals millions next year alone and improve veterans healthcare. Your application runs on any HC Android tablet. Everything is smoking, going great, as you hand your tablets, ACER a500', around the room. They are loving it. You just hit 'pay-dirt', then someone says hey I see these ACER's have gmail, facebook, blah blah. We cannot have government employees using tablets with those applications loaded, your installer removes them doesn't it? Silence enters the room, all eyes are focused on you. Your mind see millions escaping which were just within your grasp, you pause, you think, and you say YES General as you grab your Motorola Xoom and say 'that's why we recommend you buy nothing but Motorola.'. ACER just kissed millions in sales goodbye (oh and this is a true story).
i do believe acer should lock the bootloader on there devices.
However thee are things I would be doing with my tab if it were not locked.
Acer should give us the ability to flash the bootloader and not use the proprietary software. Lock that software to there bootloader.for there protections.
Give us a wway to unlock it..AT OUR OWN RISK..
So it should be locked but have a way to unlock it with the end user understanding they are totally on there own ..
I would be OK with voiding my warranty.
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Moscow Desire said:
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Click to expand...
Click to collapse
Very well put.I do know of a few people who have sent there device to acer after messing it up installing rom and telling acer.acer still fixed it free.
Honesty is always best
The evils of rooting
I'm still missing something here, why locking a bootloader does anything. Go get a Mortorola Xoom (not the FE) and you run the unlock OEM. It tells you that you are unlocking it. It tells you that you unlock it at your own risk. You cannot relock it until it is 100% back to stock. It asks you three times are you sure.
Locking the bootloader and treating everyone as an idiot is the problem. Just do what Motorola does, and stop being everybody's keeper. If they want to 'Police' this then you should have to call ACER and they fax you a form. You give DNA to prove who you are and fax it back. Then you go to a mandatory rooting class, that lasts for 5 days, where ACER preaches to you the sins of rooting. Then you have to take and pass a test. Then and only then, after passing the test you get a certificate. Then you call back, give them your certificate ID. Now they give you the secret key to unlock only your tablet.
That's the ticket,
TD
Bottom-line, it's not that they locked the boatloader, it's that you cannot unlock it. Like I said, go out to your driveway some morning and find that GM welded the hood to your car shut because they think you are stupid and shouldn't be opening the hood. Mind you that YESTERDAY, and at the time your bought it, it was not welded shut. That ladies and gentlemen is what ACER did with their OTA.
Moscow Desire said:
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Click to expand...
Click to collapse
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
wade7919 said:
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
Click to expand...
Click to collapse
I still like my car comparison
I make the car comparison to illustrate a point, because when I compare tablets to a PC everyone piles on *****ing about MS.
Bottom-line it doesn't matter if it's a blender or a PC. I own it, you own yours and I can do what I want with mine as you can with yours. Now, again I have a BIG(did i mention BIG issue with them changing it on me after I bought it.
To get back on topic, is the original poster still out there?? Has any of this helped? Are you still bricked?? Give us an update so we know if anything worked or you still need help.
The device was returned and accepted for replacement by the shop.Got new one and feel very nervous to start rooting procedure over.I was really lucky that they did not charge me anything but I really want to know what I did wrong so I don't brick my new device again.
I will provide further details soon about my computer OS and firewall settings and perhaps we may figure out what I did wrong.
To all good guys who send me them suggestions and solutions I wanna say big THANK YOU !!!
Your help is really priceless and thrilled me deeply. Will update topic soon
Happy New Yer to all Android fans!!!
So...Back on the subject.
My device was purchased in Japan and its current firmware version is
Acer_A500_7.009.03_AAP_CUS6JP
Q1. Can I flash US or World Wide firmware version on that device.
Q2. Does anybody know the Acer's ftp download server address for Japan
Q3. I think its a good idea to dump my original stock firmware but it seems there is no way doing that prior rooting.So..kinda stuck .any suggestions appreciated.
P.S. I'm thinking about flashing the latest Rooted rom 3.2.1 V3 by timmiDean (thanks for your hard work) I read the instructions very carefully and I think that everything will go smoothly but just in case (considering the specific Japanese firmware version)
would appreciate any further directions by the author.
Thanks
I really just need to vent about this...
I initially emailed on 05/09/2015, I've made it nowhere in the RMA process other than verbally assaulting their tech support (I only sort of feel bad). I've been moved around to five different people. The first three told me the exact same thing. The fourth did what the third said they would, and the fifth is what the fourth said they would be.
05/09/2015 Melissa wanted a video of the problem.
05/15/2015 I told her that's not something I should have to do for a well documented defect.
05/17/2015 Chris wanted a video of the problem.
05/17/2015 I told Chris I didn't have another device to record video with and again said I thought it was ridiculous I had to do this.
05/17/2015 Chris requested a screencast video of the device showing its ghost touches.
05/17/2015 I told Chris that it was a cool day so that the device was not acting abnormally at the moment and asked if I should warm it up in the oven.
05/17/2015 Chris thanked me for the reply and said we would pick up once the problem showed again. 05/17/2015
05/17/2015 I sent Chris a link to "lmgtfy" with the search query "one plus one touch screen issues". 86.8M results. I then told him if we waited for my device to show the defect again, that I could be in a life or death scenario and being unable to unlock my device is just... I'm dead. Worst case, but seriously you guys. It could happen. 05/17/2015
05/17/2015 Chris again thanked me for the reply and said he would be escalating it to the proper department for assistance. 05/17/2015
05/19/2015 Elmer wanted a video of the problem, and pictures of the device.
05/19/2015 I told Elmer I didn't have another device to take video or pictures with, and then suggested he do an Advance RMA so that I could take pictures with a properly function OPO.
05/19/2015 I was with a friend that day and I low and behold, the scenario where I couldn't unlock my phone showed up! So I sent it to them.
https://drive.google.com/file/d/0B4MvQwyeqEj2M1dQSWNMaFdNOGs/view?usp=sharing
05/20/2015 The next day I send another screencast video of my phone.
https://drive.google.com/file/d/0B4MvQwyeqEj2X3BlVW5tYURHZzA/view?usp=sharing
05/21/2015 I send them an email saying I like how quickly the replies were when I was fighting them on the videos, but then don't reply when I do. I also told them they had lost me permanently as a customer. "it's good to end bad relationships early."
05/22/2015 Chrystle sends me links to two different zip files. One called, ONEPLUS+ONE-FIX-Windows.zip, and the other OPO-Display-patch.zip. She informs me that they are Windows or Mac only.
05/22/2015 I send two different messages, one saying that I do not run Windows or Apple operating systems on my computer, requesting that I get something that will be flashed in recovery, or something that could work with Linux. Fast forward through my work shift. I get home and download the files anyway and extract them. there is a .bat file in there with a bunch of commands flashing partition files using fastboot. open up a terminal and I start copying and pasting the lines so I don't make any mistakes. Get to the one about flashing the userdata partition, and the script as a typo. the file has a capital G and the script is showing a lower case g. Those are 500MB "patches" just FYI. One did nothing, and the other made it worse. They were both CM11S. http://i.imgur.com/bEq9Boy.png http://i.imgur.com/InuCpLo.png respectively.
05/23/2015 I send several messages. It's early AM but I send an email asking if it's amateur hour because of the typo in the first rom. Then another message saying that the typo was also in the other patch zip. Yeah, that's right. both zips had the same typo'd batch script. It's funny they treat us like we know nothing. I finish the email with "Idiots."
05/24/2015 Cherie asks if my device was ever dropped, bumped(???), or exposed to liquids. Also goes on to explain that the CPU and Camera are close together and that the camera material transmits heat quickly so the device can feel warm there. Then suggests I close apps running in the background. Also then recommends that I recondition the battery by fully charging and discharging it three times. And also says not to use the phone while it's charging because it needs to rest. She then wanted me to install a multitouch testing app to screencast, and also requests pictures.
05/24/2015 I say I've never dropped the device, and am unsure what they mean by bumped. And say the device hasn't been anywhere near water in my possession. (near enough to cause an issue anyway). I'm just going to quote myself here, "What causes overheating of the display? And my typing is not the problem. HTC MyTouch 4G, Samsung Galaxy S3, LG Nexus 4. Those three devices could keep up with me. Ah, those were the days. Such fond memories of accurate touch screens.S o the CPU is close to the other components in the phone? That's amazing! How do you do it in such a small package? Crazyness. Though, my Nexus 4 is even smaller, must be magic to be able to fit the cpu and camera in there together. Material of the camera transmits heat... Well, most things are conducive of heat. I close background apps frequently enough. I keep the screen brightness close to 50%. The phone needs a rest while charging? Why is that? Did it get fatigued? Is it tired? Did it have a long day? I've never had an electronic device that "needs to rest". Sounds like YOU NEEDed to improve the cooling capabilities of the device. My battery usage is also not abnormal, nor under heavy load does the battery get hot. I get 7 hours of screen on time. That's absolutely amazing! Now if only I could use it for those 7 hours I'm able to turn the display on. Common problem with Li-Po batteries that are old. Are you saying I have an old battery in my device that needs to be reconditioned? I better not since I've only just bought the phone a month ago. Pull the notification drop down menu down, press the back button, and restart the device... What? How's that any different than just rebooting it? The last step of this RMA process pretty much sealed the deal that yall are idiots, and this is just kind of the icing."
05/25/2015 Cherie requests pictures of my device. And says if I do she promises my device will be like new once she forwards me to their Level 2 support.
05/25/2015 I send them the pictures they requested.
05/26/2015 I send them a screencast AGAIN saying, "Can we stop playing games?"
https://drive.google.com/open?id=0B4MvQwyeqEj2dGNidWNxRlkzVFE&authuser=0
05/26/2015 Llores sends me an email about setting up a remote session with Level 2 support. Requests that I download a few files and to set up an appointment. For Windows there were five zips linked. One for OxygenOS(I'm presuming) "oxygen-dlt.rar" 784MB. One for CyanogenMod(again, presuming) "DLT-CM.rar" 512MB. a Certificates rar that I did not download, as these are probably Windows driver things. The Android SDK which I did not need. CM11S from cyngn website 510MB. And an archive titled AFX. Which has two files in it, a persist.img and a reserv4.img... a measly 10KB.
05/26/2015 "Are you new? Or did you just not read anything? The operating system on my computer is Debian Linux. No one needs to remote access my computer because I've already proven I'm smarter than you. I do not trust any of you to access my personal computer. It is unnecessary. If you're level two tech support maybe you can fix the amateur hour typo in the previous fixes automated scripts that didn't do jack didn't squat for my device. My device has an intermittent hardware issue that needs to be resolved with a different device that has been factory reconditioned or refurbished. No amount of software is going to fix a hardware issue. Waaaaiiiittttt, you guys are that dumb huh? Holy ****. LOLOLOL." and shortly after, "I hope you can understand, that I do not want anyone accessing my computer, and running commands. A miskey from an idiot at OnePlus (witnessed from a script typo and the inability to read a conversation history) could erase all of my personal files. I would be highly aggravated, and you've only seen me mildly irritated."
And there we are so far. This kind of service is absolutely unacceptable. It doesn't matter how much the phone was. Someone on the OPO forums said they paid for the phone, not tech support and warranties.
Also, the DLT files are password protected, which I'm sure the L2 support lackey knows the passwords, I'm trying to break in to it using rarcrack, but.... bruteforcing something is relatively slow.
05/27/2015 Cherie emails me again and from the sounds of it, she had no recollection of our previous conversation. She says that Level 2 tech support needs to remotely access my computer.
05/27/2015 I tell Cherie that I've already mentioned I will not be allowing anyone from their company to remotely access my computer. Request one of their computers be sent to me for them to remotely access and flash my phone. Then go on to say that they probably won't do that because you don't trust me with your data as much as I don't trust them with mine. Tell them I will be going through with a paypal dispute.
05/27/2015 Cinderella says, "Thank you so much for the response. We understand your point of view on the said issue,I understand how frustrating it is of not being able to use your Oneplus phone and have to go through with this process. Many felt the same reaction too. In the long run, numerous Oneplus owners found out that patch fix resolved their touchscreen issues as it may install those missing "TPK firmware" on the phone."
05/27/2015 I say I don't understand why someone needs to remotely access my computer when I've already proven that I'm more than capable. And that if she gives me the password I'll be out of their hair, forever and ever.
05/27/2015 Cinderella says she understands that a remote access can be challenging but my ticket is being handled in a timely manner by tech support and that remote sessions are recorded for security purposes.
05/27/2015 I tell Cinderella that they've done nothing to gain the trust for me to open up my computer to them. Say if they give me the passwords to the .rar's I would set up a remote session.
05/28/2015 Ethan emails me informing me that it is the tech that will be unzipping the files during the remote session, and to let him know when I've booked an appointment.
05/28/2015 I get on the site to book a remote session. The next available time is 06/06/2015 @ 6:30pm. No idea if that's local time or not, But either way, who is at work at 6:30pm OR 9:30PM? I send Ethan an email telling him the company is a joke, and that I'm getting my money back. I tick the "this issue is resolved" and hit the reply button.
I am really sad though, I love the phone and I wish it would work properly.
they are only thiefs, no other adjective describe them.
They put a fail cheap ****ty display on this device, and after a random time (depend from many enviroments, temperature, isolating, what you eat... ) it appears the non responsive/ghost touch issue.
They don't want repair or change, and if you have only a micro dent on the frame... goodbye
the incredible, it's that they have prepared some zips with naming "fix touch" etc... they are ridiculous... This phone have a target of 90% middle/high geek, so, they don't want this bull**** no resolutive sw, but they want try and flash whatever they want, when they want, and they want that almost the device have a display working !!!
They stop say try what rom you prefer, your warranty will remain..... YES, RIGHT, because we haven't any WARRANTY on display !!!
This is exactly why I buy used, broken devices for dirt cheap and repair them myself. I got my 64gb 1+ off eBay for $115 after repairing it's screen.
Screw warranties, support, etc.
silverton said:
I really just need to vent about this...
I initially emailed on 05/09/2015, .....
Click to expand...
Click to collapse
I have similar experience and I too reach the point that tell them "NO way I gave you remote control"
They sad again, that second level technical will decide if my phone is for RMA.
I think with my refuses to gave them access they will close my case. I think it is not legal but.....
I just want to send phone and they fix or gave new one and I sale fast.
What we must do?
I bought phone in October, so obviously I can't claim refund from PayPal
It's been... 6 or 7 weeks now since I first submitted ticket. Somehow I managed to skip the remote session, went from asking me to book session, to setting up the phone getting picked up.
But...
A week after they said they received it, they come back saying water damage, apparently the the LDI in headphone jack was tripped and want me to pay for repair. I basically argued back, told them it had never been anywhere near and liquids.
Lo and behold, they come back saying they've made a mistake. On re checking, there is no water damage, and so now will replace my phone. Imagine I'd caved and paid for repair, or just had them send it back...
... Finding it hard to believe they made a genuine mistake...
mozyman said:
It's been... 6 or 7 weeks now since I first submitted ticket. Somehow I managed to skip the remote session, went from asking me to book session, to setting up the phone getting picked up.
But...
A week after they said they received it, they come back saying water damage, apparently the the LDI in headphone jack was tripped and want me to pay for repair. I basically argued back, told them it had never been anywhere near and liquids.
Lo and behold, they come back saying they've made a mistake. On re checking, there is no water damage, and so now will replace my phone. Imagine I'd caved and paid for repair, or just had them send it back...
... Finding it hard to believe they made a genuine mistake...
Click to expand...
Click to collapse
**updated with a sad ending**
You're not the only one I've read about having them try to claim that the liquid sticker was tripped, and then back track when they're called out on it.
Sounds much alike the issues I have with OnePlus support right now. My 2 has what I strongly suspect hardware issues. I can say that I'm pretty sure, that is after worked for a Swedish/Japanese mobile manufacturer for almost 16 years. So I know a bit about mobile phones . I think in the end the wankers will not give me another phone. Their tactics is to f**ck you around until you give up. It's a shame actually, I love their products but the company is rotten to the core how they conduct themselves. I think I'll write an email to Carl Pei in Swedish and tell him my two cents about this matter. I don't except it to do any good but perhaps I'll catch him of guard. If anybody is interested I'll let you know how that wen't down.
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