GPE 5.1 Android L-MR1 notification - One (M8) General

Just got a notification saying that the 5.1 GPE update is available for download. I don't even have a gpe phone just the loserskater gpe rom....I'm downloading the update right now if someone wants me to upload it.

{
"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"
}
Sent from my HTC One_M8 using XDA Free mobile app

Can you pull the OTA file and upload it?

digitalhigh said:
Can you pull the OTA file and upload it?
Click to expand...
Click to collapse
I have it uploaded to my site already.
I need someone who isn't rooted and hasn't touched the system on 5.1 to PM me please so you can help me pull the system partition so I can create a 5.1 RUU. You must have time to be able to pull the system, root the device and then pull the system again and upload both images.
Thanks

Update error
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela

ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
As far as I understand you will need a rooted 5.1 version... Or you can flash the unrooted ruu and then update...

Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.

Destroyer706 said:
Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.
Click to expand...
Click to collapse
Mmm.. not so cool.. but thanks for the reply anyways.
Maybe to much of an effort to unroot (any link on how to do that for this device?).
Might wait for the RUU rooted/unrooted from graffixnyc as that's much more simple to apply.
Ratatella

ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.

benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
PS: Found rooted and non-rooted 5.1 RUU for M8 here:
http://www.graffixnyc.com/m8.php
Ratatella

ratatella said:
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
Click to expand...
Click to collapse
Funnily enough, it's in the GPe OTA thread

boot issue
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.

So if I'm on a custom ROM this update is just the stock GPE ROM? So in order to maintain the ROM I'm using I need to wait for a rom release and ignore this?

I just got this OTA update as well.
I converted my phone to UNrooted 5.1 RUU last week.
I run the update, it reboots goes through the install with no errors, restarts, goes through the "Android is upgrading... and optimizing apps".
But once it's finished, the update notification still popsup as if it didn't upgrade... ran it a second time, and for whatever reason this time it "took". Checked my phone and it said it's up to date.
Very odd.

Is it needed?
Hi everyone,
A bit of a newbie, so not quite sure if this is obvious to everyone else, but here goes...
I recently installed the rooted version of [RUU] M8 Google Edition Conversion. 5.1 LMY470.H4 provided by @graffixnyc as per this thread.
Everything worked fine, and I now have a rooted HTC One M8 running stock GPE 5.1. All fine & dandy, thankyou @graffixnyc...
Today (July 8, 2015) I am told that my phone has downloaded the OTA Android L-MR1 modification. Being in New Zealand it seems to have finally arrived here two months after everyone else received it.
My question is this - do I need to install the upgrade, or have I already got it thanks to the ROM I have already installed?
Another question is - if I do need to install it, are there any special steps and/or procedures I need to take in order to install it without doing something bad (& irrevocable!) to my phone?
Hope this doesn't sound newbie-ish... I am quite prepared to RTFM if someone can point me in the direction of appropriate answers to my questions,
Cheers,
Attobrute

adamparsons said:
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.
Click to expand...
Click to collapse
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.

adamparsons said:
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.
Click to expand...
Click to collapse
I was able to recover from my issue .
For anybody else that runs into the same issue, this is what I did:
1) re-flashed twrp custom recovery
2) made data backup
3) created by own custom (system-only) ruu using graffix's gpe rooted ruu as a base. I basically deleted all img files from the zip file except for the system image.
4) I flashed the custom (system-only) ruu via fastboot
5) let the system boot
6) skipped all the account signup and settings stuff
7) rebooted the system one more time just to make sure things are still good ( I don't think this is necessary but I did it and things seemed to work for me )
8) rebooted into recovery
9) restored data backup that I made in step 2
10) let android do it's thing ( optimize and stuff )
And that's it. Things seem to be back to the way they were before applying the update. Even the android update notification, which caused me all this pain to begin with, is back.
The only thing I have left to do I guess is figure out how to get rid of the notification.
BTW, If I'm not mistaken, this update is not needed. I think it's already included in the 5.1 GPE room graffix supplies.

Hello,
I installed Android 5.1 GPE with the "Rooted Flashable Stock Rom Build"(zip file install wit twrp) from graffixnyc a month ago. Is there an Update package(ruu?/ota?) that I can use to apply the L-MR1 upgrade without losing my data?
Thanks

Got this update this week too. In fact are two updates, one is 24mb and other is 20mb. Still stays on Android 5.1 instead 5.1.1, but build number changed two times, ending .h5 and .h6. Don't know what changed, maybe just bugfixes.

Can someone upload the ota packages?

Related

[Guide] Easiest way from root to stock :)

I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"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"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)
Wow..can't get any simpler than that..thx for this.
Thanks. Very simple.
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App
Wow... Much appreciated!
laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!
Would this work on the AT&T N1?
RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:
wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
http://forum.xda-developers.com/showthread.php?t=686593
Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!
RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.
Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.

The Unofficial Thread of Official OTA Updates

{
"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?

[GUIDE] How to root m8_dugl (M8 Dual SIM)

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

5.1.1 root tips / tutorial?

Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
m123456789 said:
Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
Click to expand...
Click to collapse
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
levone1 said:
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
Click to expand...
Click to collapse
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
m123456789 said:
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
Click to expand...
Click to collapse
I haven't yet tried .216. Its new as of a couple of days ago. I also haven't yet tried PRFs. I've read a few threads that seem to indicate occasional problems with them. Since I have unlocked bl, I've been able to root the easy way, so I'm not sure what options or limitations there are with that rooting method. From my experience, I would recommend RockZ1 ROM, (.368). It has anything you would want included, and may well update to the new fw anytime soon...
Don't unlock the bootloader many functions will be lost if you are trying to keep the stock rom.
Sent from my C6902 using XDA Premium 4 mobile app
The device is now in Boot Loop after trying to go from the 5.1.1 to 4.4.4 using Sony Mobily Flasher and then trying to install 14.4.A.0.157 ...
What did I do wrong, what can i do now?
Thanks for any help
I just turned phone off, loaded 14.4.A.0.157 with Sony Mobile Flasher, plugged in with volume down key. Then it was flashing and finished. Then unplugged and started.
And now it keeps restarting at startup (when the "waves" appear). That's a bootloop right? I turned it off with the small red button now.
I tried flashing again with same method. And it is still bootlooping after it......
Any expert could help? Or is the phone broken forever now
Did you wipe data / cache?
Steffe89 said:
Did you wipe data / cache?
Click to expand...
Click to collapse
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
{
"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"
}
http://i.imgur.com/RCJNhRO.jpg
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
DetmL said:
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PC Companion does not recognize the phone. When i plug it in, it says searching, but then... "no phone connected"
But in windows i see it connected as a drive which i can not use
m123456789 said:
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
http://i.imgur.com/RCJNhRO.jpg
Click to expand...
Click to collapse
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
levone1 said:
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
Click to expand...
Click to collapse
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
m123456789 said:
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
Click to expand...
Click to collapse
The msg about unknown sources, etc. comes after the flash bc now your phone is stock, so by default they're not checked. It wouldn't have flashed if they weren't checked in the first place. You'll probably hit some bumps, but don't give up. There's almost always a fix...
On rooted 4.4.4 with Superuser installed. Then trying to load the prerooted 5.1.1 zip.
So rebooted with volume down and installed the prerooted zip file from SD. With CWRM
Everything seems to work, but at the end of flashing i saw some message like:
"set_perm some changes failed"
Then after restart all apps get optimized and i am on 5.1.1.
However, i think i lost root, also no SuperUser installed? And the Superuser was included in the zip prerooted file.
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
m123456789 said:
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
Click to expand...
Click to collapse
It's not worth it to update, believe me
m123456789 said:
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
Click to expand...
Click to collapse
Open recovery > select 'install' > choose file. You'll get a long reboot and the whole 'optimizing' thing again.
Yes, after installing xposedv75, it rebooted and loaded addiotional ~+100 apps But it seems to work.
What program would you guys recommend in terms of saving data, restricting internet access of apps (and maybe even ads). And some other for spoofing/restricting requested usage access of certain apps?
(I tried Xprivacy, but it is pretty advanced. It did not seem to block inapp ads or internet access, even when you denied it. Also it only lists apps which are newly installed, not preinstalled ones.
Maybe it is easy but I just didn't understand it yet )

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

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.

Categories

Resources