Database Users

[WIFI Only] [How-to] GT-P1010 Gingerbread Update

I know a lot of people are going to have problems updating to the latest gingerbread build.
PLEASE NOTE: This update will remove root but you can root again with CF-Root from second post.
ALSO, THIS PROCESS WILL WIPE DEVICE!
1) Put your P1010 into download mode (by holding POWER and VOL-DOWN):
{
"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"
}
2)I went ahead and used ODIN tool to downgrade/upgrade to the latest FROYO firmware before Gingerbread:
P1010XWKC1_OXX
(OEM Flash Guide here)
You should have the same tick marks and files loaded as in my screenshot. Be sure that the box is yellow on the right and you can initiate the firmware install by clicking 'Start'.
3) (VARIES) From there, after restart some people will experience a force close followed by a reboot loop. You will need to flash this kernel via ODIN:
P1010ZHKF1-kernel
(Flash this the same way as above but UNCHECK Re-Partition and CSC!)
4) You will then be able to boot into Froyo.
5) You will use ODIN again to install the Gingerbread update and flash just the PDA (leave CSC blank and leave Re-partition unchecked this time).
P1010XEUKPG
(Flash this the same way you flashed the Kernel in step #2)
6) After it reboots, you will have 2.3.6
7) (Optional) steps in post #2 to install CWM Recovery and Root.

I recommend installing CWM Recovery and CFRoot in the thread below:
ClockWorkMod Recovery for P1010
After you install CWM Recovery, you can do a nandroid backup and never worry about brick again! (=
Also, you can use ES Explorer to mount root and get rid of the Samsung bloatware (AT YOUR OWN RISK!!!)

For those wanting to remove the bloatware (AT YOUR OWN RISK!!!):
You can remove the bloatware with ES Explorer, there's an option to enable 'Root Explorer'. Download the latest version from the Market.
See below:
screenshots are from my Galaxy Nexus but it's the same for any Android 2.2+.
1) Go to the 'Settings' screen
2) Change home directory to '/'
3) Tick the 2 marks on the bottom
4) Browse to /system/app
5) Delete whichever app you don't want, but do it with caution (I usually move these files to /sdcard and move back if it causes any type of force close)
If you totally borked out the system in such a way that you can't boot, you can always move it back in recovery via ADB (much more complicated process but it's possible).
Also, why not do a nandroid backup before messing with deep system files?

Nice! Great topic.

Updated op! =)

this is the best christmas present so far.
edit: worked, almost. thanks ! rooted flashing Skin1980-CF-ROOT-P1010-BETA.tar .
skype isn't using the front camera. =s

Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App

r_3 said:
Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App
Click to expand...
Click to collapse
It's THE EU ROM but it works with my US P1010.

No restart issues?

r_3 said:
No restart issues?
Click to expand...
Click to collapse
If you followed those steps, the ROM runs stable without any FC's or reboots. I even have setCPU installed on mine.
Also, it's good to note that I'm running CF-Root kernel from the thread in 2nd post.
Plus, you could always downgrade if you run into issues. Just remember to always BACKUP YOUR DATA!

nice!
wow this is good news! does this modded skype work on this: http://forum.xda-developers.com/showpost.php?p=16889575&postcount=1262
or
http://forum.xda-developers.com/showpost.php?p=20697907&postcount=1640
?
I cant try it now as I'm not home. I hope someone could try as so I won't have to think about it until I get home..

@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck

densets said:
@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck
Click to expand...
Click to collapse
Could you attach the logcat here? or if you could send it directly to theos0o, that'll be great. he's the modder of the skype apps I pasted above.
could you also try this: http://forum.xda-developers.com/showthread.php?t=1153285 this works for me using froyo.

im getting excited about this.. is it really for the p1010 wifi only device? because from what i can see in this subforum is the devs working on the p1000 only. another thing, please don't tell me this is an official update. i don't think the bad sammy will update this little tab.

Depending on where you are freon yes it its the official ireland uk update and makes massive difference as well
Much better tab.
Sent from my GT-P1010 using Tapatalk

skype is working
@densets, skype is working for both skype mods I posted earlier. you just need to enable 'use valid preview'. for droidrx's version, set the app to 'crop' so your video is centered.

phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.

urra901109 said:
phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.
Click to expand...
Click to collapse
hmm, if you are still in froyo, you can use ffc on skype: http://forum.xda-developers.com/showthread.php?t=1153285
just rotate the camera and try out different settings.

sorry for the newbie question, but what's the password for the 2.3.3 file from sammobile?
edit: already found it, my bad

Interestingly, I've followed the guide exactly as mentioned above (had KC1 and the HK kernel from previous flashing) and flashed the PDA for XEU 2.3 from Sammobile, and I'm now stuck in an eternal bootloop. I like the new samsung boot music though, better than the previous one
Any suggestions?
Edit: I wiped data and cache from recovery, flashed KC1 and the Kernel and it boots fine. Checked Kies to be sure and it's offering me FW upgrade to KM2. Should I accept this FW upgrade or just persevere with flashing the new 2.3 firmware?

Best method to root on 4.2.2?

My phone was rooted and I did a factory reset to send it to have the screen repaired. I lost root and I get the message "com.android.phone not responding" all the time if I restart the phone but it works fine. Someone told me to use Odin to wipe the phone and get rid of that message. After I do that, what tool should I use to root on 4.2.2?

Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.

RockRatt said:
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
Click to expand...
Click to collapse
Thanks.
{
"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"
}
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
I had a similar situation, and the AT&T updates would fail at ~28%, even though I never approved the updates (my guess is that after I've said no more than 3 time, they did it anyways?). At that point I was stuck, and to make things worse, the WiFi was working only in my house, but no data over the ATT network, just voice. Even reflashing with ODIN didn't resolved the problem.
Had to bite the bullet and get the phone replaced by the warranty. I hope this doesn't happen to anyone else,

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
Since it is MDL firmware just use Motochopper + Loki and you will have a custom recovery (TWRP or CWM YOUR CHOICE). Then flash ANY custom ROM on your phone. You can have the best of BOTH worlds. You can flash a updated firmware ROM like ShoStock for the Touchwiz based Roms or a AOSP based ROMs. NO need to update firmware from ATT. In fact you lose what you can do with your phone if you do.
If you REALLY want to update to ATT newest firmware you can download the STOCK MDL firmware from samfirmware. Flash it which will make your phone PURE STOCK firmware and recovery. Then you will be able to update from ATT. The reason it fails is because you are rooted and probably custom recovery already?

Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?

SRCP said:
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
Click to expand...
Click to collapse
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that pic is recent. I got it repaired months ago.

Stuck at 4.2.2, bootloop on higher versions

Whenever I try to update 4.2.2 to a newer version via about -> phone, I get bootloop at Google logo. I've already tried to follow "official" guide for rooting but flashing any ROM in CWM newer than 4.2.2 resulted in the same error. I've been desperately looking for solutions for a while and finally came across this blog http://fixandoridproblems.blogspot.co.il/ . I actually managed to get working 4.3 with those steps, but again, as soon as I update it, I get bootloop.
In addition I got weird error while flashing ParanoidAdroid + GAppps, so that obviously didn't help as well. Of course I always wipe data, cache and dalvik cache before flashing anything whatsoever:
{
"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"
}
I really don't know what else to do, so some help would be greatly appreciated. Thanks in advance.

this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

hp420 said:
this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the factory image from developers.google.com for Nexus4 4.4 then reflash the latest versions of custom recovery and SuperSU

I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.

krneki10 said:
I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.
Click to expand...
Click to collapse
Dude, we've told you repeatedly....FLASH A FACTORY IMAGE WITH FASTBOOT! STOP USING RECOVERY, BECAUSE THAT IS YOUR PROBLEM!!
Read the guide on how to flash with fastboot.

Jd is right, there are devices out there that after a certain amount of time will refuse to boot any OS above 4.2.2, regardless of how the OS is flashed to the device. No idea why this happens, and the only solution is to get another device.
Sent from my Nexus 4 using XDA Free mobile app

I have the exact same problem on my nexus 4, have you found a fix?

I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
Take a look: http://forum.xda-developers.com/nexus-4/help/help-please-bootloop-4-4-4-imei-t2882868
I'm tired of trying different solutions whit the same result, its exhausting

conquesoextra said:
I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
I'm tired of trying different solutions whit the same result, its exhausting
Click to expand...
Click to collapse
I think this has happened to a few people recently. It happened to me too. For now I have ogt 4.2.2 running, I managed to fix the baseband and IMEI but if i update to a new version it gets broken again.
This is what I did to fix IMEI, hope it works for you
http://forum.xda-developers.com/nexus-4/help/fix-nexus-4-bad-imei-t2882694

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"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"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??

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