I spent some time on live-chat with oneplus support to be sure how to downgrade to marshmallow. In short they mentioned that you need to have a special remote session with oneplus support to make that happen. Here is a copy of my chat with them. I wanted to share that with you all...
2:49:50 PM - undefined said : Please wait one moment...
2:49:53 PM - Erik said : hi
2:49:56 PM - Rosevil said : Hello Erik. My name is Rosevil how can I help you?
2:50:04 PM - Rosevil said : Thank you for taking time contacting OnePlus Customer Support. I am happy to help.
2:50:11 PM - Rosevil said : Hello Erik.
2:50:21 PM - Erik said : hi
2:50:37 PM - Erik said : i just downloded the latest community buid
2:50:40 PM - Erik said : beta 8
2:50:45 PM - Erik said : excited to try it out
2:51:09 PM - Erik said : in the post where oneplus posted the build it was stated the following....
2:51:43 PM - Erik said : After upgrading to Android N, you will not be able to directly downgrade back to M builds. Our customer service team has a special build of Android M that will allow you to downgrade, but this will format your device. If you'd like to flash back to M, please contact our CS support here: [https://oneplus.net/support] Please keep in mind that this is beta software. This build will not be as stable as our official OTA releases. Given that this is a shift to a brand new version of Android, there may be more bugs in this build than previous Open Beta builds.
2:52:02 PM - Erik said : can you provide me with that special build please?
2:53:19 PM - Erik said : are you there?
2:53:55 PM - Rosevil said : Thank you for the information Erik. If you want to downgrade your OS from Nougat to Marshmallow, I will endorse you to our Level 2 specialist and book you a schedule for a remote session, is it okay with you?
2:54:15 PM - Erik said : a remote session? what does that mean?
2:55:12 PM - Rosevil said : Remote session is our level 2 specialist will help you access your phone and will assist you to downgrade your OS to marshmallow.
2:55:41 PM - Erik said : i was hoping to have the build in hand and then perform that task myself
2:56:11 PM - Rosevil said : I understand, what we can offer you is the downloads available in our website.
2:56:19 PM - Rosevil said : http://downloads.oneplus.net/
2:56:21 PM - Erik said : i see those
2:56:25 PM - Rosevil said : Please try to check this.
2:56:27 PM - Rosevil said : I see.
2:56:43 PM - Erik said : but I cannot just simply download the latest stable to downgrade
2:56:45 PM - Erik said : can I?
2:57:14 PM - Rosevil said : I am afradi that we are not able to provide any instruction or steps for you to do it by yourself since our Level 2 specialist as well is not allowed to do so.
2:57:34 PM - Rosevil said : As adviced, offer you our download files in the website.
2:57:43 PM - Erik said : lol
2:57:51 PM - Erik said : here is what I am asking
2:59:05 PM - Erik said : i understand how to load community builds and then downgrade back to stable builds via adb sideload. I have done it many times. The issue with this current new beta 8 nougat community build is that it was posted that I need a special build of stable OOS in order to downgrade back to stable from beta 8.
2:59:27 PM - Erik said : from the post from oneplus i was told that i can get that special build from customer support
3:00:34 PM - Rosevil said : I am currently contactin one of our Level 2 specialist here, pleasew bear with me.
3:00:41 PM - Erik said : ok
3:06:01 PM - Rosevil said : Hi Erik. I already talked to one of our Level 2 specialist, as I gathered information from him. I understand that you know how to flash your OS knows a lot on hot to do it by yourself, but we or only our level 2 specialist here has the tool to downgrade to you marshmallow version via remote session with them.
3:06:27 PM - Rosevil said : how*
3:06:45 PM - Erik said : really?
3:06:51 PM - Rosevil said : Yes.
3:06:53 PM - Erik said : why is only a remote session possible for downgrading
3:07:18 PM - Rosevil said : Because our level 2 specialist has thier tools here to do it.
3:07:29 PM - Rosevil said : This is the information I gathered from them.
3:07:39 PM - Erik said : can he/she provide us with the tools so that we can do it ourselves?
3:07:55 PM - Erik said : does it involve using sdk?
3:08:06 PM - Rosevil said : I am sorry but they are not allowed to proivde it to you as this is an internal files from us.
3:08:37 PM - Rosevil said : As much as they want to provide it but this is an intermal property/files.
3:08:42 PM - Rosevil said : Hope you understand.
3:10:07 PM - Erik said : Pelase update any postings of the community build on the oneplus community making tha clear. Most people will use beta 8 thinking they just need to get a special build from you. if they know they need a special "remote session" to downgrade that will deter people. They should know that information.
3:10:36 PM - Rosevil said : I will send your suggestion Erik.
3:11:00 PM - Rosevil said : I do apologize and thank you for understanding.
3:11:37 PM - Erik said : thank you
3:11:48 PM - Rosevil said : You're very much welcome. It's my pleasure to assist you.
3:11:54 PM - Rosevil said : Is there anything else that I can assist you with?
3:12:01 PM - Erik said : no, thanks
3:12:12 PM - Rosevil said : Have a wonderful day. Take care and be well.
3:12:16 PM - Rosevil said : Thank your for contacting OnePlus customer support , have a wonderful day. “An automatic survey will pop-up on your window when you click the "Close" button on the lower left corner of the chat screen. It is just a 1 question survey that will let you rate me and the service I have provided to you today. We appreciate your feedback. Thank you and Never Settle.
What..................
The fact that they referred you to customer support in the post implied that you would need special build to downgrade, it probably has something to do with the file system that may change for some users based on what they did to upgrade to 8
i think its enough to format partitions to ext4 and flash an old firmware ?
Yeah its probably the file system change to f2fs
ReNeH99 said:
i think its enough to format partitions to ext4 and flash an old firmware
Click to expand...
Click to collapse
it would be good for someone to do that and then post instructions here on XDA for others to follow.
That wipe only system and data or internal storage too?
Pretty sure u can do it ur self with TWRP, but they can't recommend that since it's 3rd party, u can't through stock recovery
I don't think "remote session" literally means they have to remote into your phone to do it. It probably means just a WebEx or something to show you how to do it. Lame thread.
Tikerz said:
I don't think "remote session" literally means they have to remote into your phone to do it. It probably means just a WebEx or something to show you how to do it. Lame thread.
Click to expand...
Click to collapse
i just spoke to someone on op forums who downgraded and they actually do it, they (the remote support) extract the files with a spicific key for each download ( i tested by using the key he sneakily saved from the session and it didn't work on my files), and they start the operation...
you'll download the rom (it was sent to me by email) 1.05 gigs, and a adb installer + certs!!! (also this is an encrypted rar)
and the usb drivers
they send you an email with all 3 links, and the support (normal one not the remote support) gives you a ticket number, with that ticket the remote support will continue working on your specific device and will have the specific key for the files you downloaded... soo
this pretty much silly.
i also don't think it's only f2fs issue, (, at 1st i thought it was only that, but looking inside the certs encrypted rar it does contain some sort of keys in a folder called testcertificate.
i also had a similar conversation with the support ( i have screens of it ) and what he said is basically what i already guessed.
that said, i think it's beatable, at least the f2fs part, and if that's the case, the original N package can be repackaged so it doesn't apply anything other than formating to f2fs...etc
theduke7 said:
i just spoke to someone on op forums who downgraded and they actually do it, they (the remote support) extract the files with a spicific key for each download ( i tested by using the key he sneakily saved from the session and it didn't work on my files), and they start the operation...
you'll download the rom (it was sent to me by email) 1.05 gigs, and a adb installer + certs!!! (also this is an encrypted rar)
and the usb drivers
they send you an email with all 3 links, and the support (normal one not the remote support) gives you a ticket number, with that ticket the remote support will continue working on your specific device and will have the specific key for the files you downloaded... soo
this pretty much silly.
i also don't think it's only f2fs issue, (, at 1st i thought it was only that, but looking inside the certs encrypted rar it does contain some sort of keys in a folder called testcertificate.
i also had a similar conversation with the support ( i have screens of it ) and what he said is basically what i already guessed.
that said, i think it's beatable, at least the f2fs part, and if that's the case, the original N package can be repackaged so it doesn't apply anything other than formating to f2fs...etc
Click to expand...
Click to collapse
That's crazy.
Tikerz said:
That's crazy.
Click to expand...
Click to collapse
yeah, the rom that we're willingly testing for them is not encrypted and doesn't require any "special" anything, so even the most noobs will do it (which did happen) , but reverting back to the device normal state requires this much hassle, this to be honest a **** move by OnePlus, they're locking people (most noob users who did upgrade) out of stable release. (actually it's even a hassle for the experienced user)
that's why i decided not to upgrade the second i read the 3rd point on the release post....
theduke7 said:
yeah, the rom that we're willingly testing for them is not encrypted and doesn't require any "special" anything, so even the most noobs will do it (which did happen) , but reverting back to the device normal state requires this much hassle, this to be honest a **** move by OnePlus, they're locking people (most noob users who did upgrade) out of stable release. (actually it's even a hassle for the experienced user)
that's why i decided not to upgrade the second i read the 3rd point on the release post....
Click to expand...
Click to collapse
I have faith XDA will find a way!
theduke7 said:
i just spoke to someone on op forums who downgraded and they actually do it, they (the remote support) extract the files with a spicific key for each download ( i tested by using the key he sneakily saved from the session and it didn't work on my files), and they start the operation...
you'll download the rom (it was sent to me by email) 1.05 gigs, and a adb installer + certs!!! (also this is an encrypted rar)
and the usb drivers
they send you an email with all 3 links, and the support (normal one not the remote support) gives you a ticket number, with that ticket the remote support will continue working on your specific device and will have the specific key for the files you downloaded... soo
this pretty much silly.
i also don't think it's only f2fs issue, (, at 1st i thought it was only that, but looking inside the certs encrypted rar it does contain some sort of keys in a folder called testcertificate.
i also had a similar conversation with the support ( i have screens of it ) and what he said is basically what i already guessed.
that said, i think it's beatable, at least the f2fs part, and if that's the case, the original N package can be repackaged so it doesn't apply anything other than formating to f2fs...etc
Click to expand...
Click to collapse
That pretty much is in detail what I had assumed was a very involved process with remote connection from OnePlus Notre to revert back. I am sticking to oxygen 3.2 .8 for now
But you can still flash other android N ROMs after updating to beta 8, right?
Lets wait for a freedomos update, i'm sure these problems are gone then
Vidicgapi said:
But you can still flash other android N ROMs after updating to beta 8, right?
Click to expand...
Click to collapse
i don't see why not, the issue i think is returning to official stable MM, and i wonder what will happen also after official stable N when everyone is on it, i think the same process will be there but without remote assistance, it's strange to me why would OP wouldn't want people going back and forth between their OS!
personally i'm sticking to my Unofficial CM 13, if i want N , there's plenty of N roms, with enough stability.
Vidicgapi said:
But you can still flash other android N ROMs after updating to beta 8, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=69871093&postcount=579
"All you need is to wipe flash the old 3.2.6 Firmware and good to go. check the respective rom thread as some roms need 3.5.5 Firmware.
Cant you just use the full unbrick tool to go back to 3.1.2 and stary from scratch?
chasemyass said:
http://forum.xda-developers.com/showpost.php?p=69871093&postcount=579
"All you need is to wipe flash the old 3.2.6 Firmware and good to go. check the respective rom thread as some roms need 3.5.5 Firmware.
Click to expand...
Click to collapse
I saw a guy on OnePlus forums say to do this:
To revert back to stock, you need to flash the latest stable build (not the community one! You can get it from the downloads section of the support page). Once you download it, download the stock recovery from there as well.
Once you sideload the ROM, you should be able to successfully flash the stock recovery via fastboot (fastboot flash recovery recovery.img)
That's it! Beware though, that if you try to lock the bootloader, you might lose the recovery again (happened to me twice).
Click to expand...
Click to collapse
Related
Hi all,
Noob here. I like what you guys are doing here, it is always great to increase the potential of a device and improve it from it's original state. Unfortunately most of this is way beyond the scope of my skill!! Thank you for taking the time to read this.
I have searched extensively before posting here and cannot find a solution, it is however a fairly simple problem.
Firstly I have an unmoded GT-I9001 running Gingerbread 2.3.5 stock.
The kernel version is 2.6.35.7-perf [email protected] #1
I was previously having a problem with the phone caught in a reset loop.
I tried to follow [URL="http://forum.xda-developers.com/showthread.php?t=1139050"]this[/URL] guide. (Flash/Install/Update to Gingerbread 2.3.4 to I9000: Detailed guide for n00bs) to install XWJVZ/OXXJV9/XXJVT found here.
I followed the guide and put the phone into download mode, it was detected when connected and I started the process. The files were all verified and then it displayed "Setupconnection". It hung here, I left for about 45mins before I was forced to disconnect and rebooted the handset. I tried this twice with the same result.
Finally I managed to fix the problem by preforming a factory reset and removing one of the stock programs (a stupid Irish language translation tool) before it got to update.
I don't really want to heavily modify my phone at the moment. (Mainly because presently I am unaware of the potential, new to this phone and just want to establish basic usage and get used to Android in general as this is my first on that platform. However, if somebody can recommend a ROM or Firmware suitable to my needs that would increase my user experience I'm all for it!)
All that I really need at the moment is to increase the volume of the ringer/alarm. I can barely hear the notifications when on a table on front of me (It would also be good to have the screen light on notification) and there is no chance in my pocket. Also need to unrestrict the media volume whilst using the headset as it's pathetic at the moment.
If I could also unlock my phone so I can use any SIM it would be a bonus, but not necessary. And as before, if anybody can recommend something that would provide some other functionality whilst remaining as close to stock as possible, that would be great.
So if somebody can point me to a ROM/Firmware that would provide this basic improvement in functionality and show me which guide would be suitable for installing it, I would be most grateful.
I have experience flashing and modding a Nokia-N97 a while ago, so I am not incapable or technologically impaired! I just want to make sure to get this done the right way.
Many thanks for taking the time to read, and for any assistance you can offer me,
Bren
Try my thread
http://forum.xda-developers.com/showthread.php?t=1142499
malcho said:
Try my thread
http://forum.xda-developers.com/showthread.php?t=1142499
Click to expand...
Click to collapse
Cheers mate,
Just reading through it now.
And thanks again for the prompt reply!!
Just another thread is worth reading original posted by AMDPOWERFIST :
• Installing a new ROM
• Installing a new Kernel
• Achieving the best battery life as possible
http://forum.xda-developers.com/showthread.php?t=1351663&highlight=battery
Hope this helps
Will all of those perform the volume enhancement that I need? Is there any chance you can recommend one to keep it as close to stock while providing this functionality. At the moment my phone might as well have no notification feature, I need to keep checking it. And the media playback is pretty dismal too.
At the moment these are the only features I really need to change.
I have only had this phone 4 days and have had problems so far.
When I try "Boot into CWM (vol up + menu + power)"
I get an error? message as follows;
"RAMDUMP MODE
Cause: Force Upload"
Anybody know what this means? :/
Thank you for you help so far...
I found this post on other forum base on XXJVT at I9000 ( International Version ) and also included with Voodoo Sound Control that lets you increase volume by up to 300%.
http://androidadvices.com/overclock...g-galaxy-gt-i9000-semaphore-kernel-xxjvt-235/
Hope this helps
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
I found this post on other forum base on XXJVT at I9000 ( International Version ) and also included with Voodoo Sound Control that lets you increase volume by up to 300%.
http://androidadvices.com/overclock...g-galaxy-gt-i9000-semaphore-kernel-xxjvt-235/
Hope this helps
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
bren.ryan said:
I have only had this phone 4 days and have had problems so far.
When I try "Boot into CWM (vol up + menu + power)"
I get an error? message as follows;
"RAMDUMP MODE
Cause: Force Upload"
Anybody know what this means? :/
Thank you for you help so far...
Click to expand...
Click to collapse
You should try to search again before asking this question, it has already been asked on Q&A: http://forum.xda-developers.com/showthread.php?t=1384935
Hope this helps
mohanass said:
Hope this helps
Click to expand...
Click to collapse
Great so far, thank you again...
Hi Guys,
Emergency help required need to sell my 02X (need of cash) my customer needs with Stock ICS today.
Since stefans V28G ROM i have installed ics in my O2X. at that time i have changed to new bootloader. currently im using Django 1.4 rom with rooted condition.
with smart tool im trying to flash CP & AP Files V30B indian Version.
Smartflash starts, there is a error after few mins.
(Number of Partitions: 7) and then Error !
i tried to change from New to Old bootloader. using AIO toolkit using the 4th Option but it shows an aborted message.
Nothing working for me Guys indeed in a big help !
Waitng Waitng Waitng Waitng ((
Make sure you have the ABD & LG drivers installed.. After that follow the instructions in the AIO and change the USB cable if possible...
Jishnu Sur said:
Make sure you have the ABD & LG drivers installed.. After that follow the instructions in the AIO and change the USB cable if possible...
Click to expand...
Click to collapse
Jishnu Sur, vexed up by findinf ADB drivers ((( can you please provide me the drivers ? please any one ?
The required ADB (APX) drivers are already in AIO... There is a separate option for installing them in the Main Menu.... For LG drivers , they can be downloaded from LG support website...
------------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
---------- Post added at 06:24 PM ---------- Previous post was at 05:44 PM ----------
OK... here is the link to LG USB driver....
h t t p://w w w.lg.com/in/support-mobile/lg-P990
Required drivers are in Step 1 in the Software Update tab in the above page ...
As I'm a new member so not allowed to post links.... remove spaces from link...
--------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
owais40 said:
The required ADB (APX) drivers are already in AIO... There is a separate option for installing them in the Main Menu.... For LG drivers , they can be downloaded from LG support website...
------------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
---------- Post added at 06:24 PM ---------- Previous post was at 05:44 PM ----------
OK... here is the link to LG USB driver....
h t t p://w w w.lg.com/in/support-mobile/lg-P990
Required drivers are in Step 1 in the Software Update tab in the above page ...
As I'm a new member so not allowed to post links.... remove spaces from link...
--------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
Click to expand...
Click to collapse
try to change the order of the files.
cp-bin: ..........bin
ap-bin_...........fls(baseband)
good luck
real_pac said:
try to change the order of the files.
cp-bin: ..........bin
ap-bin_...........fls(baseband)
good luck
Click to expand...
Click to collapse
No need to quote my whole post..... I was answering his question about drivers which he asked in 3rd post..... And the better solution for smart flashing (when the drivers are installed properly) is that instead of changing the order of files just use the actual order and pull the battery back in just after the flashing starts.... This always works flawlessly ....
------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
owais40 said:
No need to quote my whole post..... I was answering his question about drivers which he asked in 3rd post..... And the better solution for smart flashing (when the drivers are installed properly) is that instead of changing the order of files just use the actual order and pull the battery back in just after the flashing starts.... This always works flawlessly ....
------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
Click to expand...
Click to collapse
whats ya problem?
i just wanna help him. i didnt see your post.
real_pac said:
whats ya problem?
i just wanna help him. i didnt see your post.
Click to expand...
Click to collapse
Yes exactly, that's what XDA is all about ... helping, sharing and learning ... That's what we are all doing here... but if u even didn't see my post then why did u quote it ... that makes no sense... Anyways Peace ....
------------------------------------------------------------
"Those who are not thankful to God's creation are not thankful to God".
Prophet Muhammad (Peace Be Upon Him)
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Thank you!
alray said:
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Click to expand...
Click to collapse
Thank you so much! Now I get what is what I might need help finding the right place or thread showing me how to flash the ROM etc. I will look around too of course now that I know what the problem is.
I need help...
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
The link posted by @alray above comes with the download and instructions for flashing TWRP. And the second link takes you directly to the rom.
The only way it could be easier is if he comes to your house and flashes it all for you
Hahaha, I'm sorry, that's embarrassing.
Bob the Swede said:
Hahaha, I'm sorry, that's embarrassing.
Click to expand...
Click to collapse
just take your time and read a lot ..it's all pretty simple once you get a grasp on whats going on
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
you will first need to upgrade your firmware like said in the rom thread. Click on the link in that thread "Latest Radios and Firmware are REQUIRED and can be found here"
follow instruction to flash the latest firmware in that thread
then flash twrp 2.8.0.1 (also linked in the rom thread just above "Latest Radios and Firmware..." link.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom to your phone (either using adb push/adb sideload/usb otg) and install it using twrp.
like cisa said above, if you follow the instructions in that thread andtake your time, everything will be good.
THANK YOU!!!
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Bob the Swede said:
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Click to expand...
Click to collapse
:highfive:
I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?
XDA-Nexus-User said:
I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
Click to expand...
Click to collapse
Just download the factory image of your choice and use fastboot to flash everything individually except userdata. You won't be wiped and all you'll have to do is re-root. Or just pick a ROM from development forums.
---------- Post added at 05:07 PM ---------- Previous post was at 05:01 PM ----------
Follow the steps in Method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
As I said, flash everything except userdata. Also skip the factory reset at the end.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
LMY47I is the newest AFAIK.
---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------
Also, questions go in the Q&A forum, not in general. I've asked the mods to move it there.
XDA-Nexus-User said:
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?
Click to expand...
Click to collapse
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.
cam30era said:
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.
Click to expand...
Click to collapse
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
M was issued as an OTA for T-Mobile users. That being said, @simms22 will confirm that LMY47I works just fine on T-Mobile.
whatever carrier you are on, everything will work regardless of which letter update you chose.
XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
Available only via OTA, which means you have to go back to 100% stock first. Here >http://forum.xda-developers.com/nexus-6/general/t-mobile-rolling-lmy47m-5-1-t3059371
im on I, and am on tmobile, with the 95r radio, and everything works, including volte
@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
XDA-Nexus-User said:
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....
XDA-Nexus-User said:
@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
you can do whatever youd like, everyone has their own priorities. me, i did it the easiest way, i dirty flashed 5.1 over 5.0.2, kept all my data, all my setup, and everything else. took about 90 seconds
cam30era said:
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....
Click to expand...
Click to collapse
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?
To add fuel to the fire, 5.1.1 is expected soon as well. This will, perhaps, unify all builds into one. This is based on the SDK being updated to 5.1.1 a few days ago.
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
XDA-Nexus-User said:
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?
Click to expand...
Click to collapse
Yes, correct.
Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.
XDA-Nexus-User said:
Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.
Click to expand...
Click to collapse
Glad you got it sorted and glad to have helped in any way.
Please give an example of a build where for example
A R build was older than an I build.
M is 4 days newer than I although I don't know why google hasn't posted the M build. Hopefully the next update brings all N6 to the same build
simms22 said:
im on I, and am on tmobile, with the 95r radio, and everything works, including volte
Click to expand...
Click to collapse
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.
XDA-Nexus-User said:
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.
Click to expand...
Click to collapse
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.
simms22 said:
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.
Click to expand...
Click to collapse
Are you verifying that other people receive the SMS message? It does not give an error of any kind.
When I tested it, was in a room with 4 different people, and the message appeared to go through. However, only 1 person on the list I started the group message with would actually receive it.
Mod edit: link removed (4pda links not allowed)
Booroondook has first done FUSE ROM and now there is he again... Bravo! Many, many improvements and fixes. Sorry he is not paying attention to XDA (doing all really for free, not for donations here) but he deserves all credits.
Full Post translation and download link
Here is the full post with download link, please donate to the dev if you like his work.
The firmware is designed as a "designer" under both options screen resolutions (800x480 and 1024x600). Everyone can afford to assemble his own version. How to assemble the firmware is described in detail here:
The order of assembly of the firmware
The firmware is available as a set designer or "do it yourself" - as anyone this thing called - and is a set of modules for self-assembly of the finished image of the firmware. The assembly is made on a computer running Windows (versions from XP and higher).
How to assemble:
1) Download the archive unpack into any empty folder on your computer (the full path to the folder does not contain spaces, non-Latin characters, punctuation marks and special characters, so not recommended for unpacking on the desktop, in the "My Documents", etc. )
2) turn in this same folder
3) Run start_rus.bat file (or start_eng.bat, if you are dearer to the English interface)
4) you will be asked to choose a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers specified opposite processor type, and then pressing the Enter key
5) The following sentence - to select the screen resolution. Options are also two - 800x480 and 1024x600. The selection is made in the same manner as in the previous paragraph
6) After this, the firmware build process, which takes less than 10 seconds.
7) The result of the process - file update_ <vash_protsessor> _ <vashe_razreshenie> .img, which, after renaming update.img you can sew in a familiar way radio When you first start after flashing is (as usual in my firmware) conducted preset application and then fit /system/build.prop configuration file under the processor type and resolution (800x480 for the recorder will be installed screen density of 160 to 1024x600 - 240). Then reboot, after which the tape recorder will be completely ready for operation.
Features flashing process. Due to the fact that changing breakdown flash memory sections (including as compared with previously released on FUSE-firmware Android 4.4.4), the process can be performed in two stages, both stages are the same.
That is, you normally install firmware mode rekaveri (thus necessarily choosing the option with full data cleaning). The device is rebooted and ... hang on animated screensaver. If you want to wait, wait - but the result is not guaranteed. If you do not want to wait, press the RESET, then (without releasing RESET'a) - POWER. Without releasing the POWER, release the RESET, waiting 3 seconds and release POWER. All - a few seconds later we are back in rekaveri mode where once again just repeat the flashing process - again, choose the menu item, involves the installation of firmware and data cleaning, and ... forward. After the second cassette recorder firmware to be released to the operating mode (although longer than usual, as is the formation of the primary file system).
Option: instead of the second flashing, you can try to select a lower menu item - "clean and reset to factory condition."
As you understand, all your data will be lost after flashing, so advance reservations and they do not say I did not warn.
Attention!!! Those who do not have the RESET button and mechanical buttons. Before flashing be sure to ask if you can overload the radio in rekaveri mode from the "hung" or off state. If this method is not, then you better not reflash.
OTA-upgrade
The firmware is the possibility of prompt automatic updates. OTA (Over the Air - "air") or FOTA (Firmware Over the Air) - a technology that allows to (semi-) automatically obtain and install the update packages. User Intervention here minimum - it is only necessary to press the button, confirming compliance with the installation. Well, there is still a button manually check for updates. And all the rest State makes self - sends a request to the server, downloads the update package, checks it for validity (verifies the certificate used to sign the update package with a key available in the firmware), reloads the State in rekaveri mode where automatically launches the update process, and finally PG reboots to the operating mode.
Naturally, for the possibility of State OTA-update should have a working Internet connection. Automatic prompting to check for updates are sent automatically after every download SI operating mode and communication with the Internet. If desired, you can request a renewal of the "out of order" by pressing the appropriate button in the dialog "Settings" - "About your device" - "OTA update system." Another essential requirement to enable OTA updates - is the availability of free space on the "GPS-card" (/ mnt / external_sd), and (of course) the availability and serviceability of the card itself. In case of problems with the card update can be downloaded to start, but then will be a network error. Available space on the card must be two times larger than the size of the update package. As practice shows, the usual pack "weighing" of up to 20 MB. Although there are cases of 55-MB blocks. In general, if you keep on the card 120 MB of free space, the problems you should not be.
Cancellation OTA update? Unfortunately, a simple interactive option is not provided. But you can do the following: Open the file for editing /system/build.prop. Find it (towards the end of the file) option ro.product.ota.host = www.booroondook.ru: 2300. Replace the URL-address of the update server (www.booroondook.ru:2300) to something "obscene". For example, suppose that this line will look like this: ro.product.ota.host = localhost. Save the file, restart the SU. Everything - Updates you will not torture any more.
Disclaimer: The self-fulfilling complicated technical procedure for flashing the device, you will definitely take full responsibility for possible negative consequences up to the irrevocable failure of your head unit.
Version - from 06/03/2016
Link to the firmware (made on the basis of KLD-20160511): https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
Innovations regarding the factory options:
- Cloning a resolution of 800x480 by kernel patch (kernel.img)
- Completely redesigned Russian translation
- Root access running SuperSU
- 5 launcher to choose from ( "Settings" - "Desktop")
- 4 options "Bluetooth" application ( "Telephone"), 5 application options, "Music" and "Radio". Alternative applications are installed through the "OEM" application, return to the original (nominal) version - after the usual removal of the application settings ( "Uninstall updates")
- In settings Added "For Developers", "Screen" - "Font size" and "Display" - "Display Density"
- In settings added to the monitoring data
- OTA-update functionality
- Added missing "OEM" applications, "Weather", "DVR" (Annex "Weather" - in the version revised respected vitarkananda)
- Added widgets "Weather", "Music", "Telephone", "Video" and "Navigation", ported from the firmware for MTCD
- Partition "OEM" is increased to 384 MB. This section can be used, for example, as a "warehouse" APK-relevant distributions
- Built-in support for working with trip computer Multitronics MPC-800 (Bluetooth-name DUAL-SPP)
Attention:
1) please do not ask questions why this firmware does not work Xposed. The answer is - it does not work and on the drive firmware, and generally have Xposed big problem with Android 5 (or higher). When someone finds a way to get to work on our Xposed firmware, in principle, I immediately implement it in its firmware.
2) Management of screensaver (MTCScreenClock.apk) is only possible through /system/build.prop File Edit (parameters ro.product.screenclock = true | false and ro.product.screentimeout = 5 | 10 | 15 | 20 | 30 | 60 ). Interactive control timeout in the factory firmware is not provided, and I realize it too failed.
Note: Because an application "Weather" uses a revised version of vitarkananda, the new version of the application (as they become available) can be installed instead of the usual simple by replacing labor-intensive system file.
For developers, the public certificate signed APK following: MTCBlueTooth.apk, MTCMusic.apk, MTCRadio.apk, MTCScreenClock.apk. This means that signing their "swing" application to the same certificate (and increasing code version), you can give users the ability to easily install your development instead of forcing them to carry out the replacement of system files with setting permissions.
https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Heisenberg said:
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Click to expand...
Click to collapse
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
typos1 said:
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda. If you'd like to become a moderator please feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
Click to expand...
Click to collapse
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Heisenberg said:
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Click to expand...
Click to collapse
Why 4pda links are not allowed? Where we can find list of prohibited sites?
pa.ko said:
Why 4pda links are not allowed? Where we can find list of prohibited sites?
Click to expand...
Click to collapse
The main reason is because 4pda is rife with piracy, warez, and there are major issues with GPL compliance on that site. You're also not meant to direct members to competing forums.
Thanks for explanation. True. But they also have original work like this...
pa.ko said:
Thanks for explanation. True. But they also have original work like this...
Click to expand...
Click to collapse
There is no way for you or I to know if that work is actually original. 4pda is notorious for kanging. On the surface it looks like original work but no way to prove that. This is beside the point though; 4pda is blacklisted for all of the rotten crap that takes place there, it's that crap that pulls down any original work that might be posted.
tried...not working
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
WECoyote633 said:
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
Click to expand...
Click to collapse
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
typos1 said:
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
Click to expand...
Click to collapse
not a developer...followed instructions in first post got error with the first step
WECoyote633 said:
not a developer...followed instructions in first post got error with the first step
Click to expand...
Click to collapse
This ROM is not compatible with 3066.
The build.bat is from a previous version.
miffymiffy said:
This ROM is not compatible with 3066.
The build.bat is from a previous version.
Click to expand...
Click to collapse
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
WECoyote633 said:
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
Click to expand...
Click to collapse
It is mentioned in the Lollipop thread and I think the original thread for booroondook's ROM, which is still open, this thread is kinda superfluous really.
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Answered 10 times already!
MCU is not important, you already have MTCB unit so you can flash MTCB roms (4.4.4. or 5.1.1.)
you are probably afraid because of ksp-v2.86, that does not matter so you can flash any MTCB based rom.
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Would probably be a good idea if you read the wiki before posting.
Does anyone know how modifing exception apks for MTCScreenClock? After I modified Build.prop to activate the Screenclock, it only works when radio apk, music apk,... are working and I'd like it works always except when I'm using GPS navigator.
By the other hand, I'd like to change transparent background for MTCScreenclock and I know that the installed MTCScreeclock.apk is not the issue because I used the same and it wasn't transparent in KitKat versions. Thank you
I have got installed in my headunit last LP version of DSA (5.1.1.).