Droid Turbo - Android 5.1 Root upgrade path discussion - Verizon Motorola Droid Turbo General

this is a thread for brainstorming and testing an upgrade path from 4.4.4 stock to 5.1 stock that retains root (that is all).
i'm assuming trying to flash a pre-rooted 5.1 system .img (if ever becomes available) using mofo is not going to work unless something changes [ie, how would you get the new modem, kernel, etc?]
idea 1:
a. use mofo to flash xt1254.system.21.44.12.quark_verizon.rooted.ext4.img (stock 4.4.4 with root baked in, no other system modifications).
b. next, manually flash the android 5.1 OTA patch .zip (whenever its public, or if any soak members are willing to test now)
c. question for a willing tester (realize once you go 5.1 you cant go back and might not ever see root again), does root remain or is it lost during the upgrade?
idea 2:
a. if the above system upgrade from 4.4.4 to 5.1 does work but root is lost (and there is no "OTA Keeper" type app in the image), could we bake in a 'backup' of root and a 'restore' app into the xt1254.system.21.44.12.quark_verizon.rooted.ext4.img and then could we again upgrade to 5.1 and 'restore' root on a temporary basis (better than never having root).
b. of course this is not ideal, but if that does work, then maybe someone could also bake into the base 4.4.4 image an app that auto-restores root quickly on every boot, for a virtual perm temporary root solution.
idea 3:
put your thinking cap on and please provide.

Idea 1 is a no go

PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
well, bummer, thanks. sounds like we'll have to skip to idea 3.
but to confirm, does the 5.1 OTA patch not manually flash over a clean xt1254.system.21.44.12.quark_verizon.rooted.ext4.img ? OR it does, but root lost?

Doesn't flash at all

Has someone tried using Mofo that has taken the new update? I saw that the 2nd gen Moto X works with Mofo & 5.0 Lollipop, but not sure about 5.1.

I'm kind of confused. Can't we just modify the stock 5.1 image to have root? Or does mofo refuse to flash it?

PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.

Can you install the update on a rooted phone? Or do I need to go back to stock?

janitorjohnson said:
Can you install the update on a rooted phone? Or do I need to go back to stock?
Click to expand...
Click to collapse
back to stock. it will fail if rooted

Does anyone have a completely stock system image ?

Anyone tried kingroot?

Can't get back to stock for some reason ..rooted .. Can some one help me

One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.

hotrodwinston said:
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
Click to expand...
Click to collapse
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?

johnbravado said:
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
Click to expand...
Click to collapse
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.

neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
I would think you would just look at the SuperSU.zip script file and then insert all required files as described in the script.
https://su.chainfire.eu

Tomsgt said:
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Click to expand...
Click to collapse
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
PILLMUZIK3600 said:
Does anyone have a completely stock system image ?
Click to expand...
Click to collapse
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
does mofo flash the modem/kernel, data, etc ? or is it only going to flash the system partition?

chip! said:
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
mofo already said its not going to work on 5.1.. so we know you can only use mofo with droid turbo when the phone is still on 4.4.4. and i dont see how you can go 4.4.4 -> 5.1 from a 'system' partition .img alone. someone feel free to set the record straight, but it would be surprised if modem, kernel, etc are embedded on system partition.
Click to expand...
Click to collapse
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand

Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Faith age, boys.

Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Sweet can't wait

Related

[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011

Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.
Bookmarking this, just in case. Thanks, Jcase!
Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!
http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread
I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!
Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890
droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.
jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.

[Q] Failure to update 4.2.2

after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??
williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?
I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD
This happened to me too, though I have the wifi-only version. So it's not just the radio.
I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !
rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,
spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.
khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.

XT1052 India 4.4.4 OTA

I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA
Could you post the stock recovery image of the 4.4.2 ROM, please?
ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.
Thanks anyway. It'd be awesome if someone who has it posted. Anyone?
Yep, the update just popped up. How do you capture it by the way? What's the path?
devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.
samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...
samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?
There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed

Installing 5.0.2 on rooted tablet

So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file
jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away
viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)
Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.
Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).
I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.
So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?
Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.

Factory images with January security patch now available

This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?
Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?
simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Everything's fine for me.
FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.
Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk
anyone having trouble downloading the new system image from the site?
simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.
maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ
Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.

Categories

Resources