Related
Hi there XDA community,
I would like to know if there is an up-to-day tutorial that has working file links? I would like to upgrade, root, and unlock my Xoom. I just bought a Motorola Xoom from 1saleaday.com the Model is an MZ601 and says "approved by IDA for use in Singapore" it is currently just as is and is not unlocked or rooted. I would like to get it upgraded, unlocked, and rooted so I can use it for what I got it for. It has WiFi and Data service that supports WCDMA 850/900/1900/2100, GSM 850/900/1800/1900, ATO_ITEM: AP1520AD3X3. It is currently running on Android Honeycomb 3.0.1, build number H.6.1-38-9. If you any ideas, files, links, tutorials (up-to-day), or can help, that would be great!
Thanks InfiniteImmortal.
P.S.
Here are the configurations;
Model Number: MZ601
Android version: 3.0.1
Firmware: GAS_ASIA_USAEVRSTURTIRD_P016
Baseband version: N_014.83.28P
Baseband configuration: UCAEVEUB1B8EU034.0R
Kernel: 2.6.36.3 [email protected] #1
Build Number: H.6.1-38-9
More specs will be provided if they are needs, thanks again II!
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Response to purity0flove
purity0flove said:
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Click to expand...
Click to collapse
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Response to llama-power
llama-power said:
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
Click to expand...
Click to collapse
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
InfiniteImmortal said:
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Click to expand...
Click to collapse
yes I ordered one from 1saleaday.com on E-bay .. this seller buy also on E-bay ... new not Refurbished ! and ship with UPS but didn't now still didn't ship and wait for him !
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models?
Click to expand...
Click to collapse
Yes, the one post I have marked with "(a post by me)" is exactly how I rooted my xoom and that is a german MZ601. And it works, no brick
InfiniteImmortal said:
I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore.
Click to expand...
Click to collapse
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
To Clarify this: the Unlock should impose absolutely no risk at all as it is a feature implemented by motorola. The recovery, even if it didn't work, wouldn't lead to a brick. And the universal xoom root should not do any magic either, it should only add two files to the filesystem (su and Superuser.apk) and remove those files that would make your new shiny recovery go byebye once booted
Ty my knowledge, only the "flashing a custom rom" part is a source of bricking. And that can easily be avoided by flashing a MZ601-rom instead of something else
That said, nobody can guarantee you that this is completely safe. There is a thread right next door with a poor guy whose xoom bricked itself overnight. That was a wifi-xoom, and so far no one knows why that happened. We're still working on a solution, though
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
Click to expand...
Click to collapse
tell me what way you chioce and made and the result .. cuz I will root my item when I recive
---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
purity0flove said:
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
Click to expand...
Click to collapse
yes, you will be able to go back to the original rom and lock your bootloader again. If you do that, you will be able to get ota updates (if you really want to do so, usually custom roms are ahead of the ota-updates)
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Response to llama-power
llama-power said:
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Click to expand...
Click to collapse
I'm now intrigued, I to would like to know how to do this. I'm all for safety measures when it comes to doing things that could damage my stuff.
II
Response to llama-power
llama-power said:
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
Click to expand...
Click to collapse
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
In the first one I found out about it in the comments sections. I read everything on the pages.
II
Custom ROM Files
Hey llama-power,
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files? I know I.C.S. is the latest one, but I'm happy with an old one if it is stable. Or if you have a custom ROM for the Xoom that would be great. I have a Samsung Captivate generation 1 that I use Firefly or Cognition on, along with the original stock ROM as backup just in case. Any links or files would be very cool!
II
Suggested Thread
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom, but thanks for your suggestion. I'll try the other ones you put up, so far I have read every page on every linked thread I've come across. Lots and lots of helpful info on those as well as your pages. But if you can respond to my three earlier posts that would be helpful too. Starting to get information overload, haha.
II
Response to llama-power
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
A few more question, yes I know MORE questions! haha. Where is the backup I make stored at? I would like to put it in my backups folder for the Xoom under its drive in my computer. Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions? Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
llama-power You ROCK!
Time for me to get some sleep! Been reading and doing Xoom stuff for hours now. I'll be on later to night to read your posts!
Sincerely, InfiniteImmortal
InfiniteImmortal said:
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
Click to expand...
Click to collapse
Wow, wasn't aware of that. But these methods are really old. The method I mentioned is the universial root-method by solarnz which is supposed to work on every 'classic' xoom (despite the family edition with its locked bootloader)
InfiniteImmortal said:
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files?
Click to expand...
Click to collapse
I am using the team eos nightlies. Works really nicely except deep-sleep isn't working for me while wifi is enabled. Don't know if that is a rom-issue though, might be some app I use. Anyways, it's not really a problem to me, battery life is still more than sufficient.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
InfiniteImmortal said:
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom,
Click to expand...
Click to collapse
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
InfiniteImmortal said:
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
Click to expand...
Click to collapse
thanks, glad to read that
InfiniteImmortal said:
Where is the backup I make stored at?
Click to expand...
Click to collapse
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
InfiniteImmortal said:
I would like to put it in my backups folder for the Xoom under its drive in my computer.
Click to expand...
Click to collapse
great idea
InfiniteImmortal said:
Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions?
Click to expand...
Click to collapse
that is weird. What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far. A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
InfiniteImmortal said:
Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
Click to expand...
Click to collapse
yeah, once you flash your new rom, you should be able to access that sd-card. As stated before, you are just rooted, that gives you the power to change things but if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
InfiniteImmortal said:
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
Click to expand...
Click to collapse
see above, use team eos nightlies
Response to llama-power
llama-power said:
I am using the team eos nightlies.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
Click to expand...
Click to collapse
Okay I'll look into this one since I know you said it works for you.
llama-power said:
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
Click to expand...
Click to collapse
I know you have already seen the other thread that I posted to, and about how I know it didn't work. You commented on the thread with your own post, thanks for backing me up.
llama-power said:
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
great idea
Click to expand...
Click to collapse
Thanks, I did the same thing on my Samsung Captivate and since my mother has the same phone I made it so it could be used on ether one, less file management for me. Haha
llama-power said:
What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far.
Click to expand...
Click to collapse
You are correct on this, nothing has changed from before except becoming rooted and unlocked. I was hoping that just maybe a full system wipe might fix the connection issue I was having. I was being over optimistic!
llama-power said:
A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
Click to expand...
Click to collapse
Yes airplane mode is off and Mobile data service is enabled. I have tried it with WiFi both on and off, before and after rooting and unlocking but still nothing. As for the AT&T-APN being setup correctly, I used the exact same settings that are being used in my phone with nothing different; but still to no prevail. Do you know if there is a settings list or configuration out somewhere for the APN?
llama-power said:
yeah, once you flash your new rom, you should be able to access that sd-card... if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
Click to expand...
Click to collapse
Yeah I kinda guessed at that one, I remembered reading about the Honeycomb 3.1.0 update giving users the ability to use the micro SD cards today. That was before I read your post. lol You might know about this, Do you know where the repository of updates are located for the Motorola Xoom 'classic' model? I was thinking it would be a good idea to have all of them, if I ever wanted to use my warranty it would be good to have the latest stock ROM on it! It's better to be safe then up an icy creek in the Alps with a swim suit on!
II
InfiniteImmortal said:
Okay I'll look into this one since I know you said it works for you.
Do you know if there is a settings list or configuration out somewhere for the APN?
Click to expand...
Click to collapse
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well. So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Best regards, InternetImmortal
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well.
Click to expand...
Click to collapse
glad you like it
InfiniteImmortal said:
So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Click to expand...
Click to collapse
well, there are a couple of sources for a stock rom. For one, your sd-card should contain one (I restored my backup yesterday and yes, it even reset the recovery to stock)...
Also, motorola offers some filesystem images at http://developer.motorola.com/products/software/, but you'll need to register with them to get to the download (should be free, though)
Finally, it might be desirable to have some .sbf-file for your xoom. Those can be flashed using a software called rsd lite, even when you aren't able to enter your recovery system. Doesn't always work, so it's not more than a Hail Mary move... However, Motorola does a lot to keep these files from floating around the web, so I won't be able to provide you with a link.
As always thanks for the keen insight. Just came across a few threads that perked my interest. Have you ever tried to get working SMS text messaging and voice calling on the Xoom? Since I'm using the SIM from my phone to do the data I was hoping there might be a way. I haven't done a lot of reading on this yet but you seem to know everything.
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Have you ever tried to get working SMS text messaging and voice calling on the Xoom?
Click to expand...
Click to collapse
nope. The sim inside my xoom is on the same contract as the sim in my phone and I had to pick one that would receive texts. Naturally, since I always carry my phone, that's where the texts go, so the xoom wouldn't ever receive a text ever anyways. Voice calling is currently not possible on the xoom. So the only upside of that would be that I could send texts using the xoom, but that isn't so much better than texting on my Desire HD. Plus, that would tear apart the messaging threads between my phone and the xoom.
However, there's a thread in the xoom development section where flashable zip-files are published for every eos nightly, you should be able to just flash that over your rom and thus enable texting.
Actually, I might try that some time, but right now I should really learn for that exam on friday:-/
I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks
newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.
I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?
excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.
I've been searching for solutions to this problem for weeks now with no luck.
Many users have complained about this issue. I'm quoting what the problem is exactly below.
https://forums.motorola.com/posts/61818a4ef4
Ever since I use Gingerbread and Google Maps (5.+), the compass function in Google Maps is totally erratic and wrong, basically useless.
Here is what I noticed when using compass dependent apps:
If it is a based magnetic compass only, it works.
if it is a GPS based compass only, it works, although you must be moving over a certain speed for the GPS to detect directions.
If it is a acceleration (Gyro) based compass it is all screwed up.
I tested all the above scenarios with many GPS, compass, and map utilities and I can confirm that that is teh case.
here is an simple way you can test this:
use Google Maps (not Nav) to display a map while you are driving. you will notice that while the car is in motion the map orientation is correct and tracks you direction in relations to North. Once you stop for more then a few seconds, the GPS compass can not detect motion and you will see the orientation of the map (or the little blue triangle) shifts to a new direction sometime as wrong as 180 degrees!
I tried calibration, resting the A-GPS data, factory reset, you name it.. Nothing fixes this problem. I don't think it is a hardware problem because I had the same issue with an Atrix 4G..
From the research I did on line there are evidence that this effect all Motorola gingerbread phone, and possibly other makes as well.
This is not a new problem, and all the solutions I have found on line do not fix this problem.
Click to expand...
Click to collapse
I've tried all the calibration tips, but it just doesnt work because it isnt a problem with the compass. On dialing #*0*# I'm able to check if the compass is working fine on its own, and yes, its properly calibrated. The problem is with Google Maps and the Android OS.
I've even found a possible solution here:
http://androidforums.com/incredible-support-troubleshooting/79713-compass-calibration-problem.html
I worked out a fix that does not require a factory reset! It does require root and the Android SDK. Connect the phone to your computer using usb and run 'adb shell' once connected run the following commands:
su
cd /data/misc
rm AK8973Prms.txt
rm AK8973Prms.txt.tmp
reboot
This removes the saved calibration data. On reboot it will regenerate these files. In my research I found that on other phones the calibration data may be stored in a file called akmd_set.txt.
I hope this helps anyone else with this issue.
Click to expand...
Click to collapse
and here
http://forum.xda-developers.com/showthread.php?t=957143
I'm quite positive that these solutions would work but they require root access. I would like to do a temporary root (root and then unroot) so that my warranty doesnt get voided. I've tried using SuperOneClick but it was unsuccessful (checked through SU checker). So is there any other way in which this could be done or solved?
Its running 2.3.6.
pudup said:
ROOT
Sent from my GT-I9103 using XDA
Click to expand...
Click to collapse
Please read my entire post before posting.
Hi
I have exactly that issue, always when you need your navigator walking. It happens with google maps navigator and with Copilot Live too.Just when walking, not driving. So you need to imagine where are you walking.
I asked in a Spanish forum (htcmania.com) but nobody talked about. So I thank it were from my rom (last Austrian with last CSC from the last Germany), our perhaps from the kernel (Ardatdat 1.8.1 to 1.8.3).
Sent from an GT-I9103 with Tapatalk 2
pudup said:
I mean you can root without doing damage to your warranty.
Sent from my GT-I9103 using XDA
Click to expand...
Click to collapse
How? SuperOneClick has an Unroot option but it isnt rooting my phone. Can this (rooting and unrooting) be done with other rooting methods too?
112358z said:
How? SuperOneClick has an Unroot option but it isnt rooting my phone. Can this (rooting and unrooting) be done with other rooting methods too?
Click to expand...
Click to collapse
Yes, you can root by flashing a rooted stock kernel which can be found in our forum easily and you can unroot by flashing the stock kernel after you're done.
I think SuperOneClick does not support galaxy r
From my galaxy R
vbz89 said:
Yes, you can root by flashing a rooted stock kernel which can be found in our forum easily and you can unroot by flashing the stock kernel after you're done.
I think SuperOneClick does not support galaxy r
From my galaxy R
Click to expand...
Click to collapse
Would flashing the stock kernel require me to restore a backup or would my phone data be intact? I'm asking this because I did the restore once when I did a device update and it was a messy procedure, it did not happen successfully. Sorry for being such a noob.
112358z said:
Would flashing the stock kernel require me to restore a backup or would my phone data be intact? I'm asking this because I did the restore once when I did a device update and it was a messy procedure, it did not happen successfully. Sorry for being such a noob.
Click to expand...
Click to collapse
Ideally a kernel only affects the boot image. All other images like System, Data etc remain intact....so there's no question of you phone data getting messed.
Thanks a tonne, all of you!
I wish something could be done about this bug. Its been there since Android 2.3.
Happy to help! Just root your phone! Try if the solutions above do solve the bug and report back. Who knows you might squash an imp. bug
can any1 help abt this ???
Actually, navigation/directions doent work on my SGR, when i select get directions, it will show route, but the MY POSITION icon doent move at all...
where as in my friend's Sony Neo V (2.3.5) it works awesome, what is the problem in my phone
So I've searched and haven't found anything similar to what I'm experiencing.
Verizon M8, S-OFF, flash more than once a day sometimes. I recently had the 4G LTE issue that required I return back to stock recovery to fix nv partition through factory reset.
Since then, I've noticed that my bluetooth connects just fine to my uConnect for audio, but not phone functionality. It doesn't seem to be an issue with my ROM because I've tried multiple and experience the same issue, and a friends iPhone paired without issue.
Is it possible theres another partition that I screwed up?
Please let me know if I left out any vital information..
Thanks guys!
Have you tried reflashing your firmware?
cntryby429 said:
Have you tried reflashing your firmware?
Click to expand...
Click to collapse
I did, through the fastboot process and hboot as well.
How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.
cntryby429 said:
How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.
Click to expand...
Click to collapse
I'm going to try are0s again but through the fastboot method. I'll post back here soon.
Thanks
I also understand it's recommended to flash it twice in fastboot.
cntryby429 said:
I also understand it's recommended to flash it twice in fastboot.
Click to expand...
Click to collapse
Fixed! I'm not sure if reflashing the aero firmware fixed it or deleting the audio device on my head unit before pairing again did. This could have just been a major brain fart.
Glad you're back on track either way.
Hey guys,
So I flashed this rom two weeks back http://forum.xda-developers.com/oneplus-one/development/rom-paranoidandroid-5-0-alpha1-t2956478
after running cm12s nightlies for a while. The capacitive keys stopped working after I flashed this rom with the PA gapps and they still don't work after trying multiple roms + relocking unlocking bootloader and flashing 44s. Kinda frustrated cause I don't know what I can do. Any ideas?
Thanks
How did you flash 44S?
Transmitted via Bacon
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Sanjitha.d said:
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Click to expand...
Click to collapse
By recovery tool you mean flashing with fastboot, right?
Transmitted via Bacon
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Sanjitha.d said:
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Click to expand...
Click to collapse
That's what I meant, that's flashing with fastboot. The only thing I can think of doing is completely wiping your phone including user data (back up important files first) and flashing the stock images again, but manually this time. You can find a download and instructions in section 8 of my guide thread.
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Alright, I've also tried manually flashing the stuff myself but I'll do it according to your guide to see if it works. You don't think it could be anything software/firmware related after that yeah? I remember there was a guy who said that he had to do a full wipe to make the cap keys to work on the initial pa thread but actually no idea on how this screwed up lel
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Sanjitha.d said:
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Click to expand...
Click to collapse
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
timmaaa said:
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Sanjitha.d said:
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Click to expand...
Click to collapse
Can't really suggest one because I don't use them, but you'll find them all listed in my index thread here:
http://forum.xda-developers.com/showthread.php?t=2843675
I can't think of anything else on the software/firmware side of things, everything has been wiped and reflashed.
Transmitted via Bacon
I have a similar issue. The softkeys stopped working right after i unlocked the bootloader. They light up but do not respond. can anything be done? I unlocked the bootloader via adb.