Database Users

Need Help.. i've got "boot varified failed" when I try to downgrade from 3.2 to 3.1

Need Help.. i've got "boot varified failed" when I try to downgrade from 3.2 to 3.1
I upgrade to 3.2 but it can't Root so try to downgrade to 3.1 but it can complete and stuck in acer logo and show "boot varified failed"
Does anyone advice me how to solve this problem...

mikamocha said:
I upgrade to 3.2 but it can't Root so try to downgrade to 3.1 but it can complete and stuck in acer logo and show "boot varified failed"
Does anyone advice me how to solve this problem...
Click to expand...
Click to collapse
As for downgrading, right now its impossible until someone figure out how to root 3.2. There are lots of people (including myself) stuck in the same boat, so I feel for you. It has something to do with the newly installed bootloader only recognizing post-3.2 images.
As for getting out of your current predicament, I would start in the development section. You may try getting a copy of the stock 3.2 rom, putting it on your SD card, and recovering with that. That might at least get you running on 3.2 again.
Sorry I can't be more help.
Cheers,
-PW
P.S. Found a link that may help you:
http://forum.xda-developers.com/showthread.php?t=1113878

pacificwing said:
As for downgrading, right now its impossible until someone figure out how to root 3.2. There are lots of people (including myself) stuck in the same boat, so I feel for you. It has something to do with the newly installed bootloader only recognizing post-3.2 images.
As for getting out of your current predicament, I would start in the development section. You may try getting a copy of the stock 3.2 rom, putting it on your SD card, and recovering with that. That might at least get you running on 3.2 again.
Sorry I can't be more help.
Cheers,
-PW
P.S. Found a link that may help you:
http://forum.xda-developers.com/showthread.php?t=1113878
Click to expand...
Click to collapse
Thanks for your advice , I try to do that but it can't...
maybe I should wait for 3.2 update.zip ,right.

The only way out of your current mess is to flash one of the 3.2 images from http://forum.xda-developers.com/showthread.php?t=1113878
It will leave you on a stock, non rooted 3.2... you can't get back to 3.1 but at least you can use the tablet.

ve6rah said:
The only way out of your current mess is to flash one of the 3.2 images from http://forum.xda-developers.com/showthread.php?t=1113878
It will leave you on a stock, non rooted 3.2... you can't get back to 3.1 but at least you can use the tablet.
Click to expand...
Click to collapse
anyway i try to download and try to do that...
as http://forum.xda-developers.com/showthread.php?t=1113878
but i dont understand about ..
How to flash update package :
Once the desired file downloaded, you have to use Acer Update Decryter to decrypt them.
After decrypting the file, you have to extract the update.zip from it, put it on an external SDCard (does not work on internal memory) and boot your tablet with Vol- & Power. The update will be launch automatically.
{
"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"
}
after I decypting file it also has decypted in file's name
"After decrypting the file, you have to extract the update.zip "
how to extract the update.zip ,,pls
because my tablet now just only read the update.zip file
pls advice again ,,, thanks so much in advance,

mikamocha said:
after I decypting file it also has decypted in file's name
"After decrypting the file, you have to extract the update.zip "
how to extract the update.zip ,,pls
because my tablet now just only read the update.zip file
pls advice again ,,, thanks so much in advance,
Click to expand...
Click to collapse
Wow, it's not hard. Just unzip the decrypted file, the update.zip is inside it...

ok , i can upzip already .. mayby my winzip in my desktop has got problem..
thanks so much again

1/ Go to thread http://forum.xda-developers.com/showthread.php?t=1113878
2/ Download this file :
HC 3.2 :
Acer_A501_0.000.00_4.017.03_EMEA_CUS7 : http://cdn.acer.futuredial.com/Acer_...7_dc802d69.zip
3/ Run Acer Update Decrypter and decrypt downloaded file
4/ Unzip decrypted file
5/ Copy update.zip on root of external micro sd card
6/ Power On + Vol down and update

One poster on a different forum contacted Acer support and asked how to roll back to 3.1 as he was a developer and desperately needed a roll back.
Acer support replied "factory reset".
I'll assume the dude was referring to the reset pinhole next to the rocker?
Anybody attempt this method? Not that I need to, as I know better than to take an OTA update when rooted and custom recovery.
Just curious if anybody tried and what result they got.

mung go pantip plaza and ask reset firmware that should be ok

sanaell said:
mung go pantip plaza and ask reset firmware that should be ok
Click to expand...
Click to collapse
I guess that means don't stick your thing in the hole?
Or maybe, you're going to beat the sales rep on the head, and say "fix my firmware"

VZW 2.3.5 update borked my tab, can I ODIN/Heimdal over?

My wife carries the orginal G-Tab and we did the 2.3 update when it became available OTA. Ever since this, the thing is in a violent loop of force closing to the point that she can not really use it. The FC pop ups are out of control.
Verizon will replace the unit, but I thought that since it worked perfectly up until the 2.3.5 OTA, it has to be something that did not work according to the plan with the OTA.
We have done a factory wipe and that did not help anything.
I am set up with ODIN3 and Heimdal on this PC, so If there is a way to push back to 2.2 so that I can try the OTA again, or if I can push a clean non borked 2.3 in that would likely solve the issue and not force me to send it back for a refurb as we purchased this new and up until the OTA have had no issue.
Thank you.

Am I out of luck on getting a stock image to push?
Sent from my HTC Thunderbolt 4G using Tapatalk.

here ya go! no need to go back to 2.2!
http://forum.xda-developers.com/showthread.php?t=1362016&highlight=stock

Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.

larry0071 said:
Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
I posted a link to a heimdall file from droidforums.net that worked for me - look in this general forum for "vzw update fix" topic
Sent from my SCH-I800 using XDA App

U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App

YoshiFan501 said:
U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.

Ok, shut down both the pc and the galaxy tab, restarted both and opened up Superoneclick, clicked Unroot and it stopped at the same place.
This where I get to.
{
"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"
}
HTC Thunderbolt 4G using Tapatalk.

Honestly, just delete any root apparently like superuser titanium setcpu and the like if you need to return it. Think about it. These guys get HUNDREDS of rma devices a day. They aren't adbing or checking file systems for each one. They check it for water damage/physical damage then package and ship a refurbished model.
larry0071 said:
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
Sent from my LG-P999

Well, for warranty they now make you ship your defective unit in first and then they ship another unit out.
If they turn mine on, within 30 seconds they will see this, assuming they are even moderately intelligent.
I am worried that setting that in kernal will have them doing back flips and voiding the warranty.
HTC Thunderbolt 4G using Tapatalk.

And the update from 2.2 that it wants to install fails as expected because it sees that the thing is rooted. Not that the update is important, but it further indicates to them that I have issues related to a non stock system.

OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!

larry0071 said:
OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!
Click to expand...
Click to collapse
Use the instructions in this thread
http://www.droidforums.net/forum/sa...-how-flash-stock-rooted-ec02-froyo-2-2-a.html
This will bring you to stock version after dj11, and allow you to download and install verizon 2.3.5 official ota update - after flashing this version, go to settings, system updates, and you should be ready downloading update - follow on screen instructions and you will be good to go

Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:

leapinlar said:
Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:
Click to expand...
Click to collapse
That link goes to a DL page but I can not DL it. Can you drop box it for me?
I've downloaded 8 supposedly stock non-rooted VZW Glaxy Tab heimdal packages, and every one of them leaves me rooted with Kernal version 2.6.32.9 [email protected] #3. I really want rid of this so that I do not get burned when I send it in.
What I have tried so far today to get rid of root:
Real_Stock_for_galaxy_tab
Verizon-GTab-Stock-non-root
VZW.2.3.5.Stock.Root
I also tried SuperOneClickv2.2-ShortFuse, but this freezes on my tablet about 8 or 10 steps into the Unroot process.
Anyone know how to get my Kernal to show up as stock?

I went in to your DL link with Chrome and it worked. FOr some reason... IE did not play nice with that Megashares. I'll try yours and let you know what happens.
Larry

OK, the version you provided (SCH-I800_VZW_EC02.zip) does also still show the kernal as 2.6.32.9 [email protected] #3 and it also has SuperUser in the application lists.

So, I give up. I went back to one of the ROMs that has the kernal still listed as rooted but does not have SU installed or anything that is obviously indicating root.
I will send it in, and cross my fingers. Lets hope the guys getting in warranty exchange hardware do not take the time to really look, or I am screwed, blued, and tatooed.

I see no signs of rooting on that page. Or do you mean the [email protected] part? That's normal, and shows on an unrooted device as well! I don't have a VZW (mine's a European GSM), but my Tab is 100% original and unrooted, and it shows Kernel version 2.6.35.7 [email protected] #2. For an ordinary user it's actually not that simple to see if a Tab is rooted. One sign that may show is the presence of the app SuperUser. If you've rooted your Tab with SuperOneClick, it will be present as a system application which you can't remove by ordinary means. You can tell if a ROM is UNrooted by installing an app that needs root and running it, it will complain it needs root.
So the unrooted ROM's you tried may well actually have been unrooted if all you checked is the root part in the Kernel Version!

[Q] OTA update keeps failing to download

My wife got me a brand new A500 off ebay a couple of months ago for a Christmas gift(for me it's only three days old). So far I love it but it will not take the OTA update that it keeps bugging me about. The download starts fine but then stalls out mid download. I looked here http://forum.xda-developers.com/showthread.php?t=1113878 but did not see my current version there. Can anyone point me in the direction of the OTA I need to download and flash with recovery? My build is Acer_a500_1.145.09_com_gen1 I'm running 3.0.1. It looks like it's trying to download 4.010.11.
Further info:
According to the log the file name is Acer_A500_1.145.09_4.010.11_com_gen1_1311243587838_bd1ab95c.zip
I can't find that file anywhere on the net.

The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
If that's not the case, then you can just install the update manually. Download the update you want and put it on your external SDCard and then enter recovery (using power and volume). The recovery will install the update for you.

timmyDean said:
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
Click to expand...
Click to collapse
It said it was brand new. My wife would not buy something like this used. The weird thing is it knows it has an update and it starts to download and get's up to half way downloaded and then it just stops. It shows that it still is pulling data but the downloaded file size doesn't increase anymore after it stalls.
Ive been looking into rooting it and since I'm on 3.0.1 it appears Gingerbreak is all I need. The next question is what rom should I get and how do I go about installing it? I've never rooted droid before and most instructions on XDA are written for the experienced level and not the new guy. I'd like to stay fairly stock but rooted.
Sent from my A500 using Tapatalk

There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14

timmyDean said:
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
Click to expand...
Click to collapse
Just to make sure I'm getting it right: I go here http://forum.xda-developers.com/showthread.php?p=20680452 download that to my PC and follow the instructions contained within and I end up with a stock rooted 3.2.1? I don't need to download anything else right? A soft reset for this tab is pusing the little red button on the end by the USB port?
Sent from my A500 using Tapatalk

Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.

timmyDean said:
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
Click to expand...
Click to collapse
Sweet. You're a life saver. Thanks for translating it all to noob for me. Will I need to reinstall all of my apps and such afterwards?
Sent from my A500 using Tapatalk

Yes, the flashing tool makes it just like new, out of the box, but with root.

timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
OK that's not a big deal. The SD card will remain intact though right?
Sent from my A500 using Tapatalk

Jds method does work. But you can also trybthis.
http://forum.xda-developers.com/showthread.php?t=1410802
Simple easy no computer needed

timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
I tried your method and I get stuck at the serial number part. It says ADB server out of date. What do I do?
{
"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"
}
Edit: Never mind. I got my steps out of order. I was clicking next before running test.cmd
Last edit: It appears to have worked. I'm back to the initial setup screens just like when I first got it.

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?

[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.