Related
Offer:
I've got a $30.00 PayPal for someone with decent rep here to walk me through the update.
History: This is a new virgin phone, exchanged today. (Sun) The OTA killed my previous phone and I was unable, for whatever reason, to restore nandroid, backup, nada. Until this morning, that was the best phone I've ever had because of this forum and esp the Tips & Tricks thread.
It had: Root, Rom Manager, Titanium Backup, Ryan's OCLF, Autostarts, and MOBILE AP wireless tethering app. (This one is a must for me.)
What I want:
I want the JI6 update installed and the above programs re-installed per the Tips thread... In whatever order you think is best. We verify these things work and I send money immediately. My word is good. (I can re-install my 40 odd apps afterward on my own time.
Background:
I have followed the Tips thread instructions for ODIN. (Open ODIN, press vol up & dn, plug in wire, see COM msg in box, (debug on) mount phone, Pit>...512, PDA>...JI6, START. ..... Nothing! 2 seconds later the message box says something like {All threads complete. 0 succeeded, 0 failed>}
Bottom line:
I've read posts for hours but since I don't really know what I'm doing well, I am also unable to sift through all the advice figuring out which poster's setup is like mine. At this point, I just want it done right.
I will edit this post when it's done. Thanks for reading.
Respond: [email protected]
I'm in the same boat, as far as trying to use Odin. Broken phone, nothing working for me.
So, you took your phone to the store, told them you applied the update and now you're stuck on the vibrant screen, and they just gave you a new one right then and there?
you can drop me a pm and i can try and get you through it. Wont take your money though. Make sure you have odin 1.3 downloaded and the odin flash file for JI6 downloaded. If you can get adb working you get bonus points.
Are you hardware locked? if so you need to download the patch for it also found on here. If not should be easy to get ya up and running with the above mentioned things in place.
If I went to fast or confused you just say so in the pm and we can go as slow or as fast as you need.
adm1jtg said:
you can drop me a pm and i can try and get you through it. Wont take your money though. Make sure you have odin 1.3 downloaded and the odin flash file for JI6 downloaded. If you can get adb working you get bonus points.
Are you hardware locked? if so you need to download the patch for it also found on here. If not should be easy to get ya up and running with the above mentioned things in place.
If I went to fast or confused you just say so in the pm and we can go as slow or as fast as you need.
Click to expand...
Click to collapse
there is alot of us who had bricked our own phones who can help you on this issue i helped someone just the other day unbrick his phone
pm either of us we dont mind helping
hellcatrydr said:
Offer:
I've got a $30.00 PayPal for someone with decent rep here to walk me through the update.
History: This is a new virgin phone, exchanged today. (Sun) The OTA killed my previous phone and I was unable, for whatever reason, to restore nandroid, backup, nada. Until this morning, that was the best phone I've ever had because of this forum and esp the Tips & Tricks thread.
It had: Root, Rom Manager, Titanium Backup, Ryan's OCLF, Autostarts, and MOBILE AP wireless tethering app. (This one is a must for me.)
What I want:
I want the JI6 update installed and the above programs re-installed per the Tips thread... In whatever order you think is best. We verify these things work and I send money immediately. My word is good. (I can re-install my 40 odd apps afterward on my own time.
Background:
I have followed the Tips thread instructions for ODIN. (Open ODIN, press vol up & dn, plug in wire, see COM msg in box, (debug on) mount phone, Pit>...512, PDA>...JI6, START. ..... Nothing! 2 seconds later the message box says something like {All threads complete. 0 succeeded, 0 failed>}
Bottom line:
I've read posts for hours but since I don't really know what I'm doing well, I am also unable to sift through all the advice figuring out which poster's setup is like mine. At this point, I just want it done right.
I will edit this post when it's done. Thanks for reading.
Respond: [email protected]
Click to expand...
Click to collapse
Im pretty sure i know what u are doing wrong man. pm me and i can help u out if u havent already
I gave up on unbricking.
No Trunk, It was more of an escalation from a gentle request (at which point they told me "2 weeks & we'll mail it to ya' ".) through several layers of increasing... uhhh... 'amplitude', ("Okay, We'll do priority mail; 3 or 4 days.") culminating in chaining the duct taped Tmo rep's feet to the back of my hog for a quick ride up the street. ("I think we have one in the back, let me check...")
Cyber, your posted phone 'resume' sig is the scariest thing I've ever seen. (Except for my ex.) Does that thing have photon torpedoes too? Krap!
Okay, just kidding 'bout all that. Thank you guys for responding. Will send PMs tomorrow. (1 more brick & I'm gonna need mortar...) About 3-4 pm pacific time. Again, thanks.
I had root but no roms, no adb, no hardware unlock. I'm not a sophisticated power user. I loved it the way it was, except for the GPS/compass thing. It was fast (with the lagfix) and tethered wirelessly & easy w/ the Mobile AP, & I had some control over the running programs.
phone power off. (remove battery if you think it will help)
ok had my phone brick today took about an hour of googling, reading, downloading etc to get it to work again
Load odin
plug phone into USB (power off mind you) press and hold both volume keys at once, plug into PC, this "should boot you into download mode ( android guy with shovel screens says DOWNLOADING! once it loads into download mode you should see some Com info at the top left of odin, thats your cue to load the PDA and PIt file. check PDA box press start, and wait, installation should take about 5 mins
I was in motion with ODIN finally, when I accidentally pulled the USB cord out of my laptop. Now, all I get when trying to get in download mode is a graphic of a phone, a yellow triangle with exclamation mark, and a computer.
Holy crap this is a learning experience. Anyone know what do do?
adm1jtg said:
... Are you hardware locked? if so you need to download the patch for it also found on here.
Click to expand...
Click to collapse
There is a patch to correct the hardware lock? Please provide a link.
Thanks
Edit Just found the link, hxxp://forum.xda-developers.com/showthread.php?t=802763 (replace the xx's with tt), and can't wait to fix my phone.
trunkstar1 said:
I was in motion with ODIN finally, when I accidentally pulled the USB cord out of my laptop. Now, all I get when trying to get in download mode is a graphic of a phone, a yellow triangle with exclamation mark, and a computer.
Holy crap this is a learning experience. Anyone know what do do?
Click to expand...
Click to collapse
Ok here is your next step by step. First take a deep breath you CAN definitely recover this....
you need to hold down the up/down volume and the power button. The yellow triangle image will go dark and come back. You need to wait till after it goes dark twice then when the image shows up for the third time release the volume side. wait about 5 seconds and release the power. Should jump you back into download so make sure your odin is up and ready
adm1jtg said:
Ok here is your next step by step. First take a deep breath you CAN definitely recover this....
you need to hold down the up/down volume and the power button. The yellow triangle image will go dark and come back. You need to wait till after it goes dark twice then when the image shows up for the third time release the volume side. wait about 5 seconds and release the power. Should jump you back into download so make sure your odin is up and ready
Click to expand...
Click to collapse
Awesome. Thank you so much. What a debacle. I'm stock again. Or at least, it looks like stock again. Now, to get the OTA update and hopefully this time it won't break my phone. I have no idea why it broke the last time I tried it.
My phone was so personalized before, I feel lost, like this is someone else's phone.
Stupid question... Why not just odin the official JI6 file that's posted and be done with it. Even better forget the JI6 and look at one of the awesome roms by eugene or bionix as they both use JI6 as their base?
Dude....where in OC are ya ?
I'm in Seal Beach,if you don't get it fixed before your stated 4pm pst time...gimme a holler and I'll even bring my laptop and cable.
Save the 30$, but you're buying the beers
adm1jtg said:
Stupid question... Why not just odin the official JI6 file that's posted and be done with it. Even better forget the JI6 and look at one of the awesome roms by eugene or bionix as they both use JI6 as their base?
Click to expand...
Click to collapse
Not sure if that was for me or not, but I don't even know what JI6 is... flashing stock was the first time I ever Odin'd anything before.
I don't have much of a rep here, but here's how I did things. I installed OCLF from the market, and rooted (and only rooted). Then I installed ROM manager and did a nandroid (and I did one after each change I made to my phone as well). Then I updated to JI6 through odin. After that, I gave myself MobileAP. Then (because I was hardware locked), I used odin to fix that. As far as I know, you can install everything else you got from the market from there (all root apps not already installed included). I can't really tell you how that lag fix from OCLF works with JI6, as I never actually used that part of the app (I only used it to root).
As a side note, you may get an error with odin if you aren't in download mode (but you may still get a com message). For a sure fire way to get into download mode, open odin, and then plug in your phone (completely booted). Use the adb command "adb reboot download" and you'll be in download mode and ready to use odin. Also, if you mess up, as long as you can get into download mode, you can use odin to flash back to how your phone originally shipped.
Update
Hey guys,
I HAVE JI6!!!
I'm the OP & I just logged on to send the PMs to be rescued. I saw the mini-kies method of installing JI6, tried it, and it worked. I'm re-rooted, oclf'ed, clockworked, & have re-installed many apps.
The MOBILE AP seems to be my last major hurdle. I forgot how I did it last time but it worked great! Now the instructions I think are different??? I don't remember any "flashing" with CW though. I've never flashed anything. I've read every post HERE but I'm gunshy now. Is there a "for dummies" way to do this?
Also, I have lost my Haptic feedback. It seems to be set correctly, but it's just not there. Even when I adjust the intensity up to full, nada. It may have happened after the OCLF install, or playing with Swype, not 100% sure. It definatelt was working an hour ago... Any ideas on this? Thanks.
Thanks for the "PM me" responses. You guys are slowly curing my ignorance. (very slowly...)
Member character...
Yep. The Brickmaster is back. After a 3 day long recovery process from a new phone, I had somehow done it again...
This is to say thanks to the multiple members who offered personal help but in particular, to the one who gave it. After a PM, this man called me back and for 2 straight hours on a Friday night, with no request for, or guarantee of payment, patiently led me through the technicalities of an Odin recovery. Somehow, he fixed my phone. And I got a little more education.
During the course of this call, it turned out he is an Iraq war veteran with a new baby who is re-enlisting in the military to serve his country even more! Thank you so much for your help, and my gratitude for your service to our country.
.................................................................................................
As for me, being a natural born electronics genius is rough. Last night I elevated the art of brickification to a new high. (2 clicks gentlemen. Beat that!!!) The poison pill was OCLF, then Voodoo, BTW.
Oh yeah, PS... If anyone needs their phone converted into a shiny black paperweight, get in touch. I'm among the best out there.
So I'm in some dire need of help. I have a rooted fascinate (with voodoo) for several months now. I was trying to upgrade to the new EB01 and was getting the no memory for storage error due to me not disabling voodoo. (whoops 1) In an attempt to restore my phone back again I found a fix to return back to a stock kernal, etc. I however was jumping around on way too many threads and flashed my phone with a vibrant rom/kernal. I am now running 2.2 Vibrant on a Fascinate. Here's the real problem, now when I hook my phone up to my computer through usb the phone shuts off. I can't get the phone into download mode to flash again wtih odin or recovery mode. It appears that the volume buttons aren't recognized on my fascinate hardware and vibrant rom. If there's ANY help anyone could offer me that would be great.
Not having a download mode or usb storage that I can fix it with adb/odin is really a huge problem obviously. Thanks!
Sounds like that phone is pretty much done, your best bet probably is to take it back to verizon. If you have a warranty it will cover that, just play it off as you didn't do anything to it.
I really don't understand how people can be so careless and inattentive while flashing, especially after already screwing up once.
thefunkbot said:
Sounds like that phone is pretty much done, your best bet probably is to take it back to verizon. If you have a warranty it will cover that, just play it off as you didn't do anything to it.
I really don't understand how people can be so careless and inattentive while flashing, especially after already screwing up once.
Click to expand...
Click to collapse
Gonna have to be more creative then that...they will pop a battery in and check. And they will know if they can get it that far...
thefunkbot said:
Sounds like that phone is pretty much done, your best bet probably is to take it back to verizon. If you have a warranty it will cover that, just play it off as you didn't do anything to it.
I really don't understand how people can be so careless and inattentive while flashing, especially after already screwing up once.
Click to expand...
Click to collapse
Well not removing the voodoo is something that tons of people have done according to all the posts I've seen people writing. Mistakes happen, it's not like I haven't rooted/flashed before I've done it a dozen times this boo boo just happened to be the mother of them all. And yeah I have a feeling that if I walk into a verizon store I'm SoL due to the VIBRANT that plasters across the screen upon booting. Just wondering if there's a work around for the usb portion of it that maybe someone can pull out?
So you have no adb and you are having a hard time getting into download mode.
Do you have:
- Recovery?
- cwr?
- is the phone useable at all? Can you get wifi, write or at least read your sd card, etc.
Your only hope in the end is when you get odin working eventually.
You _might_ be able to clean up with the mbr patch from this thread, provided you can install and run terminal emulator (as a substitute for adb shell) on the phone itself... but that is really iffy.
http://forum.xda-developers.com/showthread.php?t=804784
Swyped w/ XDA App. When in doubt, mumble.
The phone turns on perfectly fine, goes into normal vibrant 2.2 mode so wi-fi is a go. I downloaded rom manager and can get it to go to a stock recovery however I can't use the up/down volume keys to navigate through the recovery, I can only reboot it again from there.
I agree that installing a voodoo incompatible kernel is a common enough and human mistake. As far as flashing full blown Vibrant, well I wish you didn't do that.
Just to be clear, in your case, you would want to get your phone into download mode ANY way you can. If it crashes when you plug it in, try to get download mode running _before_ you plug it into a computer.
I wouldn't give up just yet, there is still hope that there is something left of download and recovery modes on your phone.
There is a USB rig that you can read about how to build (fairly simple) that will force download noise by plugging it in.
It is remotely possible that you can flash something via kits to get yourself back on track, but that may only make matters worse.
Is there perhaps an app that launches download mode? (never heard of one)
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I agree that installing a voodoo incompatible kernel is a common enough and human mistake. As far as flashing full blown Vibrant, well I wish you didn't do that.
Click to expand...
Click to collapse
Ditto. Also I can get access to the sd card however the usb situation comes into play again, when I plug it in I hear the connection bing through win7 but then the phone shuts off immediately. Phone is in usb debugging mode and allowing all connections etc.
I looked up a few ways to get into d/l mode through vibrant work arounds but none of them appear to work either, again I fear that it's the volume up/down incompatibility with the fascinate that's holding me back. Looking bleak thanks for the suggestions
rapture0707 said:
The phone turns on perfectly fine, goes into normal vibrant 2.2 mode so wi-fi is a go. I downloaded rom manager and can get it to go to a stock recovery however I can't use the up/down volume keys to navigate through the recovery, I can only reboot it again from there.
Click to expand...
Click to collapse
That is good news! If you can somehow get CWR to run, you don't need volume buttons to navigate CW Recovery, it'll launch from rom manager. If you can do that, you can get to download mode.
It may still take some tricky fingers too get the volume buttons working again, but at least you can work on getting rid of the other carrier's badging.
Swyped w/ XDA App. When in doubt, mumble.
IF there IS any hope for you (which i doubt), i advise you get on the fascinate irc and seek help there.
apparently I meant JIG, not rig:
http://forum.xda-developers.com/showthread.php?t=819551
This is still your best avenue.
===========
(irregardless of whether usb is plugged in)
From regular recovery (blue) to download:
Press home button (to reboot) while hitting volume down
-- I don't think this will work for you since your volume buttons don't seem to work regardless of mode --
So, battery pull/hold vol down while plugging into usb won't get to dl mode for odin?
good day.
chopper the dog said:
So, battery pull/hold vol down while plugging into usb won't get to dl mode for odin?
good day.
Click to expand...
Click to collapse
Pretty much, I'm boned. Thanks for the suggestions though. My own darn fault
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Maybe change the title of your thread... Your phone was bricked because you installed the Rom...
How r people getting the FFC to work with stock camera
wanabdev said:
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Click to expand...
Click to collapse
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
2. pulling the battery isnt as dangerous as everyone says it is. its only dangerous if you pull it while trying to flash the stock PD15IMG to return to stock, or during the phones booting process where its loading everything up. Ive pulled my battery plenty of times, but never in those situations.
Maybe hope
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
macblaxter said:
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
Click to expand...
Click to collapse
DING DING DING we have ourselves a winner.
[OP] are you able to get into the bootloader or recovery?
I remember when I first started rooting my phone it would be titles like this that would scare me away form certain roms. Which is a good and bad thing. Although I would generalize the title a little. Like " dam i messed up installing a sense rom" this way it's a little more inviting to open minded people that want to help and less offending to people that put in time for tutorials and development
Sent using XDA App
aznprodgy said:
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
Click to expand...
Click to collapse
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Jack_R1 said:
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Click to expand...
Click to collapse
well damn bro, didnt think it was that serious...
Hey Jack_R1 thanks for the input. I always enjoy getting a snapshot of information to clarify how things work.
wanabdev do you know if you're able to get into the boot loader to get access to fastboot? You really may be able to save your phone if you're still able to do this.
Wi-Fi Calling using Darkside Runny 2.2
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Chicago T said:
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Click to expand...
Click to collapse
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Wi-Fi Calling using Darkside Runny 2.2
glacier1122 said:
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Click to expand...
Click to collapse
Right, soooooo annoying. There's gotta be a fix out there? I like this ROM the best, it has all the little tweaks that make me happy!
Anyone have any ideas?
Flash the newest version.
http://forum.xda-developers.com/showthread.php?t=1283682
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?
neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.
neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.
I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?
You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
It is the touchscreen controller software.
pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again
i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!
My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.
bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.
Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10
Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW
sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:
sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.
Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.
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