OTA Update Center
Is an Over The Air update service, that is free of use.
OTA Update Center is an Over The Air update service, that is free of use. This project is especially for the rom devs around, to be able to implement an easy to use, and free OTA Update app. The project has one goal, to provide a way to provide OTA Updates as easy and noob friendly as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Add and remove OTA Updates in a centralised database.
Push notifications on new release of rom
Check for updates once a day.
Check for updates manually when the person wants to.
Download the rom and flash it directly.
Download the rom without flashing.
Wipe data and or cache/dalvik before flashing the update.
All your rom updates in one list.
Abillity to change, update and intergrate in your own rom, YES! It's open source!
Credits :: F.A.Q. :: Downloads :: Bug report
XDA:DevDB Information
OTA Update Center, Tool/Utility for the Android General
Contributors
M3nti0n, Vetruvet, Dexter93
Source Code: http://github.com/OTAUpdateCenter/ota-updater-2.0/
Version Information
Status: Stable
Current Stable Version: 2.0.5
Stable Release Date: 2014-10-12
Created 2014-11-18
Last Updated 2014-11-18
Reserved
Reserved
We appreciate the feedback!!
Home page updated! We are ready for the first ROMS
who says OTA is not possible for CUSTOM ROMS ???
This is going to be a big hit! OTA for All!
Nice work guys, let's hope some rom developers jump on this!
awesome work man :good: i'm waiting for ota app like this i'm ready to put my Unofficial Cyanogenmod 7.2 and Cyanogenmod 9 builds of LG P350
Nice work. Will see what I can do for FreeGS3.
hey. possible to push patches this way instead of replacing the whole rom?
great idea btw :good:
ron gokhle said:
awesome work man :good: i'm waiting for ota app like this i'm ready to put my Unofficial Cyanogenmod 7.2 and Cyanogenmod 9 builds of LG P350
Click to expand...
Click to collapse
Nice, tell me what you think about it
clark44 said:
Nice work. Will see what I can do for FreeGS3.
Click to expand...
Click to collapse
Use it like discribed in the FAQ on the website and you will be happy
antdking said:
hey. possible to push patches this way instead of replacing the whole rom?
great idea btw :good:
Click to expand...
Click to collapse
Yes, just like an OTA should, you just need to make a nice update.zip though, if the updaterscript isn't right it wont work
Can u change option after downloading zip file to "open recovery" becoz after downloading and choose "flash zip", my galaxy ace stucks at flashing screen Btw, this is really awesome work. I'm waiting for your reply and release new update for my rom.
Thank you!
Devilsking
Great work guys! Godspeed!
devilsking said:
Can u change option after downloading zip file to "open recovery" becoz after downloading and choose "flash zip", my galaxy ace stucks at flashing screen Btw, this is really awesome work. I'm waiting for your reply and release new update for my rom.
Thank you!
Devilsking
Click to expand...
Click to collapse
I think you are doing something wrong, its just going to the recovery as you say, its stuck on flashing screen, its the flashing screen of the recovery. be sure you are using ClockWork Mod Recovery and that the updaterscript is working perfectly. If you are sure you are using clockworkmod and the updaterscript is working the right way, please send me a pm with the recovery.log right after trying to flash using the OTA Updater.
badjaguar007 said:
Great work guys! Godspeed!
Click to expand...
Click to collapse
Thanks mate!
mweulink said:
I think you are doing something wrong, its just going to the recovery as you say, its stuck on flashing screen, its the flashing screen of the recovery. be sure you are using ClockWork Mod Recovery and that the updaterscript is working perfectly. If you are sure you are using clockworkmod and the updaterscript is working the right way, please send me a pm with the recovery.log right after trying to flash using the OTA Updater.
Thanks mate!
Click to expand...
Click to collapse
I can flash my rom normally in cwm recovery 5 and I dont think there're something wrong while it can run well I will send u log asap. Btw, I love ur work and I want to use it. Thank for ur hard work
Edit: tried again and after pressing "install zip" it boots and stucks at screen with a warning triangle and android icon. Here is log file. After failure of flashing via Updater, I tried to open recovery manually and flash the downloaded file. It can be flashed well.
Devilsking
devilsking said:
I can flash my rom normally in cwm recovery 5 and I dont think there're something wrong while it can run well I will send u log asap. Btw, I love ur work and I want to use it. Thank for ur hard work
Edit: tried again and after pressing "install zip" it boots and stucks at screen with a warning triangle and android icon. Here is log file. After failure of flashing via Updater, I tried to open recovery manually and flash the downloaded file. It can be flashed well.
Devilsking
Click to expand...
Click to collapse
Hey mate,
I would like to tell you what you'd do wrong there.
You'd not re-sign your rom after you edited the build.prop and adding the apk file i think.
Or you didn't sign the rom at all.
Please resign the rom, then check md5 hash again, and update that in the control panel.
Code:
Finding update package...
I:Update location: /sdcard/OTA-Updater/download/The Myth 2_2.0.1.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
[B]E:signature verification failed[/B]
[B]Installation aborted.[/B]
I hope you will be able to fix it that way, if not, please tell me about it
mweulink said:
Hey mate,
I would like to tell you what you'd do wrong there.
You'd not re-sign your rom after you edited the build.prop and adding the apk file i think.
Or you didn't sign the rom at all.
Please resign the rom, then check md5 hash again, and update that in the control panel.
Code:
Finding update package...
I:Update location: /sdcard/OTA-Updater/download/The Myth 2_2.0.1.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:verify_file returned 1
[B]E:signature verification failed[/B]
[B]Installation aborted.[/B]
I hope you will be able to fix it that way, if not, please tell me about it
Click to expand...
Click to collapse
lol. I signed it and it's flashable (I mentioned above). this only cannot flash when use updater I tried to flash downloaded file manually and it worked, my friend. If u have any solution, plz tell me. Thank u.
devilsking said:
I can flash my rom normally in cwm recovery 5 and I dont think there're something wrong while it can run well I will send u log asap. Btw, I love ur work and I want to use it. Thank for ur hard work
Edit: tried again and after pressing "install zip" it boots and stucks at screen with a warning triangle and android icon. Here is log file. After failure of flashing via Updater, I tried to open recovery manually and flash the downloaded file. It can be flashed well.
Devilsking
Click to expand...
Click to collapse
devilsking said:
lol. I signed it and it's flashable (I mentioned above). this only cannot flash when use updater I tried to flash downloaded file manually and it worked, my friend. If u have any solution, plz tell me. Thank u.
Click to expand...
Click to collapse
I tell you, remake the rom, add things in build.prop, add the apk, and after that sign the rom...
Try again, if its then still not working, just come back, we'd test it with many different roms, and also how it gave the signature error. and it only gives the signature error when its edited after the rom has been signed without re-signing.
mweulink said:
I tell you, remake the rom, add things in build.prop, add the apk, and after that sign the rom...
Try again, if its then still not working, just come back, we'd test it with many different roms, and also how it gave the signature error. and it only gives the signature error when its edited after the rom has been signed without re-signing.
Click to expand...
Click to collapse
But I did re-signed it If it's not resigned, it cannot be flashable.
devilsking said:
But I did re-signed it If it's not resigned, it cannot be flashable.
Click to expand...
Click to collapse
Please ask a real rom dev how to re-sign a rom, you cant just resign without removing the old sign. i bet some rom devs will be able to explain you how to sign your rom the right way.
Related
The procedure is quite simple.
Step 1.
Download the following tools:
Cyanogen Mod 7.1 for Xperia X8 (code named Shakira)
FlashTool
FXP030 kernel (2.6.29)
Step 2.
Step 2.1
Follow the guide located here to unlock your bootloader, do this before continuing with the rest of this guide it is important to have your stock firmware rooted for this step.
Step 2.2
Unzip flashtool to its own folder e.g. /Flashtool/.
Unzip FXP030 kernel to the Flashtool/firmwares/ folder - the directory should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3.
Step 3.1
Open Flashtool and click on the 'Flash' button, select the FXP firmware from the list on the left hand side and click OK.
Step 3.2
Follow the on screen instructions.
Step 4.
Copy the update-cm-7.1.0-X8-signed.zip to the root of your MicroSD Card as shown below. (Please note that you can do this using a MicroSD Card reader OR your USB cable.
If you do not have a card reader then switch your phone on after flashing the FXP kernel and when you see the FreeXperia logo, repeatedly press the Back button until CWM loads. Once CWM has loaded scroll down to the Mounts and Storage menu. Once on the mounts and Storage menu scoll down to mount USB Storage and copy the update-cm-7.1.0-X8-signed.zip file to the root of the SD card.
Step 5.
Load CWM via the method described in Step 4 and select 'Install Zip from SD card.' then select 'Choose Zip from sdcard' and select the update-cm-7.1.0-X8-signed.zip that you copied over to the root of the SDCard in the previous step, Select the yes option using the volume buttons and let CWM work its witchcraft.
Step 6.
Go back to the main menu of CWM and select 'wipe data/factory reset'.
Next from the main menu of CWM select 'wipe cache partition'.
Finally from the main menu of CWM select 'Advanced' and 'wipe dalvik cache.
Optional
If you want the google apps installed you can download them here. To install them perform Step 4 through to Step 5 and instead of copying 'update-cm-7.1.0-X8-signed.zip' to the root of your sdcard, copy gapps-gb-20110613-signed.zip instead. All instructions in Step 4 and Step 5 that state you should use 'update-cm-7.1.0-X8-signed.zip' should use the file 'gapps-gb-20110613-signed.zip' instead.
Notes:
I'm having issues with the networking with this custom firmware, specifically the network (3G or WiFi) seems to 'drop' after any amount of small usage. If I use a Browser or the Market place for a short amount of time, they simply end up unable to load any pages whilst android reports that wifi/3g signal strengths are full. I tested the connectivity using ping commands from terminal and pings are succesfull. I'm unsure where the issue lies. I suspect however the issue is in the FXP Kernel, some people have reported using FXP 028 Kernel resolves the issues but I've been unable to find them.
Anyway I hope this helps people who are confused as to how to install this.
Credits:
Thanks to Paschalis for correcting an error in my wording.
Thanks go to dbts25 for pointing out mistakes and un-neccessary steps in the guide, sincethen the guide has been edited to be easier to follow and less convoluted.
Thanks go to rav3n_pl for the revised bootloader bundled with the kernel.
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Paschalis said:
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Click to expand...
Click to collapse
Ah Yes, I mean stock. It's 2:34am... That's my excuse haha, between university and sleep deprivation the mistakes keep mounting hehe. Thanks for pointing that out anyways.
And yes, it seems this kernel has issues with data connectivity, and call volume as well for some odd reason. It boggles the mind as to why it's been labelled 'stable'. Stable usually means it's solid and won't fall over and die, plus data connectivity on an android handset is really a critical feature, if it is buggy the custom firmware should not be labelled as stable.
It really need custom kernel?
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
EL_BELLACO said:
It really need custom kernel?
Click to expand...
Click to collapse
Yes, if you don't use a custom firmware it will get stuck in a boot loop and be unable to boot.
Paschalis said:
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
Click to expand...
Click to collapse
If I come across it I will, I'll edit my guide to feature it as a work around for connectivity issues for people in the meantime, if it works correctly.
I've got to admit though, issues aside - it is amazing what the open source community is capable of creating. CM 7.1 looks absolutely fantastic, I love the boot animation.
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
termin8tor said:
.
Step 5.
Turn your phone on and repeatedly press the back button until you are displayed with the CWM menu. On this menu select 'install zip from sdcard' and then choose the 'choose zip from sdcard' select the cyanogenmod file you downloaded and let it do its thing.
Click to expand...
Click to collapse
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
poisike said:
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
Click to expand...
Click to collapse
Can you please share the FXP028 kernel?
has any of you tried the dx kernel yet? with cynanogen mod 7.1
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
dbts25 said:
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
Click to expand...
Click to collapse
I've edited the guide to eliminate that pointless step in the original guide version, thankyou for pointing it out!
Additionally the google apps step has been added to the end of the tutorial.
tonks22 said:
has any of you tried the dx kernel yet? with cynanogen mod 7.1
Click to expand...
Click to collapse
Unfortunately the rom will not boot with the DX kernel, I tried it myself and it gets stuck in a boot loop.
rav3n_pl said:
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
Click to expand...
Click to collapse
I have included the correct kernel for the official cyanogenmod 7.1 rom and slipstreamed your edited loader into the kernel package for peoples convenience. Thanks for linking me to your post!
Hope this helps people!
It seems that this Rom and kernel [cm7] doesn't work.When i flash the kernel my SD is not recognized.And if i uninstall the kernel and try to flash the rom...i get a biiiiigg eror
i hope that they will also make a ROM that is compatible with stock kernel so that it will be easy to install... im having second thought of unlocking my bootloader because of this:
Before I start I must emphasise the fact that meddling with the bootloader is highly dangerous and will result in a hard brick if you don't follow proper instructions. Then, you will have to go and repair your phone by sending it to SE . I am not responsible if your phone dies on you because you didn't follow instructions or you screwed up somehow. I must also mention that this will probably void your warranty (rooting already probably voided it though) and that there is NO WAY to relock bootloader as of now.
Click to expand...
Click to collapse
i know they can make one because they are great programmer...
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Paschalis said:
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
mikel_0004 said:
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
Click to expand...
Click to collapse
There:
http://forum.xda-developers.com/showpost.php?p=17656148&postcount=1
Can it be installed WITHOUT unlocking the bootloader?
Thanks
thu001 said:
Can it be installed WITHOUT unlocking the bootloader?
Click to expand...
Click to collapse
I`m not 100% sure that cm71 rom will work on stock kernel...
When I flashed it under installed CM7 it stuck on bootanimation. Mybe full wipe? Not tried.
Hello
I installed on my Xperia X8 CM7.1 (I had version 2.1 of Android root), but it does not work the WiFi network and the 3G connection is disconnected, it did not work properly Market (having installed the GAPPS). My question, is there any way to get back to my terminal to android 2.1? I did a Back up of my system, but in trying to restore from CWM mistake I make, I guess it is for the kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since we got update threads scattered everywhere, I figured I'd organized things into one thread, as well as give away some new updates.
Retail EU:
81.5.31006-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.32002-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.4002-91.2.26001.Retail.en.EU 4.0.4-4.1.2
Retail GB:
81.5.31002-81.5.39001.Retail.en.GB 4.0.4-4.0.4
81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2
Orange GB:
81.5.31002-91.2.26001.Orange.en.GB 4.0.4-4.1.2
O2 DE:
81.5.32002-81.5.39002.O2.en.DE 4.0.4-4.0.4
81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2
Vodafone FR:
81.5.31002-81.5.39001.Vodafone.en.FR 4.0.4-4.0.4
81.5.39001-91.2.26001.Vodafone.en.FR 4.0.4-4.1.2
Brasil BR:
871.110.12008-871.110.12012.Brasil.en.BR 4.0.4-4.0.4
871.110.12012-871.111.20003.Brasil.en.BR 4.0.4-4.0.4
871.111.20003-982.50.20.Brasil.en.BR 4.0.4-4.1.2
AmericaMovil MX:
871.110.13009-982.50.25004.AmericaMovil.en.MX 4.0.4-4.1.2
If you have an OTA update.zip please PM it to me or contact me on google talk ([email protected]) and I will quick add it to this thread, with safe hosting, credits to The Firmware Team's Pzyduck for providing safe-haven for these types of files.
Instructions for pulling an OTA update.zip:
Do NOT install the update! Do these first!
Be rooted. We got plenty of methods. Motofail2go for ICS, and my RAZRiRoot.zip for turl1's Clockworkmod.
Download the Root Explorer app, or the ES File Manager app. (Instructions are for Root Explorer.)
Open Root Explorer and go to the ~/cache/ directory, which resides on the root directory of the phone '~/'
Hit the 'Mount R/W' in the corner, if successful will then say 'Mount R/O'
Copy the update file .zip from the ~/cache/ to your sdcard, external to be safe. External is in ~/mnt/external1/ and Internal is ~/sdcard/.
Copy over the update file .zip from the sdcard(s) you chose to your computer and upload it.
You will want to use Voodoo's OTA Rootkeeper before updating if you have a locked bootloader, you can find my thread on a RAZR i compatible version here.
Send me or post a link here to the update and exactly what System Version you were on, and where the update takes you to.
The community will thank you for your help!
Enjoy. Remember to do your part to the community and contribute all updates!
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Vistaus said:
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Click to expand...
Click to collapse
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
HSD-Pilot said:
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
Click to expand...
Click to collapse
Thanks! Uploaded to server, renamed, and added to the OP.
mattlgroff said:
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Click to expand...
Click to collapse
mattlgroff, im in 81.5.31006.Retail.en.EU - 4.0.4. and in software update i get notification of an ota. i down loaded that file when ask if i want to install it i select yes. but when in recovery it always fails. why, isnt that the official? because after that i tried flashing it in recovery but it fails too.
before alll this i was already on 81.5.40002.Retail.en.EU - 4.0.4. coming from 81.5.31006.Retail.en.EU. but i wanted to downgrade back to 81.5.31006.Retail.en.EU. and my phone died. thanks to hsd pilot my phone came back to life he sended me a file http://forum.xda-developers.com/attachment.php?attachmentid=1528201&d=1354399653. but now im stuck in what i told you at the begining. why?? what can i do to go back to 81.5.40002.Retail.en.EU. i know this is not the thread sorry but i was watching your new otas. and i cant install the one for my version.
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
HSD-Pilot said:
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
Click to expand...
Click to collapse
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.
mattlgroff said:
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.[/QUOTE
thank you guys!!! that was the problem and another one was that i erase alot of apk.s that i dont use so at time of flashing i saw it said something about an apk. missing so i fastbooted again and flash boot.img and here i am with the 40002.rt.eu. and now waiting for jellybean
Click to expand...
Click to collapse
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
joel_sinbad said:
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
Click to expand...
Click to collapse
Yes you can.
I have version 871.110.12008.XT890.Brasil.en.BR installed from sbf.droid-developers
My Razr i bootloader is unlooked and rooted. When i try to install the update with the android button (in about system) i recive error message after reboot. How can i install this update manually with fastboot console?
Thanks!
First, use an Root Explorer and copy your downloaded Update Zip out of the Cache Folder and leak it
Edit : Ok, it's in the OP already. Sorry, it's 1am in Germany :sly:
Your RazR i is rooted, how did you root it? If you used the Unlocked Root (insecure Kernel), than grap the boot signed out of the sbf you flashed and use fastboot to install it
fastboot flash boot boot_signed.
After that it should work. If not, you maybe deleted some System Apps. If that's the case, flash the system_signed.
Sent from my XT890
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
josmel91 said:
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
Click to expand...
Click to collapse
I have no clue. I'd ask in the Q&A section if you want an answer quickly
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Semseddin said:
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Click to expand...
Click to collapse
After getting a DMCA Takedown Request from posting those before from the MB886 I'm afraid I can't help you there.
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
jenova941 said:
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
Click to expand...
Click to collapse
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
mattlgroff said:
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
Click to expand...
Click to collapse
Thanks, downloading. Do I just flash it using CWM, RSD Lite or something else?
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
Disclaimer
As always, if you **** your phone up, it's not my fault. Don't blame me. Further, I will not answer any questions about this. Please help yourself.
Please use the "Thanks" ( :good: ) button if you just want to say "Thank you" or "Great" or "I wanna marry you".
Prerequisites
HTC One M8 Dual SIM (m8_dugl)
A complete backup of your phone! (e.g. with titanium backup)
fastboot installed
USB Cable
Some time (do not hurry!)
htc DEV UNLOCK (http://www.htcdev.com/bootloader/unlock-instructions)
Warning
Make sure you have a "m8_dugl" device:
Reboot your device to the bootloader (POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN). If it reads there something different than "m8_dugl", then this guide is not for you!
Steps
Download the custom recovery "TWRP" from here: https://s.basketbuild.com/devs/Captain_Throwback/One (M8)/ALL/Recovery (See hint below)
Download "UPDATE-SuperSU-vX.XX.zip" from here: http://download.chainfire.eu/supersu
Copy "UPDATE-SuperSU-vX.XX.zip" to you phone's internal SD
--> Until now no harm has been done to you device but DEV UNLOCK. So this would also be a good time to do a BACKUP! #JustSaying
Open a command prompt and navigate to your fastboot executable.
Put your phone into fastboot mode: POWER+VOLUME_UP until the screen blacks out, then press POWER+VOLUME_DOWN. You see some options soon. Use the volume buttons to navigate, the power button to perform the selected action. Select FASTBOOT and press the POWER button.
Connect you phone to the PC
Type "./fastboot boot path/to/where/you/saved/TWRP_Recovery_x.x.x.x_M8_CPTB.img"
If boot does not work, you can flash the recovery to your phone. But remember: When you do a stock update, you must revert back to a stock recovery!
Do flash the custom recovert, type "./fastboot flash recovery path/to/where/you/saved/TWRP_Recovery_x.x.x.x_M8_CPTB.img"
Touch "Install"
Select the "UPDATE-SuperSU-vX.XX.zip" file
Swipe to start
Touch Reboot System.
You're phone should be rooted.
** Hint **
If the newest TWRP does not work, try a different one.
If none of them work, try the official one: http://teamw.in/project/twrp2/225
If the official TWRP does not work for you, you can try the following one, but it's rather old: http://forum.xda-developers.com/htc...al-sim-european-version-t2816991/post54258731
****
Cheers,
Chris
PS: @donmarkoni provided some resources that might be useful to you. See his post: http://forum.xda-developers.com/showpost.php?p=56134225&postcount=12
Changelog:
[2015-01-18] Updated parts that do not work anymore. Made version numbers generic.
[2014-10-20] a) I have been hinted that the official TWRP should work for the m8_dugl as well. b) The current version of SuperSU is v2.14 and works well. c) @donmarkoni provided some more resources worth mentioning.
cimnine said:
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
Disclaimer
As always, if you **** your phone up, it's not my fault. Don't blame me. Further, I will not answer any questions about this. Please help yourself.
Prerequisites
HTC One M8 Dual SIM (m8_dugl)
fastboot installed
USB Cable
Some time (do not hurry!)
htc DEV UNLOCK (http://www.htcdev.com/bootloader/unlock-instructions)
Note: Reboot your device to the bootloader (POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN). If it reads there something different than "m8_dugl", then this guide is not for you!
Steps
Download the custom recovery from here: http://forum.xda-developers.com/htc...al-sim-european-version-t2816991/post54258731 (It must be made for the m8_dugl, the 'normal' m8 recoveries from TWRP/CWM do not work (yet)!)
Download "UPDATE-SuperSU-v2.02.zip" from here: http://download.chainfire.eu/supersu
Copy "UPDATE-SuperSU-v2.02.zip" to you phone's internal SD
Open a command prompt and navigate to your fastboot executable.
Put your phone into fastboot mode: POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN. Now you see some options. Use the volume buttons to navigate, the power button to perform the selected action. (Just select FASTBOOT and press the POWER button.)
Connect you phone to the PC
Type "./fastboot boot path/to/where/you/saved/m8-dual-twrp.img"
--> Until now no harm has been done to you device but DEV UNLOCK. So this would also be a good time to do a BACKUP! #JustSaying
Touch "Install"
Select the "UPDATE-SuperSU-v2.02.zip" file
Swipe to start
Touch Reboot System.
You should be rooted.
I did not test that yet, but this method should not prevent you from receiving OTAs. But I won't vouch for that.
Cheers,
Chris
Click to expand...
Click to collapse
Thank you Chris,
step by step guides are always helpful, as the answer a lot of questions about the whole procedure. So I´m at least rooted now. Let´s see if OTA´s will work, but they can also be installed via adb. I prefer having a custom recovery for installs and making backups from data, so this solution is the one I need (and always used before btw).
Thank you !
Guido
thanks alot i hope xda opening section for us HTC-M8 Dual Sim Owners
[deleted]
guidogsbn said:
Thank you Chris,
step by step guides are always helpful, as the answer a lot of questions about the whole procedure. So I´m at least rooted now. Let´s see if OTA´s will work, but they can also be installed via adb. I prefer having a custom recovery for installs and making backups from data, so this solution is the one I need (and always used before btw).
Thank you !
Guido
Click to expand...
Click to collapse
Hi
I hope you will tell us if the OTA will work.
By the way, do you know of unlocking the bootloader with HTC Dev create any issue for the future OTA?
Cheers
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
thebighunt said:
Hi
I hope you will tell us if the OTA will work.
By the way, do you know of unlocking the bootloader with HTC Dev create any issue for the future OTA?
Cheers
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
Click to expand...
Click to collapse
With re-locked bootloader and stock recovery OTA will work:good:
guidogsbn said:
With re-locked bootloader and stock recovery OTA will work:good:
Click to expand...
Click to collapse
Thanks
I'm still with the stock recovery
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
Stuck in a boot loop
Hi,
thanks for the guide and it worked perectly. No problems all day long after rooting the phone.
But since this morning I am stuck in a boot loop! Already tried factory reset, that works at first, after the phone is loading some updates, it is running into a boot loop
Is there anything I can do?
Rgds
Volker
Edit: Updated SuperSu, Works again...
m8 update ?
any1 knows if we are ever gonna get updates like regular m8 ? , i am still waiting on the root thing hoping they will update ,
any1 have any information or should i go ahead and root ? , is the performance better after rooting and removing all that bloatware or no significant difference ?
last question plz , does xposed module work with this phone and sense 6 toolbox use in android revolution hd rom ?
i tried asking million times here and and htc and called them and chatted online with them and all says they have no information and only 1 source ( august-sept ) under testing ,, so thats why i am asking plz if any1 knows anything , or can u advice me what to do ?!! cuz my phone sucks compared to my friends regular updated stock m8 in every aspect , sound , performance , battery , benchmarks , ......etc
aymanzz said:
any1 knows if we are ever gonna get updates like regular m8 ? , i am still waiting on the root thing hoping they will update ,
any1 have any information or should i go ahead and root ? , is the performance better after rooting and removing all that bloatware or no significant difference ?
last question plz , does xposed module work with this phone and sense 6 toolbox use in android revolution hd rom ?
i tried asking million times here and and htc and called them and chatted online with them and all says they have no information and only 1 source ( august-sept ) under testing ,, so thats why i am asking plz if any1 knows anything , or can u advice me what to do ?!! cuz my phone sucks compared to my friends regular updated stock m8 in every aspect , sound , performance , battery , benchmarks , ......etc
Click to expand...
Click to collapse
I read somewhere that our dual sim should get directly Android L and until then no update. Xposed module, sense 6 and Wanam Xsense are working good, of course u need to be rooted
FYI - You might want to update this guide to point to the official TWRP for M8 now that it supports Dual SIM.
cimnine said:
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
...
Cheers,
Chris
Click to expand...
Click to collapse
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
OTA_M8_DUGL_K444_SENSE60_MR_HTC_Europe_3.33.401.6-1.45.401.12_R_release_3986927s90q9xyzwqo8q8g.zip
Cheers!
donmarkoni said:
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
Cheers!
Click to expand...
Click to collapse
No need to post my TWRP here - the official one works fine.
Captain_Throwback said:
No need to post my TWRP here - the official one works fine.
Click to expand...
Click to collapse
OK, I will remove if you want me to, but most of the credit goes to you for unified TWRP, working MTP and UMS.
donmarkoni said:
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
Cheers!
Click to expand...
Click to collapse
@donmarkoni: i posted this question in the stock recovery thread but got no reply...
i have downloaded the mega file 0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Ra.... 2 times before and tried winzip, 7-zip and winrar but zip file is corrupt. is this a new file? i cant see an md5 or sha. size of my download from windows properties is 1,506,353,851 bytes.
have you checked the file?
the '2014-07-26--03-35-20 KOT49H release-keys.zip' is a clean TWRP backup?
i have made my own backup by temp installing TWRP 2.8 so can also confirm that works (thanks again Captain_Throwback)
any sign of an original RUU yet?
Stepp said:
I read somewhere that our dual sim should get directly Android L and until then no update. Xposed module, sense 6 and Wanam Xsense are working good, of course u need to be rooted
Click to expand...
Click to collapse
See that table from http://android-revolution-hd.blogspot.ch/2014/10/htc-devices-to-receive-android-50.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
guidogsbn said:
With re-locked bootloader and stock recovery OTA will work:good:
Click to expand...
Click to collapse
That's why I usually don't install the recovery but only boot it. We'll see in Spring 2015 if it works, it seems that we won't get an update any sooner.
PS: Can some moderator remove the 5 Minutes Wait restriction from my account? I'm not exactly new to XDA, am I?
gazzacbr said:
@donmarkoni: i posted this question in the stock recovery thread but got no reply...
i have downloaded the mega file 0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Ra.... 2 times before and tried winzip, 7-zip and winrar but zip file is corrupt. is this a new file? i cant see an md5 or sha. size of my download from windows properties is 1,506,353,851 bytes.
have you checked the file?
the '2014-07-26--03-35-20 KOT49H release-keys.zip' is a clean TWRP backup?
i have made my own backup by temp installing TWRP 2.8 so can also confirm that works (thanks again Captain_Throwback)
any sign of an original RUU yet?
Click to expand...
Click to collapse
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12.....signed.zip is a encrypted signed zip, as the file name suggests. It does work, as you can see here. All other files are good too. That's all I can say about it, as I don't have that phone, I was just helping.
cimnine said:
That's why I usually don't install the recovery but only boot it. We'll see in Spring 2015 if it works, it seems that we won't get an update any sooner.
PS: Can some moderator remove the 5 Minutes Wait restriction from my account? I'm not exactly new to XDA, am I?
Click to expand...
Click to collapse
Maybe earlier with 4.4.4 as LLabTooFer4 posted on twitter :
LlabTooFeR @LlabTooFeR 30. Sep.
M8 Dual SIM users don't be disappointed not getting 4.4.3, you will get 4.4.4 before the end of October
:good:
donmarkoni;...encrypted signed zip...That's all I can say about it said:
Ok, thanks for info. Looks like at least one user had success with it so i will keep it in a safe place
Click to expand...
Click to collapse
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.
it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.
AWESOME!!! Thanks for the information!
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
Click to expand...
Click to collapse
I actually have no idea what to do. I'm on a locked bootloader and I have never unlocked and flashed a custom rom on my z3c.
Was just, sharing some info and hoping people would test
matthiastan5 said:
it's finally released for our z3c!!!
http://get.aospa.co/official/aries
I believe need to unlock bootloader first before flashing so take note.
Click to expand...
Click to collapse
Thanks for info.
For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?
Arch9 said:
For anyone who already running this rom, how is it? Does the baseband and camera work (no fisheye effect)?
Click to expand...
Click to collapse
Neither one nor the other. All other things seems working fine.
juliopw said:
Same process then? flash boot.img and zip from TWRP?
Edit: Everytime I do that, my phone doesn't boot. Be it with CM or other ROMs, and I have to flash a stock tft. I'm currently on Concept, since I've never managed to get CM working.
Edit2: tried to install but had to modify the install-script. My device was being recognized as "z3c".
Edit3: error flashing, same thing as CM. Flashing stock MM to see if it has something to do with using Concept before.
Edit4: can't enter recovery after flashing stock MM. Going back to Concept and not sure what to do next
Edit5: that's the error I get in TWRP
View attachment 3786599
Click to expand...
Click to collapse
I get the same error 7 when trying to install PA. Ive tried modefying the install-script as you did but then i get error 6.
I flashed stock D5803_23.5.A.0.575_R11D_Nordic Generic_1288-5411.ftf and then flashed recovery to TWRP via fastboot but i still get the same error 7 when trying PA after that.
My next attempt is to install that NUT dual recovery and try flash PA after that.
Camera and modem not working
Got it installed (finally...). You need a working TWRP recovery.
What's working:
- WiFi
- Paranoid OTA seems to work; no further build available to try (doubt that it will work without recovery though; see below)
Not working:
- RIL (so no phone or SMS)
- camera
BT and GPS not tested yet.
To be able to flash you need to
- modify updater-script located in META-INF/com/google/android/updater-script (which is actually a text file) of the ROM zip
- open it in a text editor
- replace "aries" with "z3c", save it somewhere (delete .txt if it's saved with this extension; filename must be "updater-script")
- open the zip with 7zip (recommended; dunno if it works with other archivers)
- replace the updater-script with your version in the zip
- place the zip onto your device
- enter recovery
- Factory Reset (no need for a full wipe)
- flash it
- flash MM Gapps directly afterwards (OpenGapps not recommended - use Slim Zero Gapps instead)
- if you want root, flash SuperSU BEFORE rebooting (see below)
Recovery will be lost and can't be installed with TWRP Manager or Rashr after flashing (Didn't work for me - please report if you got it working and if so - how. Maybe with fastboot, didn't try that yet)
Happy flashing...
I'm sure issues will be fixed quite fast in later builds as everything works already in latest Carbon ROM (find it on testing.myself5.de). Maybe @Myself5 can help with that...(?).
juliopw said:
Camera and modem not working
View attachment 3786769View attachment 3786770View attachment 3786771View attachment 3786772
Click to expand...
Click to collapse
I flashed and it's same with you.It's not okay for daily driver.Also it overheats a lot.
Nice, they said they already fixed the mobile radio bug internally and will be releasing a new build soon
radio is fixed and currently fixing camera
From PA's official Google+ post:
We are also announcing that with the help of Sony and their Open Devices Project we will be able to support all 22 Xperia devices on the SonyXperiaDev GitHub Instance. This initial Sony release is for the Shinano family, but the Rhine, Yukon and Kitakami platforms are expected to follow shortly. This is really exciting news for us and it allows us to give you the Android experience we all love on a much wider range of devices.
Click to expand...
Click to collapse
If this is the case, maybe the camera will actually be usable? What do you think guys?
P.S. We should contact a moderator to move this thread to General forums, this is not development.
where is the zip file ?
ultraaslan88 said:
where is the zip file ?
Click to expand...
Click to collapse
It's removed for the meantime
That's because it had so many bugs
Wait for some more days for a better build
Anyone have mirror for last version?
Can i flash this rom on my z3c with SliMM 1.9?
GabrielVacker said:
Can i flash this rom on my z3c with SliMM 1.9?
Click to expand...
Click to collapse
You need unlocked bootloader for this
dont Found file
Wysyłane z Compacta za pomocą Tapatalk 2